Server Side Analytics: No Requests Coming In

You've set up an account with TAGGRS and eagerly started with Server Side Tracking. After implementing TAGGRS tracking tags, you notice no data coming in. This article addresses the most common reasons for missing data in your TAGGRS dashboard, ranked from most to least likely.

This list covers general causes applicable to all users. By checking these points, you can often quickly identify the source of the issue. If the solutions mentioned don't resolve the problem, don't hesitate to submit a support ticket.

Let's walk through the possible causes and how to effectively address them step by step.

Let’s get started...

The most common reason for not receiving data is failing to publish the containers. Ensure you publish both containers (the web container and the server container) once you've finished setting them up.

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 you haven't correctly processed the DNS settings and are using TAGGRS's enhanced tracking script, no data will come into the account.

Even after validating the DNS and publishing the GTM containers, data might still not come in. A reason could be the lack of tracking codes installed on the website. You can use two methods for this:

- The regular tracking script from GTM, found by clicking on your container ID in the web container. A container ID follows this format: GTM-1234

- The enhanced tracking script from TAGGRS

Need help? Check our explanation of the enhanced tracking script.

If you opt for the enhanced tracking script, there's an extra step to correctly send the data: Adding a web container client in the server container. This is again explained in this blog.

If a developer accidentally changes something in the DNS settings, you might get an SSL error on the subdomain. This look like this:

This error only causes a complete loss of data if you've also installed the enhanced tracking script. In this case, ask the developer to check if the DNS settings of your container still match the current settings.

You can also check it yourself by going to mx toolbox, then selecting DNS Lookup, entering your subdomain, and you will see the DNS settings of your subdomain. Make sure the IP Address (A type) matches the one in the TAGGRS Dashboard. The IPV6 Address (AAAA type) should be empty. If this is not the case as in the example below, you will need to remove them within your hosting. This varies by hosting. Therefore, you will need to contact your hosting provider. 

To fix issues where a Content Security Policy (CSP) blocks Google Tag Manager (GTM) or your server-side container's subdomain, 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 GTM and your server-side container work correctly, and monitor your site for any CSP errors post-implementation.

More info? Check out the Google official documentation.

Google Tag has a feature to prevent duplicate tracking. If duplicate tracking codes are in the code, this setting might block one of them. If you manage a Google Tag from GTM and have a code directly sending data to GA4, the Google Tag in GTM might be seen as duplicate tracking.

In this case, it will be blocked, and the Google Tag won't send data to the server container.

Check this by going to ‘manage your Google tag’ in the admin settings and disabling the setting. Then test in preview mode to see if data now comes through.

If it does, we recommend removing the other gtag script from the code and managing all tracking via GTM.

These are the key reasons you might not be tracking data.If you have discovered another cause relevant to other users, send us a support ticket.