When you want to add a cache buster to your tracking pixel, you need to use a cache buster that is compatible with your ad server. Below is a quick overview of how cache busters look and are implemented in different ad servers.
If you are using Double Click or Emedieate
When you are using Double Click or Emedieate as your ad server, your cache buster will be:
&ord=%n
or
&ord=[timestamp]
or
&ord=%%CACHEBUSTER%%
or
&ord=RNG
I.e. if your tracking pixel looks like this:
https://visitanalytics.userreport.com/hit.gif?t=100
The tracking pixel including cache buster will look like this:
https://visitanalytics.userreport.com/hit.gif?t=100&ord=%n
or
https://visitanalytics.userreport.com/hit.gif?t=100&ord=[timestamp]
The instructions for the Google Cachebuster Macro:https://support.google.com/dfp_premium/answer/1242718#cachebuster
If you are using Adform
When you are implementing your AudienceReport tracking pixel in the Adform, the Adfrom system will automatically add a cahce buster to the tracking pixel. Hence, in most cases you will not need to add the cache buster yourself.
If you need to implement the cache buster manually, the cache buster will look like this:
&ord=[timestamp]
The cahce buster should be implemented in the last part of the tracking pixel.
I.e. if your tracking pixel looks like this:
http://visitanalytics.userreport.com/hit.gif?t=100
The tracking pixel including cache buster will look like this:
http://visitanalytics.userreport.com/hit.gif?t=100&ord=[timestamp]
If you are using Sizmek
If you are using Sizmek, you just need to select that you want to use a cache-buster, when you are implementing your tracking pixel in the Sizmek system.
You should just select "Generate Random Number Instead of Token", under "Third-Party Tracking".
If you select the above mentioned feature, the cache-buster will be added automatically to your tracking pixel.
If you are using VideoPlaza or Freewheel
If you are using VideoPlaza or Freewheel, the cache buster you should use is:
&rnd=[timestamp]
I.e. if your tracking pixel looks like this:
http://visitanalytics.userreport.com/hit.gif?t=100
The tracking pixel including cache buster will look like this:
http://visitanalytics.userreport.com/hit.gif?t=100&rnd[timestamp]
If you are using Atlas (Facebook)
If you are using the ad server Atlas, the cache buster you'll need will look like this:
;cache=[timestamp]
I.e. if your tracking pixel looks like this:
http://visitanalytics.userreport.com/hit.gif?t=100
The tracking pixel including cache buster will look like this:
http://visitanalytics.userreport.com/hit.gif?t=100;cache=[timestamp]
If you are using AdTech
The cache buster in AdTech will look like this:
&rnd=_ADTIME_
I.e. if your tracking pixel looks like this:
http://visitanalytics.userreport.com/hit.gif?t=100
The tracking pixel including cache buster will look like this:
http://visitanalytics.userreport.com/hit.gif?t=100&rnd=_ADTIME_
If you are using Bidtheatre:
The cache buster in Bidtheatre will look like this:
&rnd={timestamp}
I.e. if your tracking pixel looks like this:
http://visitanalytics.userreport.com/hit.gif?t=100
The tracking pixel including cache buster will look like this:
http://visitanalytics.userreport.com/hit.gif?t=100&rnd={timestamp}
Testing the cache-buster:
You can easily test your cache-buster implementation tags either by saving the tag as an HTML file and opening locally or by using an HTML tag tester such as JSFiddle.net Fiddler or HTTPWatch allow you to see the exact cache buster and click tracker you are passing through when testing.
Learn more
If you want to learn more about how to implement a AudienceReport tracking pixel into your ad server, please click here.
Comments