container audit
GTM-NZF62RP
68 tags, 1 custom scripts, 1 third-party host — 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.
- 1 third-party host reachable from its tags.
- Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
- 415 published versions — each one live for every visitor the moment it was published.
Tags68
Custom scripts1
Third parties1
Delivered485 KB
Versions415
What we observed
A real browser loaded bikbok.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
metrics-v2.bikbok.com — the site's own host, and googletagmanager.comMeasurement sent to
metrics-v2.bikbok.com — not GoogleMeasurement 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 ×8 — read from the measurement id, not the hostname
Consent
Cookiebot answered its own API. Measurement fired beforehand but carried no identifier —
analytics_storage was denied, which is Consent Mode working as designed rather than a gap. 2 hosts appeared only after consent was granted. Google recorded gcs=G100 (all denied).Third parties contacted
10 hosts — consent.cookiebot.com, static.cloudflareinsights.com, bikbok.imgix.net, cdn.jwplayer.com, www.googletagmanager.com, consentcdn.cookiebot.com, js-agent.newrelic.com, bam.eu01.nr-data.net, and 2 more
dataLayer events seen
customerInfoLoaded, gtm.js, gtm.dom, view_promotion, gtm.load, cookie_consent_preferences, cookie_consent_statistics, cookie_consent_marketing
Where the data goes
Confirmed — a browser watched this site send measurement data to metrics-v2.bikbok.com, not to Google. observed on bikbok.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 (2)
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 »
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_8344953_587 private injects code from script.tapfiliate.com · runs page-level globals__cvt_8344953_612 private injects code from www.clarity.ms · 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-NZF62RP |
|---|---|
| Published version | 415 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:58:30 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-NZF62RP |
| Body checksum | 145c79ef1c7b20bcc451f478b752863db4eb31f495e3575464939706cab96fb7Evidence 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 »