Hello,
I’m exploring ways to bypass Safari ITP limitations and considering deploying tags via my own CDN. I also came across Stape’s Cookie Keeper:
Safari ITP Update Limits Cookies to 7 Days for Responses from 3rd-Party IPs
Would Cookie Keeper provide the same benefit, or does using a CDN have specific advantages from the perspective of browser restrictions?
Thanks!
Hello,
If you can set up an Own CDN, this is the best option for bypassing Safari ITP restrictions.
You can find a guide on setting up Own CDN here: https://help.stape.io/hc/en-us/articles/12348841204125-How-to-use-Own-CDN-on-Stape
And general information on methods to increase first-party cookie lifetime in this article: Prolong first-party cookie lifetime set by a third-party IP - Stape
Hello @Dmytro ,
Thank you for your response. I might not have the opportunity to set up an own CDN solution for some of my clients, which is why I’m curious if Cookie Keeper offers the same or similar benefits in terms of bypassing Safari’s restrictions.
Could you provide more details on that?
Thank you!
If you are no setting up your own CDN then set up custom domain and use stape cookie keeper as well. It will avoid safari’s ITP restrictions.
Cookie Keeper power-up performs the same functions, i.e. extends the first-party cookie lifetime, but in a different way the Own CDN. It works on the basis of a master cookie, which will restore the cookies you need.
Please refer to the article I provided in my last answer for more details on how it works and how to set it up on your Stape container.