tagora
container audit

GTM-T6ZTNGH

This container can hand execution to 13 third parties — more than 90% of the 46,522 containers we have measured. Each serves code it controls, which can change at any time.

Tags78
Custom scripts33
Third parties13
Delivered614 KB
Versions481

What we observed

A real browser loaded charlottetilbury.com a month 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 analytics.charlottetilbury.com — the site's own host, and googletagmanager.com
Measurement sent to analytics.charlottetilbury.com — not Google

Measurement runs through the site's own infrastructure. Part of the tag library still comes from Google, which is normal — the two are loaded separately.

Forwarded to GA4 ×3 — read from the measurement id, not the hostname
Consent OneTrust answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 0 fired afterwards. That is the outcome consent is meant to produce. 1 host appeared only after consent was granted. Google recorded gcs=G111 (all granted).
Third parties contacted 25 hosts — cdn.cookielaw.org, images.ctfassets.net, videos.ctfassets.net, amazon-cognito-assets.eu-west-1.amazoncognito.com, 64d379437159.edge.captcha-sdk.awswaf.com, geolocation.onetrust.com, 64d379437159.edge.sdk.awswaf.com, privacyportal-eu.onetrust.com, and 17 more
dataLayer events seen oneTrustPreferences, fireRemarketingTag, customerLogin, promoViewNonInteractive, OneTrustLoaded, OptanonLoaded, gtm.js, componentImpression, gtm.dom, gtm.load, gtm.scrollDepth

Where the data goes

Confirmed — a browser watched this site send measurement data to analytics.charlottetilbury.com, not to Google. observed on charlottetilbury.com 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.

reviewdocument.write (3)
3 pieces of custom code call document.write.

Whydocument.write blocks the HTML parser while it runs, and browsers ignore it entirely once the page has finished parsing — so an async-loaded tag using it can silently do nothing.

CheckIf these tags fire on page load they are costing render time; if they fire later they may not be working at all. Worth confirming the tag still does what it was added to do.

Seenseen in 18.4% of 46,522 containers measured

reviewSame GA4 property configured more than once (1)
G-WLG9DH8N53 is configured by 2 separate tags.

WhyEach config tag initialises the property independently, so a single page view can be counted once per tag. Sessions, users and conversion rates all inherit the error.

CheckIf more than one of these fires on the same page you are double-counting. Compare against a known-good day, or check for a step change in traffic when the second tag was added.

Seenseen in 4.8% of 46,522 containers measured

infoUses browser storage (8)
8 pieces of custom code read or write localStorage or sessionStorage.

WhyBrowser storage persists across visits and is not covered by cookie consent tooling, so it is easy to overlook when auditing what you keep on a visitor's device.

CheckConfirm nothing personal is being kept there, and that it is covered by your privacy notice.

Seenseen in 23.3% of 46,522 containers measured

infoLoads JavaScript from another host (5)
5 pieces of custom code fetch and run JavaScript from another host.

WhyWhatever that host serves executes with full access to the page — it can read the DOM, cookies and form fields. The code is not in this container, so it can change at any time without any change here.

CheckConfirm you recognise every host below and that someone owns the relationship. A host you cannot name is the one to chase.

Seenseen in 54.4% of 46,522 containers measured

infoConsent configuration detected (3)
The container declares one or more consent signals.

WhyConsent handling is present in the container. This describes what the artifact declares; what actually happened on the page is measured separately, above.

CheckConfirm these settings match the consent policy you intend to enforce, and compare them with the before-and-after observation.

Seenseen in 44.6% 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 »

bs.serving-sys.com ×2c.hrzn-nxt.com ×2c212.net ×2analytics.charlottetilbury.com ×1analytics.dev.tilburytech.net ×1analytics.qa.tilburytech.net ×1assets.sitescdn.net ×1cdn.pdst.fm ×1cdn.tkrconnector.com ×1connect.facebook.net ×1dynamic.criteo.com ×1s.yimg.com ×1td.oo34.net ×1

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_9858341_1765 private injects code from sc-static.net, tr.snapchat.com · runs page-level globals
__cvt_9858341_1872 private injects code from js.appboycdn.com · runs page-level globals
__cvt_9858341_1873 private runs page-level globals
__cvt_KT4F4 gallery injects code from c.amazon-adsystem.com · runs page-level globals
__cvt_PBGZL gallery injects code from www.redditstatic.com · runs page-level globals

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

charlottetilbury.com

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

ContainerGTM-T6ZTNGH
Published version481 — the identity of this configuration. It changes only when someone publishes.
Read at2026-08-22 13:32:57 UTC (a month ago)
Sourcehttps://www.googletagmanager.com/gtm.js?id=GTM-T6ZTNGH
Body checksum4653d8045ad25c39b164aff39f35a7863c29534fe7ced3e0a4420227dfc8c135
Evidence 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 a month 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.

Re-audit GTM-T6ZTNGH

Check another container

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 »