Checks

Every check MeasureProof runs on a live site, and what each one detects. Each is a bounded external observation; the evidence behind a finding and the limits of what it can prove are in the Method.

This index lists the live check set. Linked checks have full evidence explainers; the rest are summarized here and bounded in the Method.

Inventory

• Tag and pixel inventory. Which tags and pixels loaded, the IDs they carry, and how each behaved: loaded, fired, or loaded but never seen firing on this visit.
• First-party and proxied endpoints. First-party GA4 /g/collect, reverse-proxied PostHog, and Adobe Edge Network CNAMEs that a host-only scanner would miss.

Duplicate and conflict

• Duplicate GA4 pageviews. The same GA4 measurement ID sending more than one page_view beacon on a single page load.
• Duplicate or conflicting ad pixels. Two or more distinct pixel IDs for the same ad platform (currently Meta and TikTok) firing on one load.

Hygiene

• Legacy Universal Analytics. A Universal Analytics snippet (analytics.js / ga.js) still loading, or a UA hit still being sent. Standard UA stopped processing data in July 2023.
• Retired Adobe DTM container. A retired Adobe DTM container filename (the satelliteLib- prefix) still loading. DTM was frozen read-only in 2020.
• Orphaned loader. A tracking loader fetched with no matching collection request observed, restricted to GA4 and Meta where the fire signal is definite.

Consent and privacy

• Tags firing before consent. A supported measurement request (GA4, Universal Analytics, Meta, or TikTok) sent before any interaction, on a load where a supported consent banner was confirmed visible and unanswered.
• Consent Mode evidence. The Consent Mode parameters on outgoing hits (for example gcs, gcd, dma), rendered as evidence. It records what is on the wire, not whether consent was valid.