GA4 Event Name Checker

Paste the event names from your measurement plan and check them against Google Analytics 4's naming rules before they ship: the 40-character limit, allowed characters, reserved names and prefixes, collisions with auto-collected events, and the case-sensitivity trap that silently splits your data.

  • generate_leadRecommended event
    • Matches a Google recommended event — good choice, but send the documented parameters with it so standard reports populate.
  • Form SubmitInvalid
    • Contains spaces — use underscores instead (e.g. sign_up_click).
    • Contains uppercase letters. Event names are case-sensitive in GA4 (Login and login are two different events) — lowercase snake_case avoids accidental splits.
  • ga_signupInvalid
    • Starts with the reserved prefix "ga_".

Runs entirely in your browser — nothing you type is sent or stored.

The Rules It Checks

Syntax. Event names must be 40 characters or fewer, start with a letter, and use only letters, numbers, and underscores. Spaces, hyphens, and punctuation are rejected by GA4.

Reserved names and prefixes. Names beginning with google_, ga_, firebase_, or an underscore are blocked, and a short list of names (e.g. session_start, first_visit) is reserved by GA4 itself.

Auto-collected collisions. Events like page_view, scroll, form_submit, and video_start are collected automatically or by enhanced measurement. Sending them manually alongside the automatic version is the classic source of doubled counts.

Conventions.GA4 event names are case-sensitive, so the checker flags uppercase letters and suggests lowercase snake_case — and it recognises Google's recommended events (purchase, generate_lead, sign_up, …) so you know when documented parameters are expected.

Naming is the easy 10% of event tracking — deciding which events represent your funnel and implementing them cleanly through GTM is the other 90%. That process is covered in the GA4 measurement plan guide and on the Google Tag Manager consulting page.

Frequently Asked Questions

What are the GA4 event naming rules?
GA4 event names must be 40 characters or fewer, start with a letter, and contain only letters, numbers, and underscores. They cannot begin with the reserved prefixes google_, ga_, firebase_, or an underscore, and a small set of names (like session_start and first_visit) is reserved outright.
Are GA4 event names case-sensitive?
Yes. GA4 treats Login and login as two different events, which silently splits your data. The standard convention is lowercase snake_case (e.g. lead_form_submit) so casing can never fragment an event.
Which GA4 event names are reserved?
For web (gtag.js), reserved names include session_start, first_visit, first_open, user_engagement, in_app_purchase, app_remove, and the app_store_* subscription events. Separately, names like page_view, scroll, click, form_submit, and video_start are collected automatically or by enhanced measurement — sending them manually risks double counting.
Should I use Google's recommended event names?
When your action matches one — yes. Recommended events like purchase, generate_lead, login, and sign_up power standard reports and downstream features, but only if you also send the parameters Google documents for each. For actions with no recommended equivalent, a clear custom snake_case name is correct.
Does this checker send my event names anywhere?
No. Validation runs entirely in your browser; nothing you type is transmitted or stored. The rules are current as of mid-2026 — Google's documentation is the source of truth if they change.

Related Reading