container audit

GTM-WXCVD5

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

7 custom HTML tags carrying 8 KB of JavaScript. This runs on every page the container loads on.
8 third-party hosts reachable from its tags — more than 70% of the 46,522 containers we have measured.
Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.

Tags18

Custom scripts7

Third parties8

Delivered463 KB

Versions70

What we observed

A real browser loaded trade-ideas.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 sg.trade-ideas.com — the site's own host

Measurement sent to sg.trade-ideas.com — not Google

Both wires run through infrastructure the site controls.

Forwarded to GA4 ×2 — read from the measurement id, not the hostname

Consent no consent gate responded on this page, so there was nothing to hold measurement back (banners are often shown only to visitors in certain regions, and this was not a European visit). Google recorded gcs=G1 (no consent signal).

Third parties contacted 25 hosts — cdn.userway.org, cdnjs.cloudflare.com, fonts.googleapis.com, cdn.jsdelivr.net, code.jquery.com, raw.githubusercontent.com, bat.bing.com, snap.licdn.com, and 17 more

dataLayer events seen gtm.js, gtm.dom, gtm.load

Where the data goes

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

infoLoads JavaScript from another host (4)

4 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

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

infoConsent configuration detected (1)

The container declares one or more consent signals.

WhyConsent handling is present in the container. This describes what the artifact declares; what actually happened on the page is measured separately, above.

CheckConfirm these settings match the consent policy you intend to enforce, and compare them with the before-and-after observation.

Seenseen in 44.6% 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 »

a.ads.rmbl.ws ×1 analytics.tiktok.com ×1 code.evidence.io ×1 dc.ads.linkedin.com ×1 diffuser-cdn.app-us1.com ×1 securepubads.g.doubleclick.net ×1 snap.licdn.com ×1 static.ads-twitter.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.

trade-ideas.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-WXCVD5`
Published version	`70` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 18:22:45 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-WXCVD5`
Body checksum	`1f26c284e0b07f8e79d156e3044ac8bf641ada5be9b40a337a9555488b679b44` 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-WXCVD5

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 »