container audit
GTM-NLHMBNFS
38 tags, 6 custom scripts, 5 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 6 custom HTML tags carrying 7 KB of JavaScript. This runs on every page the container loads on.
- 5 third-party hosts reachable from its tags.
Tags38
Custom scripts6
Third parties5
Delivered507 KB
Versions100
What we observed
A real browser loaded bestegg.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
googletagmanager.com — GoogleMeasurement sent to
google-analytics.com — GoogleConsent
OneTrust answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 2 fired afterwards. That is the outcome consent is meant to produce. 10 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — cdn-ilekheb.nitrocdn.com, challenges.cloudflare.com, cdn.cookielaw.org, edge.fullstory.com, cdn.optimizely.com, a10967270208.cdn.optimizely.com, static.addtoany.com, d2bnxibecyz4h5.cloudfront.net, and 17 more
dataLayer events seen
OneTrustLoaded, OptanonLoaded, gtm.js, gtm.dom, gtm.load, Loaded a Page, Segment Consent Preference Updated
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on bestegg.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 (1)
1 piece 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
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 »
fls.doubleclick.net ×4s.yimg.com ×2www.google-analytics.com ×2www.googleadservices.com ×2resources.digital-cloud-west.medallia.com ×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_K8GSG gallery 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-NLHMBNFS |
|---|---|
| Published version | 100 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:55:36 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-NLHMBNFS |
| Body checksum | 81426545af0f5ecbd55914bc16ec0e264be80f54911999f369d55ccfdaf3bd9dEvidence 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.
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 »