Infrastructure observation
Interactive Measurement Demo
See what your browser-side tracking reveals
Run a public visibility check to see which marketing and consent signals can be observed — and which critical areas require deeper validation.
01
Browser-visible signals
02
Consent observations
03
Validation boundaries
Preparing sample report
Building a visibility snapshot
- 1 Opening browser session
- 2 Observing tag and container activity
- 3 Inspecting marketing network requests
- 4 Checking consent behavior
- 5 Building visibility report
Demo simulation only — no request is being sent to the submitted website.
Sample visibility report
Interactive demo using representative findings
Visibility snapshot
Sample data, not a live scan
Observed
Observed during this scan
Google Tag Manager container loaded + A GTM container request is included in this representative browser session.
Why this matters: A loaded container can deliver tags, but loading alone does not verify tag configuration or data quality.
GA4 page_view request observed + A browser request resembling a GA4 page view is present in the sample.
Why this matters: This confirms visible request activity only; it cannot confirm processing or reporting inside GA4.
Meta browser request observed + A representative browser-side request to Meta is visible.
Why this matters: Browser activity can be observed publicly, while delivery, matching, and attribution require platform access.
Partial signal
Detected but not fully verified
-
dataLayer activity detected
Activity is represented in the sample, but event completeness and field accuracy are not verified.
-
Shopify Web Pixels infrastructure detected
Infrastructure may be present; its configuration and destination behavior require deeper access.
-
Google Consent Mode signals detected
Consent parameters are visible, but correct defaults and timing cannot be fully verified here.
Consent visibility
Consent behavior observed
Consent banner detected
Observed during this sample
CMP detected
Detected but not fully verified
Consent Mode signals observed
Visible in representative requests
Consent state update observed
After sample interaction
Detailed consent validation available in a full audit
A deeper audit checks configuration, timing, and tag behavior—not just visible signals.
- • Default consent state
- • Consent update timing
- • analytics_storage
- • ad_storage
- • ad_user_data
- • ad_personalization
- • Tag behavior before and after consent
Cannot be verified from a public browser scan
Requires deeper access
Server-side event delivery
Requires server or platform evidence.
Browser/server event parity
Requires both delivery paths.
Event ID consistency
Requires paired event inspection.
Deduplication behavior
Requires platform-side validation.
Event Match Quality
Requires Meta account access.
Identity signal quality
Requires payload-level evidence.
Purchase attribution reliability
Requires platform, analytics, and source-of-truth comparison.
Go beyond visible signals
A public browser scan can reveal visible behavior, but it cannot confirm what happens inside Meta, Google Ads, GA4, GTM, or your server-side pipeline.
A full audit connects browser-side evidence with platform and implementation access to identify what actually needs attention.