Free tool · T-08

GTM Event Naming Audit

Paste your GA4 event names. Get instant validation against Google's recommended naming conventions, reserved prefix rules, and formatting standards.

Event namesOne per line or comma-separated
[01] Rules

GA4 event naming conventions

Google Analytics 4 has strict rules for event names. Breaking them doesn't always throw an error — it silently corrupts your data. These four rules prevent the most common issues.

01

Use snake_case exclusively

GA4 event names must be lowercase with underscores. No spaces, hyphens, or camelCase. "add_to_cart" not "addToCart" or "Add To Cart".

02

Stay under 40 characters

GA4 truncates or rejects event names longer than 40 characters. Keep names concise but descriptive.

03

Never use reserved prefixes

Prefixes like ga_, google_, firebase_, and gtag_ are reserved by Google. Using them will cause silent data loss or overwrites.

04

Prefer recommended events

GA4 has 40+ recommended event names with built-in reporting. Using them unlocks automatic audience triggers, conversion tracking, and ecommerce reports.

[02] Common mistakes

What bad event names look like

Wrong
Correct
Why
addToCart
add_to_cart
camelCase is not supported — GA4 treats different cases as different events
ga_signup
sign_up
"ga_" is a reserved prefix and "signup" should be the recommended "sign_up"
Button Click
button_click
Spaces break event tracking and uppercase letters create duplicate events
purchase-complete
purchase
Hyphens are not valid and the recommended event is simply "purchase"
user_completed_the_onboarding_tutorial_flow
tutorial_complete
Exceeds 40 chars and duplicates the recommended "tutorial_complete" event
[03] FAQ

Common questions

Does GA4 actually reject badly named events?

Not always visibly. Some events with reserved prefixes are silently dropped. Others with bad casing create duplicate entries that split your data. The damage is quiet — you only notice it months later when reports don't add up.

Can I rename events after they're live?

No. GA4 has no rename feature. You'd need to update the event name in GTM/code and lose historical continuity. Getting names right before launch saves months of cleanup.

What happens if I send a recommended event without its required parameters?

The event fires but you lose built-in reporting. For example, sending "purchase" without "value" and "currency" parameters means it won't appear in ecommerce revenue reports.

Should I use recommended events or custom events?

Always check the recommended list first. GA4's built-in reports, audiences, and conversion features are designed around these events. Only create custom events when no recommended event fits your use case.

[ ⌖ ] Need a full audit?

Want us to audit your entire GTM setup?

We review your event taxonomy, data layer, trigger logic, and conversion tracking end to end.