Apple Intelligent Tracking Prevention (ITP) 2.x
Intelligent Tracking Prevention (ITP), is Apple’s initiative to protect Safari users’ privacy. The first release of ITP, which was in 2017, targeted the usage of third-party cookies. In fact, Apple blocked third-party cookies entirety, which in turn, caused a severe headache for ad tech and mar tech companies because third-party cookies are generally used for tracking visitors and collecting visitor data. Now, Apple is on the move to place limitations and restrictions on how first-party cookies are used within Safari.
These versions of ITP include the following restrictions:
Capped client-side cookies that are placed on the browser using the document.cookie API to a seven-day expiry.
Released February 21, 2019.
Drastically reduced the seven-day expiry cap to one day.
Released April 24, 2019.
What is the impact to me as an Adobe Target customer?
Apple ITP 2.1 and 2.1 impact Target in the following areas:
Potential increase of unique visitor counts
Due to the expiration window being set to seven days (with ITP 2.1) and one day (with ITP 2.2), you might see an increase of unique visitors coming from Safari browsers. If your visitors revisit your domain after seven days (ITP 2.1) or one day (ITP 2.2), Target is forced to place a new Target cookie on your domain in place of the expired cookie. The new Target cookie translates to a new unique visitor even though the user is the same.
Decreased lookback periods for Target activities
Visitor profiles for Target activities might have a decreased lookback period for decisioning. Target cookies are leveraged to identity a visitor and store user profile attributes for personalization. Given that Target cookies can be expired on Safari after seven days (ITP 2.1) or one day (ITP 2.2), the user profile data that was tied to the purged Target cookie cannot be used for decisioning.
Is my current implementation of Target impacted?
How can I mitigate the impact of ITP 2.1, ITP 2.2, and future ITP releases to Target?
To mitigate the impact of ITP 2.1, ITP 2.2, and future ITP releases to Target, complete the following tasks:
- Deploy the Experience Cloud ID (ECID) library to your pages.The ECID library enables the people identification framework for Experience Cloud Core solutions. The ECID library allows you to identify same site visitors and their data in different Experience Cloud solutions by assigning persistent and unique identifiers. The ECID library will be updated frequently to help you mitigate any ITP-related changes that impact your implementation.For ITP 2.1 and ITP 2.2, ECID library 4.3.0+ must be utilized for mitigation.
- Use Adobe’s CNAME and Enroll in Adobe Analytics' Managed Certificate Program.After installing the ECID library 4.3.0+, you can leverage Adobe Analytics' CNAME and Managed Certificate Program. This program lets you implement a first-party certificate for first-party cookies at no charge. Leveraging CNAME will help Target customers mitigate the impact of ITP 2.1 and ITP 2.2.If you are not leveraging CNAME, you can start the process by talking with your account representative and enrolling in the Adobe Managed Certificate Program .
As the industry makes strides to create a more secure web for consumers, Adobe Target is absolutely committed to delivering personalized experiences while meeting and exceeding the privacy expectations of visitors. Adobe Target has already announced support for Google’s SameSite Chrome Policies in addition to support for Apple’s ITP 2.1 and ITP 2.2.
As policies continue to evolve to protect our consumers, Adobe will also continue to support these initiatives in Target, while helping our customers provide the best-in-class personalized experiences.