What are eventtrackers in Native 1.2?
Answer
eventtrackers is the Native 1.2 mechanism for declaring and returning ad tracking, replacing the older imptrackers and jstracker fields, which the spec marks as to be deprecated. In the request, the eventtrackers array states which events and methods the publisher supports: event types include 1 = impression, 2 = viewable-mrc50 (50% in view for 1 second), 3 = viewable-mrc100, 4 = viewable-video50, with 500+ reserved for exchange-specific types; methods are 1 = img pixel and 2 = js tag. In the response, each EventTracker object carries the event, the single method chosen, and the tracking URL. Bidders should send eventtrackers and keep imptrackers only for legacy partners.
Go deeper
More questions on video, ctv, native, floors, deals, and macros
- How do I build an OpenRTB video bid request? Add an imp.video object to the impression; its presence is what marks the impression as video.
- What is plcmt in OpenRTB video? imp.video.plcmt declares the video placement subtype using AdCOM's Plcmt Subtypes list, which follows the updated IAB digital video guidelines.
- What plcmt value should I send for CTV inventory? Send imp.video.plcmt = 1 (instream) for CTV.
- Should I send placement or plcmt in a video bid request? Send both during the transition, but treat plcmt as authoritative.
- How does ad pod bidding work in OpenRTB 2.6? Each slot in the pod is its own imp, and a shared imp.video.podid ties them together.
- How do I signal server-side ad insertion (SSAI) in a bid request? Set imp.ssai, an integer added in OpenRTB 2.6 with default 0.
All 93 questions are listed in the OpenRTB FAQ.