container audit

GTM-P2BPCT

This container ships 94 hand-written scripts (51 KB of JavaScript) to every visitor — more than 98% of the 46,522 containers we have measured. That is an application's worth of code, delivered as tag configuration.

Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
559 published versions — each one live for every visitor the moment it was published.

Tags545

Custom scripts94

Third parties24

Delivered850 KB

Versions559

Where the data goes

Likely — the container names , a tagging-style host on its own domain. No page load of ours has confirmed it. 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 (4)

4 pieces 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

infoOne variable that a great deal depends on (165)

"village_name" is read by 165 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

infoLoads JavaScript from another host (49)

49 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 (3)

3 pieces 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 (2)

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_1492839_1145 private injects code from amplify.outbrain.com · runs page-level globals

__cvt_1492839_853 private injects code from connect.facebook.net · runs page-level globals

__cvt_K4VXG gallery injects code from sc-static.net, tr.snapchat.com · runs page-level globals

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.

thebicestercollection.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-P2BPCT`
Published version	`559` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-12 22:41:03 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-P2BPCT`
Body checksum	`c4cb9d974d605e319a6bbf62c2a69b7b60d9da4664a54d303e5800cda814f10f` 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-P2BPCT

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 »