Native Ads carriage
plannedHow 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.
What this page will cover
- Carriage points for verification scripts in a Native response
- Native-specific conventions beyond event 555
- Access modes and geometry data under native rendering
Source material
| Source | File / path | commit | Fetched | Integration status |
|---|---|---|---|---|
| InteractiveAdvertisingBureau/AdCOM | OpenRTB support for OMSDK.md | 26c59ba | 2026-09-22 | integratedThe Specific Guidance for Native Ads section is integrated and can support the event 555 part |
| InteractiveAdvertisingBureau/Native-Ads | OpenRTB-Native-Ads-Specification-Final-1.2.md | 5b9afa2 | 2026-09-22 | not integratedThe intersection between the Native spec and OMID has not been verified item by item |
Reusable material
- /protocol/native/1.2
Native object and enum definitions live in the Native module
Gaps to verify
- Requires cross-checking Native Ads 1.2 against the OMID spec PDFs; this site currently integrates only the OpenRTB-side event 555 convention, which is not enough for field-level prose.
Related chapters
- Ad format carriage
- OpenRTB / AdCOM carriage
- Impression criteria & creative typesplanned