PRIVATE · INITIAL-PAGE EVIDENCE
Conversion Tracking Audit Tool
Inspect supported GA4 tracking requests during one initial page load. Keep network observations separate from analytics receipt and real business outcomes.
Browser worker: setup required
Automatic checks are not connected yet. The administrator must deploy and verify an isolated browser worker. No paid analytics API is required by this implementation.
What this report can establish
Supported request patterns, observed HTTP responses and repeated-record review candidates in one bounded sample. An HTTP 2xx response is not proof of analytics receipt, correct attribution or a measured business outcome.
Questions and limits
Does this confirm my forms, calls or purchases are measured?
No. This first release observes one initial page load only. It does not submit forms, click call links, place orders or correlate a business outcome with an analytics record. Those journeys require separately approved controlled tests.
What does a successful HTTP response mean?
Only that a response was observed for that request. It does not prove processing, attribution, deduplication or receipt in the correct analytics account.
Why is an expected event missing?
Consent, timing, interactions, network blocking, first-party proxies, unsupported formats or server-side collection may explain it. Not observed in this bounded sample is not proof of broken tracking.
What source setup is required?
An administrator must deploy and verify an isolated Playwright/Chromium worker. The code needs no paid analytics API, but a suitable worker host is required. The website shows setup required until it is configured.
Will this send a test purchase or change consent?
The tool does not synthesize events or interact with the page. The target page can naturally emit tracking requests on load; only test pages you are authorized to inspect. No consent button is accepted or rejected.
What is private?
Checks require your own signed-in website session. Raw tracking payloads, cookies, client/session IDs and headers are not returned in reports. No report history is saved by this module. Event names, destination IDs and the submitted URL still warrant care when sharing exports.
Which platforms are supported?
Only a narrow set of GA4 web collection request patterns on known Google Analytics endpoints. Google Ads, Meta, server-side events, first-party proxies and analytics-account confirmation are not supported by this release.
Is the browser identical to a normal visitor?
No. Network-none Chromium uses a separate HTTPS IPv4 broker with public-address checks. Cookies and authentication headers are not forwarded. Compressed resources, unsupported methods, WebSockets and popups are blocked. Non-measurement resources honor bounded robots checks. These restrictions can change page behavior and produce partial results.