container audit
GTM-WL43S67
73 tags, 19 custom scripts, 3 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 19 custom HTML tags carrying 3 KB of JavaScript — more than 80% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 3 third-party hosts 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.
Tags73
Custom scripts19
Third parties3
Delivered532 KB
Versions160
What we observed
A real browser loaded aplazame.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
webmetrics.aplazame.com — not GoogleMeasurement is first-party; the container still loads from Google. These are separate decisions, and this is the more common of the two.
Forwarded to
GA4 ×4 — read from the measurement id, not the hostname
Consent
a consent platform is present, but our browser could not complete the accept step — so the before-and-after comparison did not run here. 4 hosts appeared only after consent was granted. Google recorded
gcs=G100 (all denied).Third parties contacted
13 hosts — fonts.googleapis.com, www.datocms-assets.com, widget.trustpilot.com, www.googletagmanager.com, cdn.cookiehub.eu, cookiehub.net, pagead2.googlesyndication.com, googleads.g.doubleclick.net, and 5 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, cookiehub_ready, cookiehub_necessary, cookiehub_consent_update, cookiehub_dialog
Where the data goes
Confirmed — a browser watched this site send measurement data to webmetrics.aplazame.com, not to Google. observed on aplazame.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.
infoUses browser storage (3)
3 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
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
infoLoads JavaScript from another host (1)
1 piece 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
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_M6BJS gallery injects code from cdn.cookiehub.eu, dash.cookiehub.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-WL43S67 |
|---|---|
| Published version | 160 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:19:38 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-WL43S67 |
| Body checksum | 46f1c1d5c5a92e7d469600db81fa48f16aedc1428e89262d00e3a88366d1b29fEvidence 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 »