Generate consistent GA4 event names with proper snake_case schema.
Inputs
Generated event name
—
Suggested GA4 events for this category
Event Name
When to fire
Recommended params
About this tool
GA4 event naming is the foundation of every analytics setup, and the place most operators introduce inconsistencies that haunt them for years. Mixed case, snake-case-some-things-camelCase-others, "Add to cart" vs "add_to_cart" — each variation creates a different event in GA4 and fragments your data.
This tool generates GA4-compliant event names from human descriptions. It applies snake_case lowercase, validates length (40-char max), and aligns with Google\'s recommended event names for ecommerce flows. The category dropdown surfaces the recommended event names for each common analytics use case.
The discipline is one-time: establish the naming convention before implementing tags. Once events are flowing into GA4 with inconsistent names, fixing them requires backfill (deleting old events) or alias mapping (which adds complexity to every report). Better to get it right at setup.
Pair with the UTM Builder (campaign tracking conventions) and the Conversion API Health Check tool (server-side event quality). Together they form the core of a clean analytics stack — clean events, clean campaigns, clean attribution.
Frequently asked questions
Why does event naming consistency matter?
GA4 treats event names as exact strings. "Add To Cart", "add_to_cart", and "addToCart" are three different events. Inconsistent naming fragments your data — you can't see total cart-adds because they're split across naming variations. One misnamed event means weeks of lost analytics.
What's GA4's recommended naming convention?
Snake_case lowercase: add_to_cart, view_item, begin_checkout. Match GA4's recommended event names exactly when applicable — those have automatic dimensions and reports. Custom events should also be snake_case lowercase for consistency.
Should I use GA4's recommended events or custom?
Use recommended (e.g., view_item, add_to_cart, purchase) for standard ecommerce flows — they get automatic Enhanced Ecommerce reports. Use custom for non-standard interactions specific to your business (e.g., wishlist_add, size_chart_view).
How many parameters per event?
GA4 supports up to 25 parameters per event, but practical limit is 5-10. More than that becomes hard to maintain. Stick to value (price), currency, item_id, item_name, item_category, plus 1-2 business-specific params.
What's reserved that I should avoid?
Don't use GA4's automatically-collected event names (page_view, session_start, first_visit, etc.) or system parameters. Don't exceed 40 characters in event names. Don't use spaces, special chars, or capital letters.