Marketeers' challenges with Intelligent Tracking Prevention (ITP)
ITP is a privacy feature used by Apple’s Safari browser since 2017. It was established to protect users’ online privacy, by limiting the ways advertisers and site owners can track users across domains to personalize content and advertise. This is intended to ensure that users only have long-term persistent cookies and website data from the sites with which they regularly interact, and tracking data is removed proactively as they browse the web.
Google have also announced a similar feature that they intend to phase in over the coming two years, as well as Firefox, who currently have the ETP privacy feature.
How does ITP work?
Any websites that load scripts or images across domains are classified according to a machine-learning algorithm, and cookies that those sites deposit are essentially sectioned off — preventing them from tracking the user 1 – 7 days after they first interacted with the site. The time range here is significant:
Only third-party cookies with cross-site tracking capabilities, loaded via another domain, are purged after one day. However, if the user interacts with a domain directly, often referred to as a first-party domain, Intelligent Tracking Prevention considers it a signal that the user is interested in the website and will allow the cookies to be loaded in a first-party context for 7 days, after which they too will be purged if there is a lack of activity.
It seems ITP is the solution we’ve been waiting for?
Well, ITP and its ever more restrictive iterations over the past few years are making the lives of marketeers difficult. We explain why below:
Why does it matter for marketeers?
Currently, the default expiration length for the Adobe Analytics and Google Analytics cookies is 2 years. This means that you could visit a site on 11/12/2020, and a cookie will be set with an expiration of 10/12/2022. You could have zero interactions with the site for one year and 364 days, but when you return on that 365th day, Adobe Analytics and Google Analytics would recognize you as the same user that was on the site on 11/12/2020.
How does ITP impact this?
If you were to use Safari to visit the same site on 11/12/2020, and there aren’t any interactions with the site for seven days, the cookie will be destroyed. This means that should you visit the site on 19/12/2020, you’ll be identified as a completely new user.
These cookies are how Adobe and Google identify a user who visited your site last month via Google, as the same user visiting this month via Facebook, as the same user six months ago via a double-click ad, so not having them present on the browser results in a whole host of consequences to your marketing metrics, such as not being able to determine your conversion rate for any one particular channel, or not being able to put an accurate figure on the cost of each conversion. Advertising is also adversely impacted due to users falling out of your remarketing audience rapidly if they aren’t exposed to another ad to renew the cookie’s expiration date.
What can you do?
Google Tag Manager Server– Side is a recent development, which allows for the hosting of a server-side GTM container. In that container, Google Tag Manager gets data from the client-side tracking codes, processes it, manipulates it, and then sends it to any 3rd party vendors you’re working with. This is in contrast, of course, to this happening in your users’ browsers.
This brings a number of benefits – one of which is that ITP’s aforementioned cookie expiration limit of between 1 and 7 days can be avoided when the cookie is stored from the server-side.
Therefore, whilst GTM Server Side is certainly a development that should be of interest to marketeers looking to tackle ITP, it doesn’t come without its share of technical drawbacks, such as the inability to continue providing data to third-party vendors. It is also important to point out that this only works with Google cookies, and organizations tend to use a combination of tracking tools. Using Server-Side tagging as the only solution to ITP can create further issues for your organization regarding capturing consent; compliance requirements for regulations such as GDPR will not be met.
Cassie’s Identity Service
Here at Syrenis, we have developed an innovative solution for organizations feeling the effects of ITP on their online marketing. Cassie’s Identity Service has been built specifically to support companies who wish to maintain and persist the consent that their visitors have provided. This persistent feature regenerates the cookies and critically the identifiers by storing their users’ cookie consents, or indeed the actual cookie scripts themselves, in Cassie’s centralised platform. Regardless of whether these cookies have been categorised as first or third party, Cassie’s identity service will assign each anonymous visitor to your site a unique identifier and create a record of the consent provided for each cookie loaded to that user’s browser. Should that particular individual revisit the site at a later date, Cassie will recognise the visitor based on their unique identifier and regenerate the purged cookies.
This innovative solution simply delivers the consent that the visitor originally made. It is compliant and ethical and resolves the inaccurate attribution data caused by ITP. The solution has a low-tech stack allowing you to use your existing solutions so is quick and easy to deploy. With the support of our experienced project management team, who have successfully rolled out Cassie’s Identity Service for many clients, you can defend yourself against ITP’s impact on their online marketing efforts.
See how Syrenis can help.
If you’d like to see how ITP will impact your organization you can use our ITP Calculator by clicking here.
Alternatively reach out today to schedule a demo of Cassie and discover how we can help your marketing team tackle ITP.