container audit

GTM-PFFXDMKT

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

10 custom HTML tags carrying 5 KB of JavaScript. This runs on every page the container loads on.
Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.

Tags48

Custom scripts10

Third parties0

Delivered475 KB

Versions19

What we observed

A real browser loaded bose.de 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 tagging.bose.de — not Google

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 OneTrust answered its own API. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 1 fired afterwards. That is the outcome consent is meant to produce. Google recorded gcs=G100 (all denied).

Third parties contacted 25 hosts — players.brightcove.net, assets.bosecreative.com, static.cloudflareinsights.com, edqprofservus.blob.core.windows.net, cdn.cquotient.com, www.googletagmanager.com, magiclayer.bose.com, zn8hzinwseotwpdiy-bose.siteintercept.qualtrics.com, and 17 more

dataLayer events seen gtm.js, page_view, home, gtm.dom, gtm.load, sticky_popup-open-direct, view_item_list, gtm.scrollDepth, OneTrustLoaded, OptanonLoaded, OptanonReady, gtm.triggerGroup, +1 more

Where the data goes

Confirmed — a browser watched this site send measurement data to tagging.bose.de, not to Google. observed on bose.de 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 cookies directly (5)

5 pieces of custom code set cookies in code.

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

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 »

No third-party hosts were found in this container's tags.

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.

bose.de

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

Container	`GTM-PFFXDMKT`
Published version	`19` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 18:01:51 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-PFFXDMKT`
Body checksum	`694bf58fae7e7b8a4216f8081f29f4ffc45b2de6a832f2ca994d982f0f005fa1` 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-PFFXDMKT

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 »