Implementing click trackers

Some Adserver-systems need a redirect and a landing page in order to make a click tracking work. 

 

Implementing click trackers in ad servers, other than Sizmek and DoubleClick for Publishers (DFP) or DCM

In most other ad servers, it is simply possible to select to use your pixel as a click tracker. Just find the place to implement click trackers and put in your pixel from AudienceReport.

Click trackers in Sizmek and DFP

If you are using Sizmek or DFP as your ad server, you need to build your own click tracker and provide it to them. Here is a quick guide in how to create a click tracker for Sizmek and DFP.

Please see below in the end of this text to receive information on how to make DCM redirects work.

First, here is an example of how a Sizmek and DFP clicktracker looks like:

http://clicktrackingv2.userreport.com/?[t-code];[Landing_page]

The part that you have to replace is the t-code. It is important that you leave the landing page section open, since you add your landing page in another place in Sizmek and DFP. 

The Landing page is simply the site where you want users to end after clicking at your ad. An example could be http://www.audiencereport.com 

Second, you need to type in the t-code of your tracking pixel. The t-code is found in the end of the tracking pixel created in AudienceReport. The Tracking pixel will look like this:

http://visitanalystics.userreport.com/hit.gif?t=xxx123456">

The t-code will be the part after, “t=”. Hence, in this case the t-code will be xxx123456.

To learn more about t-codes click here.

By using the above information, it is now possible to build the click tracker for Sizmek or DFP. In this example the click tracker will look like this:

http://clicktrackingv2.userreport.com/?xxx123456;

This click tracker is to be send to Sizmek, DFP or implemented directly to the system.

Below is an example of both impression and click tracking added directly to Sizmek.

Input below from DFP

To track clicks in DFP, Publisher has to use DFP click macro within the third-party code. So, the Publisher has to work with the creative providers and check for the correct placeholder for the click macro in the tag. Once the click macro is implemented in the tag, DFP will count the clicks accurately upon performing the click actions on the creative. I've implemented a sample code as a reference here:

<a href="%%CLICK_URL_UNESC%%http://clicktrackingv2.userreport.com/?XXX123456;https://www.audienceproject.com/" target="_blank">

<div style="width:728px; height:90px; position:absolute;z-index:100005">

</div></a>

<iframe height="90" width="728" src="https://storage.googleapis.com/gtech-pds-hyd/Brindha9/2017/August/Bold_728x90_111015.gif" frameborder="0" scrolling="no" allowTransparency="true"></iframe>

<img src="https://visitanalytics.userreport.com/hit.gif?t=XXX123456&event=click">

Input below from DCM

1) Re-write Audience Project ClickTracker to a redirect URL in this format (http://clicktrackingv2.userreport.com/?XXX123456;https://www.audienceproject.com/) - it is very important that this is the correct and final landing page that has been added to the redirect URL.

2) Add the redirect a the landingpage in DCM as if you would add the landing page on a creative.

NOTE:

- Normally you would add your own landing page on the creative and insert a ClickPixel via "Event Tags" in DCM, but this part is currently not working - hence this work around.

- It do become a bit more complex to handle the landingpages in DCM, since you will see the full redirect URL from AudienceReport when editing the landingpage.

Questions?

If you have questions in regards to creating click trackers, please do not hesitate to contact our support team at support@audiencereport.com

Attachments

Comments

Powered by Zendesk