container audit
GTM-MXG38X86
20 tags, 1 custom scripts, 4 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 1 custom HTML tag carrying 1 KB of JavaScript. This runs on every page the container loads on.
- 4 third-party hosts reachable from its tags.
duplicate-ads-conversionis uncommon — under 4% of the containers we have measured have it. That is context rather than a verdict: a server container is rarer still and is a sign of a mature setup. What it means is in the finding itself.
Tags20
Custom scripts1
Third parties4
Delivered471 KB
Versions14
What we observed
A real browser loaded isp-netzplan.de 2 months ago and recorded every request it made. This is what happened, as distinct from what the container is configured to do. It is one page load — anything that fires only deeper in the site did not fire here.
Container loaded from
googletagmanager.com — GoogleMeasurement sent to
google-analytics.com — GoogleConsent
a consent platform is present, but our browser could not complete the accept step — so the before-and-after comparison did not run here. Google recorded
gcs=G111 (all granted).Third parties contacted
23 hosts — www.netzplan.de, www.teccle-group.de, www.googletagmanager.com, www.clarity.ms, snap.licdn.com, www.google.com, px.ads.linkedin.com, scripts.clarity.ms, and 15 more
dataLayer events seen
borlabs-cookie-opt-in-google-analytics, borlabs-cookie-opt-in-google-tag-manager, borlabs-cookie-opt-in-microsoft-clarity, borlabs-cookie-opt-in-facebook, borlabs-cookie-opt-in-maps, borlabs-cookie-opt-in-instagram, borlabs-cookie-opt-in-open-street-map, borlabs-cookie-opt-in-x-alias-twitter, borlabs-cookie-opt-in-vimeo, borlabs-cookie-opt-in-youtube, borlabs-cookie-opt-in-videoask, borlabs-cookie-opt-in-linkedin, +6 more
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on isp-netzplan.de More info »
Findings
Ordered by consequence. review has a concrete cost when it bites; info is real but depends on your setup. Seen is how common it is across the containers we have measured — reported separately on purpose, because common and harmless are different claims.
reviewSame Google Ads conversion defined more than once (1)
1 conversion action is defined by more than one tag.
WhyA conversion ID plus label identifies one action. Two tags carrying the same pair can report the same conversion twice, inflating conversion counts and the ROAS that bidding runs on.
CheckCheck whether both tags can fire on the same page. If they can, your Ads reporting is overstating this action and automated bidding is optimising against it.
Seenseen in 3.8% of 46,522 containers measured
reviewNo consent signal in the container (1)
Nothing in this container sets, reads, or gates on a consent state.
WhyThe container itself neither sets a Consent Mode default, holds any tag back for consent, nor references a known consent platform. Either enforcement lives entirely outside GTM — where it cannot be audited from here — or tags fire regardless of what a visitor chose.
CheckIf a consent platform blocks scripts before GTM loads, this is fine — confirm that is actually the case. If not, tags are firing on a choice nobody recorded.
Seenseen in 52.1% of 46,522 containers measured
infoVendor IDs written into custom code (1)
1 vendor ID is pasted directly into custom HTML rather than held in a variable or template.
WhyChanging a property, pixel or account then means editing every tag that mentions it, and any one that gets missed keeps sending to the old destination indefinitely.
CheckFine if the ID never changes. If you have ever migrated a property, check that none of these still point at the old one.
Seenseen in 31.4% of 46,522 containers measured
Third parties it can reach
Each host is a party that can execute code or receive data in a visitor's browser. Follow one to see who else loads it. More info »
What the custom templates can do
Custom templates are third-party code shipped inside the container. Injecting scripts and running page globals is ordinary for them — most tag templates need it to work — so this is an inventory, not a warning. It lists the capability each template declares so you can match it against templates you meant to install.
__cvt_168078565_7 private injects code from cdn.mxpnl.com · runs page-level globals__cvt_5RM3Q gallery injects code from connect.facebook.net · runs page-level globalsDetected on
Sites observed loading this container. A container used across many hosts is a shared template; one on a single host is a bespoke build. Follow a site to see every container it loads.
What this audit describes
Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.
| Container | GTM-MXG38X86 |
|---|---|
| Published version | 14 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:50:15 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-MXG38X86 |
| Body checksum | 95892f8c14c1dadbecec285dab14a6f186f6dda41cacf67291ab919b67c5f839Evidence of the exact bytes we read, not an identity: Google varies the response per request, so re-fetching an unchanged container yields a different checksum. Compare the published version instead. |
Re-audit
This reading is from 2 months ago. A container can be republished at any time, and nothing here updates on its own — a fresh read is the only way to know whether it still says this. Running it again replaces this page in place, so the link keeps working.
Put this container under version control. Tagora exports it to a repository you own, so every change arrives as a pull request. How it works »