Enhanced Tracking Script - Errors and Solutions

Implementing TAGGRS's Enhanced Tracking Script can significantly improve data accuracy and privacy compliance. However, users may encounter certain issues during setup. This guide provides detailed solutions to these common problems, ensuring a seamless integration of the Enhanced Tracking Script.

This list provides universal reasons that apply to all users. By reviewing these items, you can typically pinpoint the root of the problem swiftly. Should the outlined resolutions not rectify the issue, please feel free to reach out by submitting a support ticket.

We'll guide you through potential causes and demonstrate how to tackle them systematically.

Error by adding the GTM code from TAGGRS

Should you come across any of the errors listed below while integrating the GTM code, rest assured—the code will remain functional!



400 Error in the console when adding the Enhanced Tracking Script

Seeing a 400 error in the console typically indicates a missed step in establishing client creation within the server container, an essential phase in configuring the Enhanced Tracking Script.


Duplicate Google Tag Manager code in the console, affecting data accuracy

When using the Enhanced Tracking Script, there is no need to maintain a huide Google Tag Manager code. This is because then two different tag managers - the old one and the Enhanced Tracking Script - are loaded at the same time. To solve this problem, the original GTM code should be removed after activating the Enhanced Tracking Script. Only the GTM code of the Enhanced Tracking Script remains.


Debug Mode No Longer Functions in the Server Container

If the debug mode in the server container ceases to function, resulting in error messages, verifying the container ID used is crucial. A common mistake involves using the server container ID instead of the web container ID. This prevents Google Tag Manager from establishing a connection, rendering the preview mode inoperative.


Adding the Enhanced Tracking Script Results in Complete Tracking Halt

Reaching the request limit (TAGGRS Dashboard) can cause Tag Manager to pause and tracking to halt. It is vital to understand that after implementing the Enhanced Tracking Script, exceeding the request limit will interrupt tracking functionality. Monitoring and managing the request limit is therefore crucial to ensure continuous tracking.request limit has been reached taggrs dashboard

These are the main errors and solutions for the TAGGRS Enhanced Tracking Script. If your issue isn't listed here or if you've discovered another cause relevant to other users, send us a support ticket.