Impressions#
The following diagram presents a simplified overview of the interactions between Supply-Side Platform and Demand-Side Platform regarding Impression Events and Conversion Events:
General rules#
Here are general rules guiding the workflow around Impression Events and Conversion Events:
All Impression Events originate from Supply-Side Agent, as this is the only entity able to observe the User interacting with Creatives within the Site.
All Conversion Events originate from Demand-Side Agent, as this is the only entity able to observe the User performing actions within the Target.
Each Impression Event must be reported to both Supply-Side Platform and Demand-Side Platform, so that they can stay in synch.
Additionally, each Register Event must be reported to both to the Context Provider associated with Supply-Side Platform and the Context Provider associated with Demand-Side Platform.
In case of Register Events, Context Provider returns a Context Script, and Supply-Side Agent is expected to make an attempt to execute this script within its sandbox.
Supply-Side Agent is free to report Impression Events to its Supply-Side Platform in any way it wants, as this communication is not part of Adshares Protocol. However, reporting Impression Events to Demand-Side Platform is based on the following rules:
In case of View Events and Click Events, the endpoint for notification calls is contained in the Creative Object payload.
Whereas for Register Events, the endpoint for notification calls is contained in the Context Scripts returned in response to the View Event notification call.