container audit

GTM-PJ49M5Z

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

536 published versions — each one live for every visitor the moment it was published.

Tags178

Custom scripts76

Third parties23

Delivered695 KB

Versions536

What we observed

A real browser loaded dollarshaveclub.com 2 months 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 ss3.zone.us.dollarshaveclub.com — the site's own host, and googletagmanager.com

Measurement sent to ss3.zone.us.dollarshaveclub.com — 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 ×5, other — read from the measurement id, not the hostname

Consent a consent platform is present, but our browser could not complete the accept step — so the before-and-after comparison did not run here. 5 hosts appeared only after consent was granted. Google recorded gcs=G111 (all granted).

Third parties contacted 25 hosts — cdn.shopify.com, assets.visually.io, use.typekit.net, live.visually-io.com, shop.app, static.ordergroove.com, www.lightboxcdn.com, cdn-widgetsrepository.yotpo.com, and 17 more

dataLayer events seen gtm.dom, gtm.js, dl_user_data, rr_bot_validation, fprint, gtm.load, tie_user_attributes, gtm.click

Where the data goes

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

infoOne variable that a great deal depends on (62)

"ecommerce.currencyCode" is read by 62 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 (17)

17 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

infoConsent configuration detected (3)

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

infoUses browser storage (2)

2 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

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_126870000_3 private runs page-level globals

__cvt_126870000_276 private injects code from static.ads-twitter.com · runs page-level globals

__cvt_126870000_277 private injects code from static.ads-twitter.com · runs page-level globals

__cvt_126870000_279 private injects code from js.go2sdk.com

__cvt_PBGZL gallery injects code from www.redditstatic.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.

dollarshaveclub.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-PJ49M5Z`
Published version	`536` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-12 22:44:08 UTC (3 months ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-PJ49M5Z`
Body checksum	`91d64edce0f05b2cc5df6b29fdf68c7e905b1000da643cfc18e82df8530e963d` 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 3 months 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-PJ49M5Z

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 »