container audit

GTM-57F7STTF

97 tags, 0 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).

1 third-party host reachable from its tags.

Tags97

Custom scripts0

Third parties1

Delivered493 KB

Versions36

What we observed

A real browser loaded receitasnestle.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 www.receitasnestle.com.br — the site's own host, at /modules/contrib/google_tag/js/gtm.js rather than the default path, and googletagmanager.com

Measurement sent to data-sa.receitasnestle.com.br — not Google

Measurement 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 ×12 — read from the measurement id, not the hostname

Consent OneTrust answered its own API. Measurement fired beforehand but carried no identifier — analytics_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).

Third parties contacted 25 hosts — pagead2.googlesyndication.com, forms-blip-receitas.cs.blip.ai, www.google-analytics.com, use.typekit.net, googleads.g.doubleclick.net, cdn.cookielaw.org, www.googletagmanager.com, 534001252.collect.igodigital.com, and 17 more

dataLayer events seen fireTags, gtm.js, lce_banner_view, gtm.dom, local_gtm_settings, global_zone_pageview, globalGTMReady, OneTrustLoaded, OptanonLoaded, lce_section_view, oneTrustReady, gtm.load, +1 more

Where the data goes

Confirmed — a browser watched this site send measurement data to data-sa.receitasnestle.com.br, not to Google. observed on receitasnestle.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 (1)

1 piece 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

infoOne variable that a great deal depends on (96)

"event_name" is read by 96 tags and triggers — more than anything else in this container.

WhyGTM shows you where a variable is defined, never how much depends on it. Editing this one touches a large share of the container at once, and whatever breaks will surface somewhere that looks unrelated to the change.

CheckBefore changing it, check what reads it. If it feeds both measurement and consent or routing logic, split those uses apart first.

Seenseen in 10.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 »

www.google-analytics.com ×96

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.

winiary.pl purina.co.uk receitasnestle.com.br

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

Container	`GTM-57F7STTF`
Published version	`36` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-22 09:47:47 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-57F7STTF`
Body checksum	`588e56120a0ad81696a1ef6132c8a2dd69d42cc56d4fa38e99f62c41e8c42da9` Evidence 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.

Re-audit GTM-57F7STTF

Check another container

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 »