GTM server-side promises many benefits to Google Tag Manager users, developers and analysts. Some of which include:
And that’s just to name a few. So as you can see, this could potentially be really positive for your business. So in this article we wanted to show you how to set GTM Server-Side.
1.1. Find your Account in Google Tag Manager.
1.2. Click on Create Container
1.3. Add your domain.
1.4. Select Server.
1.5. Click Create.
1.6. Accept the terms and conditions.
You can now see the default Workspace of the SERVER container.
Remember the container settings. It’s important in setting up the server later on.
2.1. Click on the Admin tab on the upper left.
2.2. Then click on Container Settings.
2.3. There’s an empty field there called Server container URL. Remember this field later on.
2.4. Under Tagging server, click on the Set up your tagging server button.
2.5. Once inside, select Manually provision tagging server.
Note: It’s recommended to use manual provisions because if you have an existing Google Cloud project, you override or erase the existing App Engine in that project. Manual provisions avoid project management headaches. See the “Creation of Google Cloud Platform” section of this article for more details.
Take note of the code under Your Container Config. This is needed for the Google Cloud Server we saw earlier. Go to Part 2, section 2.7 to add this Container Config.
3.1. Under the newly created SERVER container, go to Clients.
The ‘clients’ section is the most important part and it is unique to gtm server-side tagging. As a default, UA and GA4 are already set up. There are actually no other changes that you need to make here.
Take note of the Client name of Universal Analytics and Google Analytics 4. You need them when setting up tags later on.
3.2. Go to Variables.
3.3. Once inside, select Configure.
3.4. Once inside, select and tick every one of the Built-In Variables. The most important variable here is ‘Client Name’. This is related to the Clients we saw earlier.
Let’s create the Universal Analytics Tag and Google Analytics 4 Tag. First I’ll show you how to set up the UA tag.
3.5. Go to Tags.
3.6. Click on New.
3.7. Name your tag. Then click on the Edit icon.
3.8. Select Google Analytics: Universal Analytics.
3.9. You don’t change anything on the settings. Leave everything as is.
3.10. Under Triggering, click on the edit icon.
3.11. Click on the add a trigger button.
3.12. Name your trigger. Click on the edit icon button to configure the trigger.
3.13. Select Custom
3.14. Then select Some Events.
3.15. Change the parameters as follow:
Client Name > Contains > Universal Analytics
3.16. Click on Save.
You need to do the same thing for the Google Analytics 4 tag.
3.17. Go to Tags.
3.18. Click on New.
3.19. Name your tag. Then click on the Edit icon.
3.20. Select Google Analytics: GA4.
3.21. You don’t change anything on the settings. Leave everything as is.
3.22. Under Triggering, click on the edit icon.
3.23. Click on the add a trigger button.
3.24. Name your trigger. Click on the edit icon button to configure the trigger. We suggest (GA4 Trigger).
3.25. Also, choose the trigger type. Select Custom.
3.26. Then select Some Events.
3.27. Change the parameters as follow:
Client Name > Contains > GA4
3.28. Click on Save.
Once everything is good to go, don’t forget to Publish the server container.
1.1. Go to https://cloud.google.com/
1.2. Click on Select a Project on the upper left.
1.3. Click on NEW PROJECT.
1.4. Give your project a Project name, Project ID, and Location.
NOTE: It’s better to create a new Google Cloud project because if you have an existing one, you override or erase the existing App Engine project. Creating a new project prevents any data loss or any project management headaches.
2.1. Once the project is created, click on the Activate Cloud Shell icon.
For sanity checks, make sure you are working on the correct project. The project ID you inputted should be the same as the one you see inside the cloud shell console.
2.2. Next, copy the code from the Google documentation, and paste it into the console:
bash -c "$(curl -fsSL https://googletagmanager.com/static/serverjs/setup.sh)"
2.3. Press Enter.
2.4. Select Authorize.
2.5. Press Enter to continue as instructed.
2.6. Container Config (Required): appears.
2.7. Go back to your GTM server-side container settings and copy the Container Config code.
NOTE: Further down this article there’s a section on where to find this Container Config.
2.8. Policy Script URL (Optional) appears.
2.9. If you have Policy Script, add the URL then enter. Otherwise, you may leave this empty and just press enter. This is Optional.
2.10. Request Logging (Current: on/off) appears.
2.11. Type off for now and press Enter
2.12. Deployment Type (testing/production) appears.
2.13. Type testing then press Enter.
NOTE: Deployment type production begins the billing of your Google Cloud project (100 EUR). In summary, production requires technical expertise on how to handle server instances and logs. But for now, we can start with testing. Consult with a Google Tag Manager agency to learn more.
3.1. Look for App Engine or search for Custom Domains.
3.2. Select Settings, then select Custom Domains, then select Add a Custom Domain.
3.3. Under Select the domain that you want to use, select Verify a new domain. Then under the next field, add your domain.
3.4. Click on the blue Verify button.
3.5. You’re redirected to a new tab.
3.6. Select the server you are using.
3.7. A TXT record appears for DNS configuration. Send this to your web developers if you don’t know what to do here. They should know what to do with it.
3.8. NOTE: When uploading the DNS records, you need to decide the subdomain for your server-side instance for Google Tag Manager. An example is data or sgtm or ss. In the end, your server-side endpoint might look like the following:
3.9. After the TXT DNS record has been added to your server, click on the Verify button.
3.10. Go back to Google Cloud. Click on Refresh domains.
3.11. Under Point your domain to gtm-xxxxxxxx-xxxxx: close (click x button) on the www.sgtm.domain.com. Only one subdomain should be mapped.
3.12. Click on Save mappings, and then Continue.
3.13. Under ‘Update your DNS records to enable security’ are the A and AAAA records. Send these to your web developers, they should know what to do with them.
3.14. Click on Done.
3.15. Wait until mapping is completed. Best not to close the browser tab. This includes SSL certification.
3.16. Endpoint should be responding once completed. To check, go to the endpoint. For example, sgtm.domain.com/healthy
3.17. You’ll see an ‘ok’ text on the screen if everything is implemented correctly.
1.1. Go to your Google Tag Manager WEB container. Note that you should already have Google Tag Manager set up already.
1.2. Go to Variables
1.3. Create a new User-Defined Constant variable for your server-side endpoint.
NOTE: Include the https://. A mistake in setting up GTM server-side tagging is NOT including it. Without it, the HTTPS requests are misconfigured.
2.1. Go to your Universal Analytics pageview Tag.
2.2. Under your UA pageview tag, go to More Settings. Then go to Transport URL.
2.3. Add in your constant Variable that represents your server-side endpoint.
2.4. Click Save. Your current Universal Analytics pageview should be good to go.
2.5. Look for your GA4 (Google Analytics 4) pageview tag. Do the same.
2.6. Under your GA4 pageview tag, look for and tick Send to server container. After which, add in your constant Variable that represents your server-side endpoint.
2.7. Click Save. Your current Google Analytics 4 pageview should be good to go.
2.8. Publish the WEB container.
For this section, we’ll look at how to debug the GTM server-side container if everything is working or configured properly.
1.1. Go to your Server container.
1.2. Click on Preview.
2.1. You have landed on the debug view.
2.2. Go to your website on a separate tab. This allows a pageview hit.
2.3. Go back to the debug view and you will see HTTP requests on the server container.
If everything is configured properly, the tags are fired. This means that pageview hits from the website are sent to the server, then sent to respective vendors in this case it’s Google Analytics.
Note that it might be different in your containers if the naming is different. Any custom HTTP request hits also get reported in the debug view.
This is only the basic setup of GTM server-side tagging. There is custom tracking like sending IP addresses and other custom HTTP requests. To learn more about robust GTM server-side tracking, consult with Google Tag manager experts and contact us today.