container audit
GTM-MH9L43J
22 tags, 5 custom scripts, 7 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 5 custom HTML tags carrying 3 KB of JavaScript. This runs on every page the container loads on.
- 7 third-party hosts reachable from its tags — more than 70% of the 46,522 containers we have measured.
- 378 published versions — each one live for every visitor the moment it was published.
Tags22
Custom scripts5
Third parties7
Delivered466 KB
Versions378
What we observed
A real browser loaded penso.com.br 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
a consent banner was present and we accepted it. 2 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. 5 advertising hosts were contacted before anything was granted.
Third parties contacted
18 hosts — www.googletagmanager.com, www.google.com, ad.doubleclick.net, connect.facebook.net, snap.licdn.com, www.clarity.ms, koi-3s3a416jys.marketingautomation.services, widget.manychat.com, and 10 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, ui_click, form_submit_attempt
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on penso.com.br 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.
reviewHardcoded http:// URL (2)
2 pieces of custom code reference a plain http:// address.
WhyOn an https:// page the browser blocks or upgrades these. Blocked means the tag quietly stops working; upgraded only works if that host also serves https.
CheckCheck whether the hosts below still respond over https, and update the URLs.
Seenseen in 12.8% 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
infoLoads JavaScript from another host (3)
3 pieces 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
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 »
koi-3s3a416jys.marketingautomation.services ×3www.google-analytics.com ×2app-3s3a416jys.marketingautomation.services ×1googleads.g.doubleclick.net ×1mccdn.me ×1www.clarity.ms ×1www.googleadservices.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_6132011_332 private injects code from connect.facebook.net · runs page-level globals__cvt_6132011_335 private injects code from snap.licdn.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-MH9L43J |
|---|---|
| Published version | 378 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-11 20:56:44 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-MH9L43J |
| Body checksum | c2502f2f59cea13c5eb293461545c612bcdcbeb9b2174d769e94fed7f45fef53Evidence 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 »