ITP has been around for a while now. Introduced in June 2017, Safari’s privacy feature began cancelling any 3rd party cookies from being deposited on a browser by default. In March this year, Firefox introduced new privacy rules with the release of 66.0, and Safari came out with ITP 2.1 which also restricts 1st party cookies.
With 14 and 15% respectively, the combined hits generated by Firefox and Safari account for nearly a third of the internet. Blocking 3rd party cookies by default could therefore have a seismic impact on companies that rely on cross-site traffic measurement and retention analyses.
The technical consequences
ITP doesn’t only affect cross-site tracking – by drastically limiting the lifetime of first party cookies, it potentially prevents a user from being recognized from one session to the next.
This leads to distorted figures with an inflated number of unique visitors, audiences that do not reflect reality, and a complete fragmentation of conversion paths. In practical terms, on the basic indicators, session and new visitor figures are artificially inflated. In terms of allocation, ITP and especially ITP 2.2 have a bias in favour of free channels (less likely to include parameters in URLs) and contact points at the end of the several-day process (favoured by the limited cookie duration).
Firefox 66 has just introduced a pre-checked box in the new browser settings that automatically prevents the deposit of 3rd party cookies; while it’s private-browsing mode cancels all hits. Safari already blocked 3rd party cookies by default – its new rule now means that all remaining cookies that are not ITP compliant are deleted after 7 days.
User analysis and the ITP
To ensure that their traffic is not significantly affected by ITP, analysts today need to be able to rely on a powerful and high-performance analytics solution. Analytics tools will always be impacted by web browser evolution, especially with the increasing shift towards data privacy. However, it is possible to be fully privacy-compliant and still maintain a clear and detailed overview of your traffic. CDDC (Custom Domain Data Collection) is an AT Internet solution that collects and sends data directly via your own domain name (instead of AT Internet’s domain) so that tracking scripts are not disabled, making it possible to retrieve the majority of traffic lost due to ad blocker usage.
Another key to your analysis is identified visitors. By using identified visitor ids between your sites, you avoid spreading their information to external sites – you can therefore carry out cross-site analysis without affecting user privacy. This is the time to get visitors to subscribe to your sites.
In terms of 3rd party cookies, their days are numbered. For anonymised visitors, the domain structure will eventually need to be updated not just for analytics but for all resources. To stay ahead of the game, you can avoid the impact of ongoing restrictions by adjusting your measurements to ITP standards. Analytics solutions such as AT Internet already offer its customers ways to analyse anonymised visitors with ITP activated on the browser.
At the leading edge of the digital analytics market, AT Internet’s solution is fully aligned with the evolution of the major browsers. And CDDC is your perfect ally for handling ad blockers and matching the latest browser privacy requirements. Some of our customers have already recovered a significant amount of their traffic using CDDC – no need to worry about technical infrastructure on your end – AT Internet teams will put everything in place.
You can find more in our video on Custom Domain Data Collection, and the impact of ad blockers and ITP on web analytics tools: