Track device playback
Fire the URL exactly as stamped by the server, appending only ets (occurrence time in RFC3339). Every query parameter is server-provided — relay the URL verbatim, never parse or modify it. An <Error> URL is the one exception: fill in its [ERRORCODE] macro and skip ets.
Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters”Asid is the per-serving id (the ad-serving id; the decision-store key) stamped on the tracking URLs by Exchange.Ads.
Ad_event carries an ad-level event marker (e.g. “impression”). Proto field name is the GET query param (?ae=…)
Creative_event carries a creative-level event marker (e.g. “start”). Proto field name is the GET query param (?ce=…)
Sts is the Verve server timestamp stamped at decision time (RFC3339).
Ets is the player-side event occurrence timestamp (RFC3339). Optional with ce=error.
Dvactid is the opaque Advertima activation id.
The following are offline-fire enrichment params: present only on offline self-resolving fires, absent on online fires (which resolve via asid lookup). The handler branches on their presence (dual-shape decode). flight_id is the booked flight behind the decision.
Campaign_id is the campaign behind the decision.
Request_id groups the ads served by one /ads response.
Source is the supply kind behind the decision (a Source* kind).
Creative_id is the served creative/asset id.
Location_id is the place the device is located in (offline attribution).
Device_id is the player/screen that rendered the ad (offline attribution).
Flight_revision is the flight resource revision id at decision time.
Error_code is the VAST error code the player puts in place of the [ERRORCODE] macro. Sent with ce=error only.
Responses
Section titled “ Responses ”A successful response.
Empty body (200 = accepted for processing).
object
Examplegenerated
{}