Struct openrtb_native1::response::EventTracker
source · pub struct EventTracker {
pub event: EventType,
pub method: EventTrackingMethod,
pub url: Option<String>,
pub customdata: Option<Map<String, Value>>,
pub ext: Option<Map<String, Value>>,
}
Expand description
5.8 Event Tracker Response Object
The event trackers response is an array of objects and specifies the types of events the bidder wishes to track and the URLs/information to track them. Bidder must only respond with methods indicated as available in the request. Note that most javascript trackers expect to be loaded at impression time, so it’s not generally recommended for the buyer to respond with javascript trackers on other events, but the appropriateness of this is up to each buyer.
Fields§
§event: EventType
required; integer; - Type of event to track. See Event Types table.
method: EventTrackingMethod
required; integer; - Type of tracking requested. See Event Tracking Methods table.
url: Option<String>
optional; text; - The URL of the image or js. Required for image or js, optional for custom.
customdata: Option<Map<String, Value>>
optional; object containing key:value pairs; -
To be agreed individually with the exchange, an array of key:value objects for custom
tracking, for example the account number of the DSP with a tracking company. IE
{“accountnumber”:”123”}
.
ext: Option<Map<String, Value>>
optional; object; - This object is a placeholder that may contain custom JSON agreed to by the parties to support flexibility beyond the standard defined in this specification.
Trait Implementations§
source§impl Clone for EventTracker
impl Clone for EventTracker
source§fn clone(&self) -> EventTracker
fn clone(&self) -> EventTracker
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more