GTM-M2R7M87
This container is published but empty — no tags, so nothing fires.
What we observed
A real browser loaded ips.pt 2 months 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.
googletagmanager.com — Googlegoogle-analytics.com — Googleanalytics_storage was denied, which is Consent Mode working as designed rather than a gap. no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. Google recorded gcs=G100 (all denied).Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on ips.pt 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.
No findings were raised for this container.
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 »
No third-party hosts were found in this container's tags.
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-M2R7M87 |
|---|---|
| Published version | 1 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:42:30 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-M2R7M87 |
| Body checksum | 14058b2bd13657619333b5dec131f277c4e791d856ac26f4b5a13ca712c97dabEvidence 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 »