container audit
GTM-KD3FNFD
21 tags, 3 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 3 custom HTML tags carrying 4 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.
inner-htmlis uncommon — under 6% of the containers we have measured have it. That is context rather than a verdict: a server container is rarer still and is a sign of a mature setup. What it means is in the finding itself.
Tags21
Custom scripts3
Third parties1
Delivered503 KB
Versions99
What we observed
A real browser loaded fredonia.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
sst.fredonia.edu — the site's own host, and googletagmanager.comMeasurement sent to
sst.fredonia.edu — 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 ×7 — read from the measurement id, not the hostname
Consent
a consent banner was present and we accepted it. 6 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). no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. 4 advertising hosts were contacted before anything was granted.
Third parties contacted
19 hosts — cdn.jsdelivr.net, use.typekit.net, www.googletagmanager.com, cse.google.com, www.google.com, analytics.google.com, stats.g.doubleclick.net, www.google.co.il, and 11 more
dataLayer events seen
gtm.js, gtm.dom, udm_id, gtm.load, gtm.scrollDepth
Where the data goes
Confirmed — a browser watched this site send measurement data to sst.fredonia.edu, not to Google. observed on fredonia.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.
reviewWrites innerHTML (1)
1 piece of custom code assign to innerHTML.
WhyAssigning innerHTML parses the string as HTML. If any of it comes from the URL, the page or a cookie, that is a script-injection route into your own site.
CheckCheck whether the assigned value is a fixed template or built from something a visitor can influence.
Seenseen in 5.7% of 46,522 containers measured
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
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_11382980_274 private injects code from connect.facebook.net · runs page-level globals__cvt_11382980_328 private injects code from opencdn.fpjs.sh · 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-KD3FNFD |
|---|---|
| Published version | 99 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-13 09:21:02 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-KD3FNFD |
| Body checksum | 3e7157bcd1a00b64b82d7c40133a75350b36e74a3320549d816fc230190cc223Evidence 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 2 months 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 »