You may be aware that Firefox 22, that is due for release in June 2013, was planning to block third party cookies by default. Third party cookies are those set by a different domain to the one that the user is visiting at the time and have a range of applications including including analytics solutions. In these instances, if the user visits www.coolshop*.com, which uses an analytics package from hitstats*.com, Firefox 22 will by default, block the cookies from hitstats*.com.

Thanks to Webgainsí cutting edge Device Tracking technology, this change will not impact any Webgains publishers or advertisers as long as a few basic guidelines are followed.


What do I need to do?
If you donít have any kind of additional tracking logic or conditions in place that determine when to execute the Webgains tracking code, you donít need to do anything.

What if I use additional logic?
In some instances, the Webgains tracking code will only be firing conditionally, based on predefined criteria. This is likely to be the case for advertisers who are on more than one network, those who are deduping against other channels, and those who are using some kind of container tag or tag management system examples of which include TagMan, BrightTag, Qubit OpenTag and Google DoubleClick. In order to ensure that the implementation of these tags continues to work as normal, you should speak with your provider to ensure that the logic used is first and not third party.

If you follow the guidelines above, there should be nothing more you need to do. If however you do have any other questions or would like to discuss this, please donít hesitate to contact your account manager.


Below is a list of FAQs which should tell you everything you need to know. If however you do have any other questions or would like to discuss this, please donít hesitate to get in contact.

How will the change affect my links Webgains links?
As well as other tracking methods, our click tracking uses first party cookies, therefore clicks will not be affected.

What about postview tracking?
For postview tracking, publishers will need to ensure that when using Webgains tags, they choose the JavaScript option (not the HTML or HTML/JS mixed tag). To help avoid any errors, moving forward it will only be possible within the Webgains platform to select the JavaScript tag for postview enabled creative. Additionally, JavaScript will be set as the default for all tags.

Our advice to publishers is to always use JavaScript tags if you are unsure.

For publishers who have already implemented HTML or mixed tags, these will need to be switched to JavaScript. If you are unsure, please contact

What about advertisers using additional tracking logic?
We are working closely with advertisers to ensure that they are aware of the issue and that any additional tracking logic used is first rather than third party. If you have questions about a specific advertiser, please contact your account manager or the advertiser directly.

What about tracking commissionable events?
Firefox will only block the writing of new cookies with the reading of existing cookies unaffected. In addition, even if cookies fail, our Device Tracking will ensure that your transaction is still tracked successfully.

If you have any other questions, please do not hesitate to get in contact either on