container audit

GTM-WS6DT9

This container can hand execution to 25 third parties — more than 99% of the 46,522 containers we have measured. Each serves code it controls, which can change at any time.

17 custom HTML tags carrying 81 KB of JavaScript — more than 70% of the 46,522 containers we have measured. This runs on every page the container loads on.
588 published versions — each one live for every visitor the moment it was published.
eval is uncommon — under 1% 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.

Tags30

Custom scripts17

Third parties25

Delivered564 KB

Versions588

What we observed

A real browser loaded radiotimes.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 www.radiotimes.com — not Google, at /api/gtm/g/collect

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

Consent Quantcast 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 13 hosts — use.typekit.net, images.immediate.co.uk, cdn.speedcurve.com, www.googletagmanager.com, www.datadoghq-browser-agent.com, cdn.greenvideo.io, embeds.greenvideo.io, media-api-prod.greenvideo.io, and 5 more

dataLayer events seen Site Data, Page Data, gtm.js, gtm.dom, gtm.load

Where the data goes

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

reviewWrites innerHTML (4)

4 pieces of custom code assign to innerHTML.

WhyAssigning innerHTML parses the string as HTML. If any of it comes from the URL, the page or a cookie, that is a script-injection route into your own site.

CheckCheck whether the assigned value is a fixed template or built from something a visitor can influence.

Seenseen in 5.7% of 46,522 containers measured

revieweval() (1)

1 piece of custom code call eval().

Whyeval turns a string into executing code. If any part of that string comes from the page, the URL or a cookie, whoever controls that input controls the code.

CheckTrace where the evaluated string comes from. A fixed literal is harmless; anything derived from user-controllable input is not.

Seenseen in 0.5% of 46,522 containers measured

infoLoads JavaScript from another host (9)

9 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 »

What the custom templates can do

Custom templates are third-party code shipped inside the container. Injecting scripts and running page globals is ordinary for them — most tag templates need it to work — so this is an inventory, not a warning. It lists the capability each template declares so you can match it against templates you meant to install.

__cvt_WP5K6 gallery injects code from static.anonymised.io

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.

radiotimes.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-WS6DT9`
Published version	`588` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-22 10:52:34 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-WS6DT9`
Body checksum	`7da5b0380720c510a134dd1b5c07f78ec853dd48f31ee08c6f75907334961aa4` 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-WS6DT9

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 »