Ad format carriage

The capability declaration and partner identity of the Open Measurement Interface Definition (OMID) are carried through the auction by OpenRTB and AdCOM. Request side: imp.{banner,video,audio,native}.api with value 7 (OMID-1 in the AdCOM APIFrameworks list) declares that the placement supports OMID, bid.apis declares that the creative requires OMID, and source.ext.omidpn / source.ext.omidpv carry the name and versionString of the OMID Partner object. For Native ads a custom event tracker with event value 555 carries the verification script resource.

• ·Request-side carriage points: api / apis / source.ext.omidpn / source.ext.omidpv
• ·Native's event 555 with ext.vendorKey and ext.verification_parameters

Response side: verification scripts of the Open Measurement Interface Definition (OMID) are carried by VAST's AdVerifications / Verification elements (declared on both InLine and Wrapper in the official 4.0 XSD), JavaScriptResource marks an OMID resource with apiFramework="omid", and the browserOptional attribute plus the VerificationParameters element are integrated from 4.1; the macros [VERIFICATIONVENDORS] and [OMIDPARTNER] fill in the verification vendor list and the Partner identity (name/versionString) respectively. The Video Player-Ad Interface Definition (VPAID) is deprecated as of VAST 4.1 and its measurement role is taken over by OMID.

• ·The AdVerifications / Verification elements and their attributes
• ·Version introduction of apiFramework="omid" and browserOptional

How verification scripts are carried in Native ads (the OpenRTB Native Ads specification): the combination of event trackers and ext fields, access mode selection under native rendering, and the measurement methodology for the nativeDisplay creative type.

• ·Carriage points for verification scripts in a Native response
• ·Native-specific conventions beyond event 555