Install the Enhanced Tracking Script

The TAGGRS Enhanced Tracking Script is a direct drop-in replacement for the standard Google Tag Manager script. It defends against ad blockers and Intelligent Tracking Prevention (ITP) using advanced masking techniques, making your tracking signals unrecognisable to even the latest blocking filters. This way, more data gets through, your dashboards stay complete, and your ad platforms can optimise properly.

This guide walks you through the easy implementation of this script, so you can quickly improve the reliability of your tracking across all major browsers.

Important
The Enhanced Tracking Script replaces your existing GTM script. Do not run both simultaneously.

Key features

Resist ad blockers by masking the GTM script and encrypting event request paths before they reach the server-side container
When combined with the correct server-side setup, helps improve cookie resilience on ITP-restricted browsers such as Safari
Increases the volume of events captured by GA4 and ad platforms even from users with ad blockers enabled or privacy-focused browser settings active

Privacy note
The Enhanced Tracking Script is intended to improve consented measurement, not to track users against their choices. Keep consent handling, privacy policy transparency, anonymization, and PII controls in place.

Prerequisites

An active TAGGRS account with a configured product
Your GTM web container ID (format: GTM-0000000)
Access to edit your website's <head> and <body> code

Configuration

Configure your settings in the TAGGRS dashboard

Open your TAGGRS product and navigate to Features → Optimize → Enhanced tracking script.

The Enhanced Tracking Script is part of the Features tab, Optimize section in the TAGGRS dashboard.

Make sure to fill in your container's GTM code (e.g. GTM-0000000), toggle the Maximize your performance option on, and click Save.

Adding Configuration Parameter to Google Tag in Web Container

Implement the Enhanced Tracking Script codes on your website

After saving, scroll down to 2. Implement Tracking Codes. You will find two snippets to add to your website.

Head code

Copy the Head code and paste it as high as possible inside the <head> tag of your website.

Body code

Copy the Body code and paste it as high as possible inside the <body> tag of your website.

Publish and verify

Save your changes in your CMS or code editor.
Open your website and right-click anywhere on the page.
Select Inspect → Elements and search for any part of the Enhanced Tracking Script to confirm it is present. Then open the Network tab and verify that tracking requests are reaching your server-side container.
Check the TAGGRS Analytics dashboard and confirm that requests appear under the Enhanced Tracking Script category.

Setting up a GTM server container client

Go to your server container in Google Tag Manager.
In the left-hand menu, select Clients → New.
Under Client Configuration, select Google Tag Manager Web Container as the client type.
Under Allowed Container IDs, add your GTM code (the same GTM-0000000 you used in the TAGGRS dashboard)
Save your settings, then submit and publish your updated containers to activate the Enhanced Tracking Script.

Expert insight
The Enhanced Tracking Script does not replace Server-side Tracking. Its main benefit is that more eligible events can reach the server-side container, because the browser-to-server request is protected before blockers can match common tracking paths. Direct browser requests to third-party endpoints may still be blocked.

Troubleshooting

Error when adding the GTM Code in your CMS

Symptom: Validation errors or script injection warnings appear when adding the script in your CMS (e.g. WordPress).
Cause: CMS security or validation rules flagging the script.
Fix: These warnings can safely be ignored. The Enhanced Tracking Script will continue to function correctly. Only investigate further if tracking is visibly broken after publishing.

400 error in the Browser Console

Symptom: A 400 error appears in the browser console after adding the Enhanced Tracking Script.
Cause: No Google Tag Manager Web Container client has been created in the server container, or the wrong container ID was used.
Fix: Verify that a Google Tag Manager Web Container client exists in your server container. Add the same GTM web container ID that you entered in the TAGGRS dashboard under Allowed Container IDs. The server container ID should not be used here.

404 error in the Browser Console

Symptom: After enabling the Enhanced Tracking Script (and optionally the additional data capture beta feature), the browser console shows the following error:
‍GET

https://pagead2.googlesyndication.com/
dfp.min.js

Cause: This is the expected behaviour. The TAGGRS Enhanced Tracking Script probes for the presence of dfp.min.js, a known ad-serving resource, to detect whether the visitor has an ad blocker active.
Fix: No action is required. This error does not indicate a misconfiguration or a problem with your tracking setup. It's a passive detection mechanism and has no negative impact on your data collection or the functioning of the Enhanced Tracking Script.

Duplicate GTM Script Detected

Symptom: The browser console shows duplicate GTM scripts, causing inflated or inaccurate data.
Cause: Both the original GTM snippet and the Enhanced Tracking Script are loaded at the same time.
Fix: Remove the original GTM snippet from your website.
Keep only the Enhanced Tracking Script active.
Running two GTM instances simultaneously will negatively affect data accuracy.

Preview mode no longer works in the server container

Symptom: GTM preview/debug mode fails or shows connection errors in the server container.
Cause: The server container ID was used in the Enhanced Tracking Script instead of the web container ID.
Fix: Verify that the Enhanced Tracking Script references your web container ID. The server container ID should only appear inside the server container configuration itself.

Tracking stops completely after implementation

Symptom: No data is sent to GA4 or ad platforms after adding the Enhanced Tracking Script.
Cause: The monthly request limit in the TAGGRS dashboard has been reached.
Fix: Check your request usage in the TAGGRS Dashboard.Upgrade your plan or adjust settings if the limit is consistently being hit. Once the request limit is reached, TAGGRS automatically pauses tracking until the next billing

Cloudflare 520 or similar errors

Symptom: The Enhanced Tracking Script loads inconsistently, tracking requests fail, or the browser shows Cloudflare errors such as 520.
Cause: The custom tracking domain is proxied through Cloudflare. For Enhanced Tracking Script custom domains, Cloudflare should not proxy the traffic. If the DNS record uses the orange cloud (“Proxied”), Cloudflare can interfere with the request flow.
Fix: In Cloudflare DNS settings, set every custom tracking domain used for TAGGRS to DNS-only. The cloud icon should be grey, not orange. Do this for all custom domains connected to the Enhanced Tracking Script or server-side tracking endpoint.

FAQ

How to identify which requests originate from the Enhanced Tracking Script?

You can identify requests generated by the TAGGRS script in your request graph in the analytics dashboard. Events originating from the script are labelled Enhanced, so you can see which portion of your tracked data comes from enhanced tracking.

Analytics dashboard that highlights the source of request count distribution over time: one of the item is 'Enhanced' and shows the uplift coming from the TAGGRS Enhanced Tracking Script V3.

How to measure the uplift generated by the Enhanced Tracking Script?

The uplift is visible in your Additional Data graph. This graph highlights the increase in tracked events, so it's easy to assess the impact of the Enhanced Tracking Script.

Useful resources

TABLE OF CONTENTS

Key features Prerequisites Configuration Troubleshooting FAQ Useful resources