container audit
GTM-MZJZ59
This container can hand execution to 17 third parties — more than 96% of the 46,522 containers we have measured. Each serves code it controls, which can change at any time.
- 13 custom HTML tags carrying 9 KB of JavaScript. This runs on every page the container loads on.
- 860 published versions — each one live for every visitor the moment it was published.
Tags30
Custom scripts13
Third parties17
Delivered442 KB
Versions860
What we observed
A real browser loaded plannedparenthoodaction.org 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
ppfa.plannedparenthood.org — the site's own host, and googletagmanager.comMeasurement sent to
ppfa.plannedparenthood.org — 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 — read from the measurement id, not the hostname
Consent
no consent gate responded on this page, so there was nothing to hold measurement back (banners are often shown only to visitors in certain regions, and this was not a European visit). Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — secure.everyaction.com, connect.facebook.net, ppfa.plannedparenthood.org, www.googletagmanager.com, www.youtube.com, bat.bing.com, secure.quantserve.com, dx.mountain.com, and 17 more
dataLayer events seen
dataLayer_initialized, gtm.js, gtm.dom, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to ppfa.plannedparenthood.org, not to Google. observed on plannedparenthoodaction.org 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 (3)
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
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 »
qa-parallel-plannedparenthood.ppedit.org ×2qa-plannedparenthood.ppedit.org ×2qa-plannedparenthoodaction.ppedit.org ×2uat-parallel-plannedparenthood.ppedit.org ×2uat-parallel-plannedparenthoodaction.ppedit.org ×2d2hhc2rnb2eiis.cloudfront.net ×1docasap.com ×1qa-parallel-plannedparenthoodaction.ppedit.org ×1uat-plannedparenthood.ppedit.org ×1uat-plannedparenthoodaction.ppedit.org ×1www.docasap.com ×1www.google-analytics.com ×1www.plannedparenthood.org ×1www.plannedparenthoodaction.org ×1www.weareplannedparenthood.org ×1www.weareplannedparenthoodaction.org ×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_666187_2666 private injects code from ppfa.plannedparenthood.orgDetected 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-MZJZ59 |
|---|---|
| Published version | 860 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-13 11:44:10 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-MZJZ59 |
| Body checksum | ecaf45088a4fb81fe74f9a845c72025592657a6c81322ed0cf1879fe125893f8Evidence 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 »