All Console Errors and Solutions

After implementing Server Side Tracking via TAGGRS, you get errors when opening the console in the browser. Don't panic, often these errors are harmless or easily fixed.

Discover in this support article all situations and solutions for console errors after implementing our software.


When you get the ERR_BLOCKED_BY_ORB 200 Error in the console it means that our TAGGRS Tracking Tags pixel is blocked by tracking prevention. As you know, pixels (third party cookies) are going down due to browser prevention and regulations. When TAGGRS Graphs about extra data due to server side tracking, a pixel is used via the web container. When you see ERR_BLOCKED_BY_ORB 200 it means it is being (partly) blocked.

This has no impact on your tracking, this is purely the extra data graph!


2. 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!



3. 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.


4. 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.


5. 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

6. No Request in Server Container on Magento 2

Encountering no requests in your Magento 2 server container for Server Side Tracking? This often results from Magento's CORS rules, designed to block outgoing requests as a security measure. To fix, adjust your .htaccess with Header add Access-Control-Allow-Origin "https://*", replacing "https://*" with your subdomain, thus ensuring your requests are allowed. Check our Magento 2 No Request support article.


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