container audit
GTM-W62WMQJX
94 tags, 4 custom scripts, 2 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 4 custom HTML tags carrying 2 KB of JavaScript. This runs on every page the container loads on.
- 2 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.
Tags94
Custom scripts4
Third parties2
Delivered452 KB
Versions28
What we observed
A real browser loaded berea.edu 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
server-side-tagging-livx3p2vba-uc.a.run.app — 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 ×8 — 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. Google recorded
gcs=G111 (all granted).Third parties contacted
14 hosts — p.typekit.net, bereafaust.wpengine.com, fonts.gstatic.com, www.googletagmanager.com, connect.facebook.net, smart-pixl.com, 42pgxxd20k-dsn.algolia.net, analytics.google.com, and 6 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, gtm.timer
Where the data goes
Confirmed — a browser watched this site send measurement data to server-side-tagging-livx3p2vba-uc.a.run.app, not to Google. observed on berea.edu 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
infoOne variable that a great deal depends on (50)
"gtm.elementUrl" is read by 50 tags and triggers — more than anything else in this container.
WhyGTM shows you where a variable is defined, never how much depends on it. Editing this one touches a large share of the container at once, and whatever breaks will surface somewhere that looks unrelated to the change.
CheckBefore changing it, check what reads it. If it feeds both measurement and consent or routing logic, split those uses apart first.
Seenseen in 10.1% 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 »
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.
What this audit describes
Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.
| Container | GTM-W62WMQJX |
|---|---|
| Published version | 28 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:16:09 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-W62WMQJX |
| Body checksum | 7996bf42af5b712f918a1c3cdcf5c1c3c44663b9c7ed1c5541f92b1085c1764cEvidence 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 »