Tracking Preflight

GA4 / GTM / Clarity public page preflight

Check whether tracking is visibly firing before you trust the setup.

Scan a public URL, optionally click a consent button or event selector, then get a plain-English report that separates visible proof from things that still need GTM, GA4, or consent-mode confirmation.

Run preflight

Prototype preview

Fast product preview with no browser scan.

Auto consent

Try safe cookie banner clicks before measuring post-consent events.

Current mock input: https://www.typeform.com/. Real remote scanning needs Browserless or a self-hosted Playwright worker.

Environment status

Public mode uses mock and fixture reports. Local browser scanning is disabled.

Environment: checking

View health API

Sample report

Consent gated

Needs review
Scripts
4
Collects
2
Failures
1
Consent
1
GA4G-N6F0VDRT9W
GTMGTM-WH2ZQ3X
ClarityNot visible

Decision for this scan

Do not treat this as broken yet. The page showed partial evidence, so the next step is to check consent, GTM Preview, regional loading, or the selected event.

Scan setup

Mode
Mock
URL
https://www.typeform.com/
Consent
Auto safe
Event
Signup

Findings

  • GA4 and GTM were visible on the public page.
  • Auto consent clicked an accepted cookie banner before the event pass.
  • One Google Ads conversion request appeared after consent, but one tracking request failed.

Recommended next steps

  • Compare before-consent and after-consent reports.
  • Open GTM Preview to confirm which tags fire after consent.
  • Inspect the failed conversion request in the browser Network panel.

What this checks

Public page requests for GA4, GTM, Universal Analytics, Clarity, Google Ads conversion, supported consent clicks, redirects, failed tracking requests, and obvious malformed tracking URLs.

What this cannot prove

It cannot prove attribution quality, server-side tagging, private dashboard data, authenticated user flows, or every consent mode detail. Those still need native tools such as GTM Preview, GA4 Realtime, DebugView, and Search Console.

Workflow for small teams

1

Scan the landing page

Confirm visible install signals before sending traffic or submitting launch docs.

2

Repeat after consent

Click the cookie banner or use a safe selector to compare pre-consent behavior.

3

Trigger one key event

Use a button selector for signup, download, checkout, or outbound click checks.

4

Keep a baseline

Save reports after deploys so broken tracking is caught before it becomes invisible.