Rich-text Reply

Plans for tackling Safaris upcoming ITP 2.1 standard

lkraav 03-08-19

Plans for tackling Safaris upcoming ITP 2.1 standard

Hey guys, As you know, Safari will soon cap the client side cookie duration at 7 days with ITP 2.1 ( https://webkit.org/blog/8613/intelligent-tracking-prevention-2-1/ ). Do you guys have a workaround in place for this?
--
Leho, marketing & tech architect | G+: lkooglizmus@gmail.com
Level 4

JasonDahlin 03-08-19
 

Re: Plans for tackling Safaris upcoming ITP 2.1 standard

[ Edited ]

Today, clearing cookies does cause the user to rebucketed (even though localStorage still has all the info from my previous optimizelyEndUserId value and now the new one too)

 

Potential issues:
1- Over time locaStorage could get full.

2- We are contracted for a certain number of visitors. If cookies get erased, they count as a new visitor

3- In long running tests, only high-value frequent shoppers will actually stay in one variation the entire experiment

(mostly just commenting so I can be sure to get their reply)

--Jason Dahlin
Analytics and Testing Guru Smiley Happy


Experimentation Hero
CouchPsycho 03-13-19
 

Re: Plans for tackling Safaris upcoming ITP 2.1 standard

I think, this is an issue for the optimizely dev teams to solve the case @JasonDahlin mentioned. If cookies are limited to 7 days, experimentation will not work for us anymore. Our conversion latency is about 35-40 days.

 

There is no official info from optimizely?

Kind regards

Michael