D-010 List: Event Types numbers the events one apart from OpenRTB Native 1.2, which keeps impression at 1. Which numbering does the vocabulary take?
What the schemas do
AdCOM's numbering, as its table writes it: 1 loaded, 2 impression, 3 viewable-mrc50.
Options
Why
The registry is AdCOM's lists as AdCOM writes them, so the vocabulary takes AdCOM's codes. Native 1.2 is another standard with its own table; a bridge between OpenRTB 2.x native and AdCOM-based native must map the codes, and the record names the difference so that the bridge's authors see it.
What we ask the specification to state
Add a note to Event Types that its codes differ from Native 1.2's eventtrackers.event codes by one, and say which numbering an OpenRTB 2.6 native request uses. Today a bridge that copies the integer fires a viewability tracker on an impression.
The specification lines it rests on
Each line is quoted as the record pins it. Expand an item to read the quote.
main
List: Event Types, the row of
1L3629 at 26c59ba1| loaded: Delivered as a part of the creative markup. Creative may be pre-cached or pre-loaded; prior to initial rendering.List: Event Types, the row of
2L3633 at 26c59ba2| impression: Ad impression per IAB/MRC Ad Impression Measurement Guidelines.List: Event Types, the row of
3L3637 at 26c59ba3| viewable-mrc50: Visible impression using MRC definition of 50% in view for 1 second.
Tag AdCOM1.0-202607
List: Event Types, the row of
1L3629 at d67a6a81| loaded: Delivered as a part of the creative markup. Creative may be pre-cached or pre-loaded; prior to initial rendering.List: Event Types, the row of
2L3633 at d67a6a82| impression: Ad impression per IAB/MRC Ad Impression Measurement Guidelines.List: Event Types, the row of
3L3637 at d67a6a83| viewable-mrc50: Visible impression using MRC definition of 50% in view for 1 second.