Safari Intelligent Tracking Prevention Could Block Affiliate and Tracker Cookies (6)
Safari Intelligent Tracking Prevention Could Block Affiliate and Tracker Cookies
I'm not seeing anyone talking about this, but this could be a big hit to the affiliate, analytics and tracker industry https://webkit.org/blog/7675/intelli...ng-prevention/
There are a few implementation details I'm not 100% sure of. E.g. for now if a user interacts directly with a domain, then cookies are not blocked. The big question is does a redirect that sets cookies count as an interaction?
For now, I'm doing more research into exactly what this means. Worst case is that affiliate/tracker cookies last 24 hours at max or not set at all.
Without having the latest browser to test, it seems like on the tracker side, the problem is solved by hosting the tracker on the domain of the LP you are using. Still not sure of subdomains will count as 3rd party or not.
If subdomains count as 3rd party, this could make cloud hosted trackers less effective since the only real way to have it share a domain with the lp is to cname to a subdomain. Shared tracking domains are going to not work anymore for setting cookies.
In terms of timelines I'm guessing all of this will be live in September. Which gives some months to prep for the worst.
Looking to hear thoughts and interpretations from other "tech brains" on the forum.
Hmm, that's concerning.
[BIG EDIT - I found something more relevant]
Looks like this feature is actually live in Safari 11.0 - https://developer.apple.com/library/...fari_11_0.html
That means that it's likely to roll out next month according to MacRumours et al on Mac desktops.
It'll then land on iOS mainstream in September, as MrBaffoe says. However, the beta is apparently available now - http://bgr.com/2017/06/05/ios-11-bet...e-iphone-ipad/
Weirdly I can't find any commits in the GitHub mirror of the WebKit repo related to Intelligent Tracking Prevention. MrBaffoe/anyone else, can you find any commits that look relevant? If we can actually find the code in the repo that'd tell us a lot more.
Originally Posted by caurmen
K found the reference I think - https://twitter.com/groovecoder/stat...49376134774787
Webkit bug log https://t.co/loJYwSmaVx
And lastly have a look through this twitter user - https://twitter.com/johnwilander
Loads of info there about how blocking of cookies will work.
Nana, you're the first (and only) person I know about this from - first via the mailing and now here.
I think as long as you have a domain that sets its own cookie, it shouldn't be a problem. Third party cookies can be blocked - which other tools like Privacy Badger or Adblock do.
Subdomains should count as third party - a cookie set on www.stmforum.com is an absolutely different thing than a cookie set on stmforum.com.
I'm not sure how they would implement blocking of tracking cookies - how would this solution automatically tell the difference between a cookie that is useful for doing something on the site and a tracking cookie?
Maybe you can block cookies of some well known advertising and affiliate networks... I can imagine that.
it looks like the way they identify a tracking cookie is based on 2 factors - 1) its a domain your not interacting with (ie not submitting a form or clicking a link), and 2) the domain sets a cookie within a iframe on another domain (3rd party)
im running a test on ios11 to see how this works in practice will report back in a few days
Home > General > Affiliate Marketing Forum