validateur de nom d'événement GA4
Paste a GA4 event name and parameters. The tool checks naming conventions (snake_case lowercase), GA4 limits (40-char name, 25 parameters per event), reserved-name conflicts, and best practices.
Entrées d'événements
Validation Report
How to use the GA4 Event Name Validator
Type your event name. Add parameters one per line. The validator checks name length, snake_case format, reserved-name conflicts, parameter count, and recommended-event status.
Pourquoi cet outil est important
GA4 silently drops events that violate naming rules — you only notice weeks later when reports are empty. A 30-second validation before deployment catches every common mistake.
Cas d'utilisation courants
- Pre-deployment QA of new tracking
- Standardizing event names across teams
- Migrating from Universal Analytics
- Spec-reviewing developer proposals
- Training new analytics team members
GA4 naming conventions
Event names: lowercase snake_case, max 40 chars, must start with a letter, no reserved prefixes (ga_, google_, firebase_). Parameter names: same rules, max 40 chars, max 25 parameters per event.
Foire aux questions
Why does GA4 reject events that violate rules?
GA4 strictly enforces the spec. Events that violate get dropped silently which makes analysis impossible.
Should I use GA4 recommended events?
Yes when applicable — sign_up, login, purchase, add_to_cart. Recommended events get auto-tracked dimensions.
Is camelCase ever ok?
No — GA4 requires snake_case strictly. camelCase events get dropped silently. The #1 mistake teams migrating from UA make.
How many events can I send total?
500 distinct event names per property. Audit periodically.
Need a GA4 implementation built right the first time?
Riman Agency runs GA4 + GTM implementations.