Why do I need an external view tracking with popups?
Unlike banners it comes with pop-ups often the case that the popup will not be displayed (for example due to pop-up blockers or because the advertiser has a frequency capping / targeting enabled). If so, there can be Zählabweichungen between publishers and marketers: The publisher counts all "Views" (every time the pop-up code was integrated into the page) - the marketer but only counts the views in which the pop really has opened.
To unify these different counting can be used external view tracking.
How are the views counted in PopUp blockers?
It depends how the ad is created.
Case a)
Publisher opens itself the popup window. He got a simple banner or the URL that is to show the popup.
In the event publishers and advertisers count the same.
Case b)
The publisher gets a script code which the popup. Here, the publisher counts only "script code embedded" (= View) while AdSpirit counts if the popup has risen.
Therefore it is necessary in case b, the publisher of the ViewUrl to AdSpirit passes so we can tell him when a view has really taken place. The reaction takes place via the parameter &exttrack=
Reacting external view Tracking
To be used by the publisher at pop campaigns external view tracking, this can be done by appending the tracking URL to the pop-up script.
| Parameters for the placement of the publisher | &exttrack= | the attached URL is displayed as a 1x1 pixel image with every pop appeal. |
Example of a foreign AdServer the publisher:
...&exttrack=View tracking URL_des_Publishers (Encoded)
For example if the publisher also employs a AdSpirit AdServer:
...&exttrack=%viewredirect2%