container audit
GTM-NHRHKC3
4 tags, no hand-written scripts, 1 third-party host — smaller than 85% 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.
duplicate-ads-conversionis uncommon — under 4% 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.
Tags4
Custom scripts0
Third parties1
Delivered395 KB
Versions4
What we observed
A real browser loaded unicentro.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. Google recorded
gcs=G1 (no consent signal). 2 advertising hosts were contacted before anything was granted.Third parties contacted
12 hosts — www.googletagmanager.com, fonts.googleapis.com, vlibras.gov.br, www.google-analytics.com, www.clarity.ms, scripts.clarity.ms, googleads.g.doubleclick.net, www.google.com, and 4 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, gtm.linkClick
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on unicentro.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.
reviewSame Google Ads conversion defined more than once (1)
1 conversion action is defined by more than one tag.
WhyA conversion ID plus label identifies one action. Two tags carrying the same pair can report the same conversion twice, inflating conversion counts and the ROAS that bidding runs on.
CheckCheck whether both tags can fire on the same page. If they can, your Ads reporting is overstating this action and automated bidding is optimising against it.
Seenseen in 3.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
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 »
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-NHRHKC3 |
|---|---|
| Published version | 4 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:54:45 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-NHRHKC3 |
| Body checksum | 94a11c775585a4d4cac601ab20f734ed34d50a08f007143f506de755fde4155fEvidence 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 »