container audit

GTM-NBZ5JLL

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

5 third-party hosts reachable from its tags.
duplicate-ads-conversion is 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.

Tags16

Custom scripts0

Third parties5

Delivered475 KB

Versions19

What we observed

A real browser loaded reiss.com 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 — Google

Measurement sent to tags.reiss.com — not Google

Measurement is first-party; the container still loads from Google. These are separate decisions, and this is the more common of the two.

Forwarded to GA4 ×6 — 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. 1 host appeared only after consent was granted. Google recorded gcs=G100 (all denied).

Third parties contacted 25 hosts — cdn.cookielaw.org, static.queue-it.net, cms.platform.next, fonts.googleapis.com, assets.queue-it.net, www.googletagmanager.com, geolocation.onetrust.com, www.next.co.uk, and 17 more

dataLayer events seen siteDetails, gtm.js, gtm.dom, bloomreach, OneTrustLoaded, OptanonLoaded, UserConsentChangeNotification.FunctionalEnabled, banner_impression, gtm.elementVisibility, gtm.load, NotifyGoogleAnalytics.BannerShown, UserConsentChangeNotification.PerformanceEnabled, +3 more

Where the data goes

Confirmed — a browser watched this site send measurement data to tags.reiss.com, not to Google. observed on reiss.com 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

infoUses browser storage (1)

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

ad.doubleclick.net ×4 fls.doubleclick.net ×4 www.googleadservices.com ×4 googleads.g.doubleclick.net ×3 www.google-analytics.com ×1

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.

reiss.com

What this audit describes

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

Container	`GTM-NBZ5JLL`
Published version	`19` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-22 10:27:03 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-NBZ5JLL`
Body checksum	`31b489c805fe441a5a1195c22b1fa566bf11a0f3b1d1299bd53f54da58050440` 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-NBZ5JLL

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 »