Event types

Event types name the ad events a tracker can fire on: the creative loading, the impression, and three viewability thresholds. AdCOM uses the list in the Event and EventSpec objects, which makes it an OpenRTB 3.0 signal. OpenRTB 2.x carries similar codes in Native 1.2 eventtrackers, but Native 1.2 numbers them differently, so the two lists cannot be copied across.

List: Event Types6 values

Values

Value	Name	What it means
`1`	loaded	The creative markup was delivered and loaded, possibly before it rendered; the point to start measurement scripts.
`2`	impression	An ad impression as defined by the IAB and MRC impression measurement guidelines.
`3`	viewable-mrc50	Viewable by the MRC standard for display: at least 50 percent of the ad in view for one continuous second.
`4`	viewable-mrc100	A stricter standard: the whole ad in view for one second.
`5`	viewable-video50	Viewable by the MRC standard for video: at least 50 percent in view for two continuous seconds.
`500+`	Vendor-specific codes	Vendor-specific events agreed between the parties.

How to use it

The list describes when an event happens, not how the tracker fires; the method comes from the event tracking methods list. AdCOM suggests attaching measurement scripts at the load event so they are running before the impression. The key trap is numbering: Native 1.2 starts at 1 for impression, 2 for 50 percent viewable, 3 for 100 percent viewable and 4 for video viewable, with no load event. AdCOM inserts load as 1 and shifts the rest up by one.

Common mistakes

Sending AdCOM numbers in Native 1.2 eventtrackers, or the reverse. A Native 1.2 viewability tracker sent as 2 is read by AdCOM as an impression tracker.
Firing an impression tracker at the load event. Load happens before rendering and is not an impression.

Validation

On OpenRTB 2.6 snapshots, RTBlint reports a value outside this list as openrtb.value.invalid. Paste a request into the tester to check the values you send.

Related lists

All lists are on the enumerated lists index.