GTM-MRJVDLW7
This container ships 106 hand-written scripts (37 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.
duplicate-ads-conversionis 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.
What we observed
A real browser loaded softbank.jp 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.
googletagmanager.com — Googlegoogle-analytics.com — GoogleWhere the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on softbank.jp 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.
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
WhyCookies set this way bypass GTM's consent settings, because the consent checks live in the tag templates rather than in raw JavaScript.
CheckIf any of these cookies are used for analytics or advertising, confirm they are still gated on a consent decision.
Seenseen in 21.2% of 46,522 containers measured
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
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
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
WhyChanging a property, pixel or account then means editing every tag that mentions it, and any one that gets missed keeps sending to the old destination indefinitely.
CheckFine if the ID never changes. If you have ever migrated a property, check that none of these still point at the old one.
Seenseen in 31.4% 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_182950856_3 private injects code from s.yimg.jp · runs page-level globals__cvt_182950856_4 private injects code from s.yimg.jp · runs page-level globals__cvt_182950856_5 private injects code from s.yimg.jp · runs page-level globals__cvt_182950856_6 private injects code from s.yimg.jp · runs page-level globals__cvt_182950856_7 private injects code from s.yimg.jp · runs page-level globals__cvt_182950856_979 private injects code from static.ads-twitter.com · runs page-level globals__cvt_182950856_980 private injects code from static.ads-twitter.com · runs page-level globals__cvt_5R7R4 gallery injects code from tag.flvcdn.net · runs page-level globals__cvt_KT4F4 gallery injects code from c.amazon-adsystem.com · runs page-level globals__cvt_PLV57 gallery injects code from tag.flvcdn.net · runs page-level globalsDetected 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.
What this audit describes
Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.
| Container | GTM-MRJVDLW7 |
|---|---|
| Published version | 229 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-20 22:19:33 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-MRJVDLW7 |
| Body checksum | 1663f3824f7114127c7edb58e1ea0340865198d3f16c7b52685459e28f8d15adEvidence 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.
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 »