Couple of weeks ago I had a play with getting server side GTM live for http://gtmrecipecontainers.com/ and thought it would be worth sharing a snapshot view of the process
For Google Analytics set-up I have the following:
1)GA for client
2)GA 4 for client
3)GA for client and server
1)GA for client
2)GA 4 for client
3)GA for client and server
This is how my Server GTM container set-up looks in addition you also need to set-up a Google Cloud project so you can set-up an app engine implementation
In the client GTM the Client and Server-Side GA tag got to add the end-point from the server-side GTM into the tags under transport URL which sends the hits to
Then the process is to activate an app engine within Google cloud using cloud shell. With me doing a test I only went for minimum and maximum of 1 server to keep the costs down.
One of the advantages of going server side you can use your own domain. Then I verified my domain under my hosting http://krystal.co.uk by a creating a txt record
Once I added the DNS records and went to preview mode in my server-side GTM this was what I was seeing
Checking on http://dnschecker.org I realised I had an additional DNS record 77.72.0.66 which was pointing in-correctly and causing an error when I was testing
Using a 1 server and my traffic being negligible my avg cost per day is £1.08 so in 12 days since launching my cost is £11.57 with a forecasted cost of around £35 for December 2020
Mini thread on how to stop server side GTM https://twitter.com/mrdipeshashah/status/1346531195358752773