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?
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
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?
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: