The latest in Apple’s Intelligent Tracking Prevention (ITP) saga has just dropped. It may not seem like a huge update, but make no mistake — it is significant, and, to some, it will be a doozy.
In a blog post, Apple outlines two changes to ITP that have even more implications for how advertisers track across the web:
- Full Third-Party Cookie Blocking
Cookies for cross-site resources are now blocked by default across the board. This is a significant improvement for privacy since it removes any sense of exceptions or “a little bit of cross-site tracking is allowed.”
- Cookie 7-Day Cap on All Script-Writeable Storage
… Now ITP has aligned the remaining script-writable storage forms with the existing client-side cookie restriction, deleting all of a website’s script-writable storage after seven days of Safari use without user interaction on the site.
In a nutshell, this means:
- Third-party pixels are now officially, completely dead on iOS devices. They simply will not work in any circumstances, full stop.
- The local storage workaround for this is now capped to a 7 day window. (Meaning that if the user goes more than 7 days between when a click puts a user on the site, and them going back to the site, attribution gets snapped at that point.) It means that the max attribution window for mobile web offers is now 7 days.
Does this change soften our stance on the JavaScritpt SDK, what’s known as our cookieless tracking solution, as the preferred tracking method? Nope. It’s still way better than pixels (which just flatly won’t work here). The ultimate recommendation is postbacks, but not everyone can support that.
Apple’s most recent Intelligent Tracking Prevention updates:
- ITP 3.0 (the subject of this post, which some people are calling “ITP 3.0,” even though the 3.0 is not part of its official name)
- ITP 2.3
- ITP 2.2
- ITP 2.1
- ITP 2.0
While complicated, postback tracking has always been the most reliable, future-proof way of tracking conversions across the internet and mobile apps. Which is why we’ve recommended postback tracking from the beginning.
We understand that not everyone has the technical resources or grit to implement server-side tracking methods, such as postback tracking. However — and I cannot stress this enough — the time for that reasoning or excuse is quickly changing. Soon, companies and individuals like you will have to make a decision: dedicate yourself to learning server-side tracking, hire somebody who knows how to master postback tracking, or get left behind.
As always, feel free to drop us a line with any questions or comments.
Becky is the Senior Content Marketing Manager at TUNE. Before TUNE, she led a variety of marketing and communications projects at San Francisco startups. Becky received her bachelor's degree in English from Wake Forest University. After living nearly a decade in San Francisco and Seattle, she has returned to her home of Charleston, SC, where you can find her enjoying the sun and salt water with her family.