container audit

GTM-KJQ752R

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

35 custom HTML tags carrying 14 KB of JavaScript — more than 80% of the 46,522 containers we have measured. This runs on every page the container loads on.
432 published versions — each one live for every visitor the moment it was published.
duplicate-ads-conversion is 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.

Tags414

Custom scripts35

Third parties14

Delivered890 KB

Versions432

What we observed

A real browser loaded hp.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 udl.hp.com — 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 ×3 — 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 3 fired afterwards. That is the outcome consent is meant to produce. 10 hosts appeared only after consent was granted. Google recorded gcs=G111 (all granted).

Third parties contacted 25 hosts — rum.hlx.page, www.googletagmanager.com, cdn.cookielaw.org, geolocation.onetrust.com, privacyportal.onetrust.com, www.youtube.com, cdn1.adoberesources.net, znaid9q7g0kclquju-hpexperience.siteintercept.qualtrics.com, and 17 more

dataLayer events seen gtm.js, standards.pageReady, pb.onOptInGroups, e_pageView, gtm.dom, gtm.load, mu.ready, OneTrustLoaded, OptanonLoaded, gtm.click, gtm.triggerGroup, mkt.PageView

Where the data goes

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

reviewSame Google Ads conversion defined more than once (9)

5 conversion actions are defined by more than one tag.

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

infoOne variable that a great deal depends on (41)

"linkID" is read by 41 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 (13)

13 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 (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 »

fls.doubleclick.net ×143www.googleadservices.com ×119www.google-analytics.com ×8 analytics.tiktok.com ×5 c.amazon-adsystem.com ×5 googleads.g.doubleclick.net ×3 insight.adsrvr.org ×2 services.xg4ken.com ×2 www.redditstatic.com ×2 resources.xg4ken.com ×1 static.xingcdn.com ×1 utt.impactcdn.com ×1 www.hp.com&ex-hargs=v%3d1.0%3bc%3d3386715520702%3bp%3d53277798-fba1-4186-1147-a027894c1e24 ×1 www.hp.com&ex-hargs=v%3d1.0%3bc%3d5341515560702%3bp%3dbcbfb0f8-0c69-1617-5f29-3745e9557669 ×1

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_96161394_116 private injects code from connect.facebook.net · runs page-level globals

__cvt_96161394_118 private injects code from snap.licdn.com

__cvt_96161394_1397 private injects code from www.redditstatic.com · runs page-level globals

__cvt_96161394_1413 private injects code from c.amazon-adsystem.com · runs page-level globals

__cvt_96161394_1448 private injects code from analytics.tiktok.com

__cvt_96161394_7 private injects code from static.ads-twitter.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.

hp.net hp.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-KJQ752R`
Published version	`432` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-22 10:21:23 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-KJQ752R`
Body checksum	`2e83ab03825d4427698b768d9488981d6059471030b3aa013ea23d5464894834` 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-KJQ752R

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 »