Event quality

GA4 event parameter auditor

Enter the full page URL you want to scan. We'll load it in a real browser and analyze it live.

Browser session capture

The tool opens the page in a headless Chromium session and records the cookies, requests, tags, and dataLayer activity visible during that run.

Scoped rule set

Each tool applies a narrow ruleset to the captured session. It is useful for implementation QA, not a full-site crawl or legal determination.

Point-in-time report

Results show what was observed in that session, with severity labels and evidence. Re-run after changes or if your site varies by region or user state.

What we check

Naming conventions

Validates snake_case naming. Catches CamelCase, spaces, reserved prefixes (ga_, google_, firebase_).

Required parameters

Checks that recommended events include their required parameters per the GA4 spec.

Duplicates & reserved names

Flags duplicate event names and events using Google-reserved names that will be silently dropped.

Parameter limits

Warns when events exceed the 25-parameter limit or measurement ID is inconsistent across hits.

How to read results

Events are decoded from GA4 network requests. Each event is checked against Google's naming rules and parameter spec.

Critical = Missing page_view or reserved name collision. Data loss.Warning = Naming violations (CamelCase) or missing recommended params.Pass = Event follows GA4 naming and parameter conventions.

Common issues we find

CamelCase event names like Add_To_Cart

GA4 requires snake_case. "Add_To_Cart" becomes a custom event instead of mapping to the built-in add_to_cart. Fix: rename to lowercase snake_case.

Missing page_view event

No page_view fires on load, breaking session tracking and engagement metrics. Fix: ensure enhanced measurement is enabled or fire page_view manually.

25+ parameters on a single event

GA4 silently drops parameters beyond 25 per event. Fix: consolidate related params or split into separate events.