container audit
GTM-N58WWMC
24 tags, 4 custom scripts, 5 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 4 custom HTML tags carrying 3 KB of JavaScript. This runs on every page the container loads on.
- 5 third-party hosts reachable from its tags.
Tags24
Custom scripts4
Third parties5
Delivered500 KB
Versions63
What we observed
A real browser loaded hardwarezone.com.sg 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
Quantcast answered its own API. 2 measurement hits left the page before it was granted, carrying a client id (whether that is permitted depends on jurisdiction, and this was not a European visit). 10 hosts appeared only after consent was granted. Google recorded
gcs=G1 (no consent signal). 10 advertising hosts were contacted before anything was granted.Third parties contacted
25 hosts — dev.visualwebsiteoptimizer.com, adtag.sphdigital.com, js-agent.newrelic.com, securepubads.g.doubleclick.net, tags.crwdcntrl.net, cdn.sphlabs.com, geniuslinkcdn.com, bam.nr-data.net, and 17 more
dataLayer events seen
pageview, gtm.js, gtm.dom, gtm.load
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on hardwarezone.com.sg 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.
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
infoUses browser storage (2)
2 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
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 »
www.google-analytics.com ×9sph465.outgrow.us ×1www.googleadservices.com ×1www.hardwarezone.com.sg ×1www.youtube.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_11428705_109 private injects code from analytics.tiktok.com__cvt_11428705_200 private runs page-level globals__cvt_11428705_201 private injects code from cdn.moengage.com · runs page-level globals__cvt_5RM3Q gallery injects code from connect.facebook.net, capi-automation.s3.us-east-2.amazonaws.com · runs page-level globals__cvt_NNQ8S gallery injects code from amplify.outbrain.com · runs page-level globals__cvt_PLW64 gallery injects code from cdn.taboola.comDetected 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-N58WWMC |
|---|---|
| Published version | 63 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 10:09:41 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-N58WWMC |
| Body checksum | ff0ba6018b394b9c7f600c540823bef1616bc9c4fdaf75b021df45a71e46638aEvidence 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 »