GA4 Quality

Event Parameter Auditor

Paste your URL below. We'll decode every GA4 event from network requests and check naming conventions, required parameters, duplicates, and limits.

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

Real browser scan

We launch a headless Chromium browser and load your page exactly like a real visitor would.

Instant analysis

Every network request, cookie, and dataLayer push is intercepted and analyzed in real-time.

Actionable findings

Get severity-scored results with specific fix instructions. Share the report via a unique link.

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.