You've started with your TAGGRS account and are ready to dive into the world of Server Side Tracking. After installing the TAGGRS tracking tags, you notice that you only see a blue (client side) or orange line (server side). This article addresses the most common reasons for this specific situation, organized from most to least frequent.
This list is compiled with general causes that may be relevant to every user. By systematically checking these points, you can usually identify and solve the problem quickly. If the points in this list do not resolve the issue, please send us a support ticket.
Let's step through the possible causes and their solutions to get you back on track as quickly as possible.
1. Container Not Published
The most common reason for not receiving data in TAGGRS is failing to publish one of the containers. Ensure that you publish both containers (the web container and the server container) when you are done setting up.
2. Both Tracking Tags Installed?
Check whether you have installed the tracking tags in both the web and server containers.
3. DNS Not Validated
Server Side Tracking works best on your own subdomain. If you chose this option in the setup process, always validate the DNS in TAGGRS. Do this by clicking the 'validate' button in the container. If it's not validated, you may only receive client side data in TAGGRS.
4. Google Tag Lacks 'server_container_url' Parameter
When installing the tracking tags, you use GA4 to send data to the server container. If you forget to set up the Google Tag (formerly GA4 configuration tag) correctly, the data will not be sent to the server container. Therefore, you will not see the server side line (orange) in the graph.
Therefore, add 'server_container_url' as a parameter and enter the subdomain you entered in the TAGGRS setup process.
Note! Don't forget https:// in front of the
5. SSL Error on the Subdomain
If the developer has accidentally changed something in the DNS settings, you may get an SSL error on the subdomain. If you are not using the enhanced tracking script, you will only collect client side data.
In this case, ask the developer to check if the DNS settings of your container still match the current settings.
6. 502 Error on the Subdomain
In rare cases, a 502 error may occur on the subdomain. When this happens, the server must be reinstalled. You can do this by making a change within your container, such as changing the container name. If this is not successful, please contact us.
7. Content Security Policy Blocks GTM or the Subdomain
To troubleshoot issues where a Content Security Policy (CSP) blocks Google Tag Manager (GTM) or the subdomain of your server-side container, update the CSP to allow the necessary domains and scripts. Add https://www.googletagmanager.com and https://subdomain.yourdomain.com to the script-src and connect-src directives of your CSP. Test the changes in a safe environment to ensure that GTM and your server-side container work correctly, and monitor your site for any CSP error messages after implementation.
View the Google Developers CSP Guide.
8. Duplicate Tracking with 'Ignore Duplicate Tracking' Enabled in Google Tag
The Google tag has a feature that prevents duplicate tracking. If there are duplicate tracking codes in the code, this setting can cause one of these tracking codes to be blocked. If you manage a Google Tag from GTM and have one in the code that sends data directly to GA4, the Google Tag in GTM may be seen as duplicate tracking.
In this case, it will be blocked and the Google Tag will not send data to the server container.
You can check this by going to the admin settings and selecting 'manage your Google tag', then disable the setting. Then test in preview mode to see if data is now coming through.
If this is the case, we recommend removing the other gtag script from the code and running all tracking through GTM.
9. Incorrect Trigger on TAGGRS Tracking Tags
If one of the TAGGRS tracking tags fails to fire due to an incorrectly configured trigger, it can disrupt data collection.
Solution:
- Verify Trigger Configuration: Check trigger conditions in Google Tag Manager (GTM) to ensure they match intended user interactions or page conditions.
- Test the Trigger: Use GTM's Preview mode to confirm the trigger fires correctly when conditions are met.
Right triggers:
Wrapping Up
These are the main reasons why you might not be tracking data. If your issue isn't listed here or if you've discovered another cause relevant to other users, send us a support ticket.