container audit
GTM-TPFK4PCC
2 tags, no hand-written scripts, 1 third-party host — smaller than 90% of the 46,522 containers we have measured, and carrying none of the hand-written JavaScript most of them do.
- 1 third-party host reachable from its tags.
Tags2
Custom scripts0
Third parties1
Delivered342 KB
Versions2
What we observed
A real browser loaded percentagecalculator.net 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. no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision.
Third parties contacted
8 hosts — cdn.snigelweb.com, www.googletagmanager.com, securityannex.net, c.amazon-adsystem.com, securepubads.g.doubleclick.net, adengine.snigelweb.com, aax.amazon-adsystem.com, fundingchoicesmessages.google.com
dataLayer events seen
gtm.js, adconsentReady, gtm.dom, gtm.load
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on percentagecalculator.net 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.
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_261400198_7 private 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-TPFK4PCC |
|---|---|
| Published version | 2 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:12:00 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TPFK4PCC |
| Body checksum | c71b73e1d6d2c3f2fc36293e7ea71f7fe5606c933222a43b0b5799692053e601Evidence 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 »