container audit

GTM-PW7G7R6

243 tags, 564 KB delivered to every visitor — more than 90% of the 46,522 containers we have measured. Size is a description here, not a fault.

17 custom HTML tags carrying 28 KB of JavaScript — more than 70% of the 46,522 containers we have measured. This runs on every page the container loads on.
10 third-party hosts reachable from its tags — more than 80% of the 46,522 containers we have measured.

Tags243

Custom scripts17

Third parties10

Delivered564 KB

Versions291

What we observed

A real browser loaded integrishealth.org 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 google-analytics.com — Google

Consent a consent banner was present and responded. 1 host appeared only after consent was granted.

Third parties contacted 13 hosts — integrisandme.com, static.legitscript.com, use.typekit.net, maps.googleapis.com, s7.addthis.com, www.googletagmanager.com, cdn-cookieyes.com, freshpaint-cdn.com, and 5 more

dataLayer events seen gtm.js, gtm.scrollDepth, gtm.dom, gtm.load, gtm.click

Where the data goes

Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on integrishealth.org 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 (15)

15 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

reviewUniversal Analytics tags still shipped (1)

1 Universal Analytics tag is still in the container.

WhyUniversal Analytics stopped processing data in July 2023. These tags still download and execute on every matching page, and send to an endpoint that discards them.

CheckNothing is being collected from these. Confirm the equivalent GA4 tag exists, then delete them.

Seenseen in 23.2% of 46,522 containers measured

infoOne variable that a great deal depends on (90)

"gtm.triggers" is read by 90 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

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 (1)

1 piece 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 »

integrisok.com ×33schema.org ×16prnewswire2-a.akamaihd.net ×4 arcadiatrails.com ×3 www.google-analytics.com ×2 www.integriscommunityhospital.com ×2 freshpaint-cdn.com ×1 lakeside-wh.com ×1 upload.wikimedia.org ×1 www.lakesidedoctors.com ×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_7303686_1317 private injects code from cdn-cookieyes.com

__cvt_7303686_1337 private injects code from perfalytics.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.

integrishealth.org

What this audit describes

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

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

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 »