Hi Community,
it looks like new WebKit update restricts the expiration period of cookies set by 3rd-party A/AAAA DNS server to max. 7 days.
Are there any ways to avoid this new restriction with server side GTM? Is it possible to deploy GTM s2s on your own server?
it looks like new WebKit update restricts the expiration period of cookies set by 3rd-party A/AAAA DNS server to max. 7 days.
Yes. Thatâs correct. More info here: Safari ITP update limits cookies to 7 days - Stape
Are there any ways to avoid this new restriction with server side GTM?
We were ready for this update. To avoid restrictions, you can utilize our new power-up âCookie keeperâ. It will restore missed cookies. This week we will publish a detailed guide on how to use it.
Also, we are preparing additional power-ups that will help to avoid this restriction.
Is it possible to deploy GTM s2s on your own server?
Yes. We propose the option âStape on own serversâ. You can contact our sales using âContact salesâ button. I need to say this is quite pricy 
Server-side hosting pricing - Stape
Hello,
You can use the Stape Power-Up Cookie Keeper. It will recover the user cookie based on the user id you need to set in the user cookie from your server.
If you use Shopify - you can simply install the Stape app for this: Stape Server GTM - Set up server-side Google Tag Manager container in a few... | Shopify App Store
The same applies to Wordpress: GTM Server Side â WordPress plugin | WordPress.org
Hi Denis!
Thank you for the quick response!
Could you please provide the link to GitHub with Cookie Keeper code?
This is it?
Thatâs not a tag. Thatâs power up for sGTM.
If you use Stape hosting for sGTM, you can utilize it.
If you use another hosting, it will be pretty hard to implement a similar approach as it requires some Database and logic of storing/restoring cookies. However you can try to implement this using Cookie Restore Tag
Hello,
I am trying to activate Cookie Keeper Power Up, but when I click Save Changes nothing happens. (on Chrome)
Any idea if this is a temporary bug?
Thanks!
Changes not saving?
Logic is similar to the Anonymizer power-up. If you change something, click save. Thatâs it. Nothing else will happen.
Here is a video. (updated link)
Also tried with clear cache, same thing, settings are NOT saved.
Hi Dennis,
Can you elaborate a bit on how to use this. When I have enabled it I get more options in âWeb GTM code settingsâ:
Do I need to set the user identifier myself from my own site/server (which will not be blocked by ITP). In that case I suppose I would need to set a HttpOnly cookie with the user ID on .mydomain.com (when having server side GTM/Stape on sgtm.mydomain.com)? In the case of the image above the name of that cookie would need to be âuser-identifier-cookieâ and I would need replace my client side GTM code with the code generated as a result of the values in the image above?
Thanks
Hello @soerendam_rm
You understood it exactly right, that cookie that you will be setting (not falling under ITP) would be used as a master cookie to restore those that youâll list. It does not need to be named exactly âuser-identifier-cookieâ - you can pick a name just make sure to plug it correctly into the snippet generator.
One small amendment: that cookie should not be a HttpOnly, it needs to be set from the server response, but httpOnly should be set to false, so that we can access that cookie with JS.
Weâve just recently published an article on the Cookie Keeper, I suggest you check that out:
Hey @Alin_Tatarca
As far as we can see all of setting are applied, and the power-up is on. Could you please re-confirm that?
Yeah, after further investigation, it seems that a Chrome Extension was the problem. So now everything is back to normal with the power-up.
Thanks!
