This section covers all information about the Implementation of the DMP Pixels.
| Contents of the Table | |
|---|---|
|
On-Site Pixel
Place this exported code (Javascript) on the website. For an easy implementation it is advised to put it in a centralized <head>Pixel</head> or <body>Pixel</body> section.
Pixel Activity Monitor
An important step of the implementation is to check whether the pixel is implemented correctly and the data is being collected properly. In order to do so the DMP includes a feature to verify the DMP pixel loads in a user-friendly way and without the need for developer skills. The Pixel Activity Monitor can be enabled as an On-Site pixel module and serves as a tool to verify the DMP pixel is active on the website. It will pop-up as a floating and draggable element in your browser and shows all data events that are initiated by the implemented pixel script. This also includes interaction events like ‘Time on Page’, ‘Page Scroll’, and ‘Form Interactions’ that are originating from the default pixel modules. Please note that this module is not available by default.
...
| Info | ||
|---|---|---|
| ||
Note that the tool can also be used for demo purposes. An extension like Greasemonkey (Firefox) can be used to automatically run the Pixel script on a given website. |
Impression Tracking Pixel
Add the exported code to the creative in the execution platform. Most platforms support 3rd party impression tracking through one mechanism or another. Many ad servers include a user interface which lets you paste in third-party Impression tracking URLs. If the ad server doesn’t have a UI for trafficking third-party impression tracking URLs, you should still be able to include them at the creative level. Some ad servers offer creative templates that include options for third-party trackers. With other ad servers you might have to change the creative type to one that lets you enter or edit the HTML code for the creative.
Template
The default impression tracking pixel template can be found below:
| Code Block | ||
|---|---|---|
| ||
https://go.flx1.com/imp?id=12345&m=11&pl=1 |
Parameters
- Required: The "id", "m" and "pl" parameters are required and static in a sense that they may not be changed. The "id" represents the pixel_id, the "m" represents the customer_id that is assigned to your DMP instance ID (this will always be the same for your account) and the "pl" represents the "platform" for which you exported an impression tracking pixel.
- Optional: The impression trackers pixels can be customized to a large extent by means of predefined parameters as part of our log format.
Macros
Creative macros allow you to transmit impression-level information to systems outside of the execution platform - in this case our DMP - which you can then use for audience building purposes, reporting and/or campaign optimization. In this example, you would like to capture information about the advertising campaign and inventory you're buying and store it in our DMP.
Pixel Type(s)
Our DMP supports the export of both a JavaScript and an image type impression tracking pixel. The only difference that may be noticed from the export URL is the additional "t=gif" parameter. In most execution platforms you only have to add the URL of the pixel and choose between a type for the actual implementation. However, if this is not supported you need to implement the impression tracking pixel as HTML tags which can be done as follows:
...
| Code Block | ||
|---|---|---|
| ||
<img src="//go.flx1.com/imp?id=12345&m=11&pl=1" width="1" height="1" /> |
Secure Protocol
With the implementation as outlined in this entry our pixel automatically determines the correct protocol and handles the requests according to the standard(s).
Click Tracking Pixel
Add the exported code to the creative in the execution platform. Most platforms support 3rd party click trackers and offer a feature to simply copy/paste a click tracking template as part of the user interface. In addition, most execution platforms do have a landing page URL macro available that can be set as value for the "&out" parameter to automatically redirect to the landing page that is set on another level (i.e. advertiser or campaign). If this is not supported you can either put the click tracking pixel in front of the landing page url or add it to the creative code that will be trafficked directly into your ad server.
Template
The default click tracking pixel template can be found below:
| Code Block | ||
|---|---|---|
| ||
https://go.flx1.com/click?id=12345&m=11&pl=1&cid=12345678&out= |
Parameters
- Required: The "id", "m" and "pl" parameters are required and static in a sense that they may not be changed. The "id" represents the pixel_id, the "m" represents the customer_id that is assigned to your DMP instance ID (this will always be the same for your account) and the "pl" represents the "platform" for which you exported a click tracking pixel. The "cid" and "out" parameters are also required but may be dynamically populated. The "cid" respresents the creative_id of the ad unit and the "out" parameter initiates a redirect to the landing page URL. Therefore, the "out" parameter should always be the last element of the Click Tracking Pixel and the value must be either the actual URL of the landing page or a macro that populates the landing page url automatically.
- Optional: The impression trackers pixels can be customized to a large extent by means of predefined parameters as part of our log format.
Macros
Creative macros allow you to transmit impression-level information to systems outside of the execution platform - in this case our DMP - which you can then use for audience building purposes, reporting and/or campaign optimization. In this example, you would like to capture information about the advertising campaign and inventory you're buying and store it in our DMP.
Secure Protocol
With the implementations as outlined in this entry our pixel automatically determines the correct protocol and handles the requests according to the standard(s).
Common Questions
- What is the difference between the referer_url and the event_referer_url?
The referer_url is present in the 'Request Header' section of the browser console and represents the referer of the pixel itself. In case a user enters a page on which the pixel is active and being loaded for the first time this referer_url is always similar to the actual event_url. When you then visit the 'next page' it will be the url of the first page visit where the pixel was loaded. Consider this as the internal pixel referer_url. The event_referer_url is present in the 'Query String Parameters' section of the browser console. This is the referer_url as represent in the 'Query String Parameters' section. As an example you could imagine that a user has entered the page on which the pixel is active as a result of clicking on a google search entry and can therefore be seen as the cross-domain referer_url.
...