TAGGRS Debug Series

Have you installed the tracking tags, but no requests are coming in? This can have several causes.

Ready to resolve this situation? Click the button below for a detailed explanation.

You have created an account with TAGGRS and started with Server Side Tracking. After configuration, the requests are coming in, but you notice a spike in the statistics on the TAGGRS dashboard.

In this article, we explore the most common causes of spikes in the request graph.

If no graph is visible in your TAGGRS dashboard, the TAGGRS Tracking Tags may not be installed. These tags collect and visualize your data.

Want to know how to install these tags? Click the button below for a guide.

You have installed the tracking tags, and the message 'data is being collected' remains for more than 5 minutes. This can have various causes.

View the corresponding article for possible reasons.

Do you notice a negative difference in your data after implementing TAGGRS Tracking Tags? This may indicate discrepancies in data collection.

Click the button below for more information and solutions.

After installing TAGGRS Tracking Tags, no web or server line is visible. This can have multiple causes.

Click the button below for the solution.

You notice an upward trend in your measured data. Do you want to further optimize this and achieve better results?

View the article for tips to increase this difference. Click the button below for details.

After installing the TAGGRS tracking tags, you notice an unrealistically high data discrepancy of more than 60%.

View the article for the main causes. Click the button below for more information.

Have you set up the Tracking Tags but do not see any additional events appearing (or only Page_View)?

View the article for possible causes and solutions. Click the button below for more details.

Have you seen an increase in Unassigned (not set) traffic in Google Analytics after implementing Server Side Tracking? We have the solution.

View the article for the causes and how to resolve this.

If you do not set up Consent Mode (V2) correctly, it can lead to the loss of valuable data, as tags are not activated when cookies are declined.

With a correct setup of Consent Mode (V2), you can still collect valuable data, even without full cookie consent.

Here you will find solutions for error messages during debugging in the server container after all tags and triggers have been configured.

View the article for causes and solutions.

Failure to set up Consent Mode (V2) properly can result in the loss of a lot of valuable data. This is often because when a visitor does not agree to certain cookies, the related tags are not activated.
If you set up Consent Mode (V2) correctly, you can still access valuable data even without full consent for the cookies.

Not receiving a request on the server and have a Magento website? This is often due to Magento's CORS rules, which block outgoing requests as a security measure.

View the article for causes and solutions.

Has the number of Google Ads Remarketing audiences decreased after implementing Server Side Tracking or Consent Mode V2?

View the article for causes and solutions.

After implementing Server Side Tracking via TAGGRS, error messages may appear in the browser console. These errors are often harmless or easy to resolve.

View the article for possible error messages and solutions.