Event Naming Convention & Parameter Validator for GA4

How to check your GA4 event naming convention

A GA4 event naming convention only works if every name also passes Google's own rules. This checker reads your whole list at once and tests each name against Google's event naming rules and collection limits. Then it suggests a clean name for each one that breaks a rule.

1. Paste your events. Use a plain list, or copy rows from your tracking plan spreadsheet: event, parameter and an example value. Developers can switch to Code or JSON and paste gtag('event', …) calls, dataLayer.push() code or a Measurement Protocol body.
2. Add user properties if you use them. They have tighter limits: 24 characters for the name and 36 for the value.
3. Pick your property and stream. Analytics 360 raises the parameter limits. Web and app streams reserve different names, so choose the one you send to.
4. Read the summary. Errors are names GA4 won't process. Warnings are names that work but cause messy reports, such as Add_to_cart next to add_to_cart.
5. Copy the fixes. The rename list maps each old name to a suggested one. Download it, or the full results, as CSV for your developer or agency.

What the checker tests

• Shape — starts with a letter, only letters, numbers and underscores, no spaces, at most 40 characters.
• Reserved words — Google's reserved event names for web and app, the query_id prefix, and the parameter prefixes _, firebase_, ga_, google_ and gtag..
• Duplicates — names that differ only in case, dashes or underscores, which GA4 counts as separate events.
• Recommended events — home-made names like addToCart or signup that should be Google's recommended event names, and recommended events that miss a required parameter.
• Limits — 25 parameters per event, 100-character values, 25 user properties per property (higher on 360).

What to do next in GA4 and Tag Manager

1. Fix the name where it is set. In Google Tag Manager that is the Event Name field of each GA4 Event tag. In code it is the second argument of gtag('event', …). Change it there, not in a report.
2. Or rename it inside GA4. In Admin, under Data display, click Events, then Modify event › Create. Match event_name to the old name and set it to the new one. Google's modify events page says this does not change historical data.
3. Register the parameters you report on. In Admin › Data display › Custom definitions, open the Custom dimensions tab and click Create custom dimensions. Choose Event scope and type the parameter name exactly as your tag sends it. A standard property has 50 event-scoped slots, so pick only the ones you use.
4. Test before you publish. Open GTM Preview or GA4 DebugView and check that each event arrives with the new name and its parameters.

Common GA4 event naming errors and fixes

GA4 custom event not showing up

The most common cause is a name GA4 refuses to process: over 40 characters, a space, a dash, or a first character that is a number. Nothing warns you — the event is simply missing. Shorten or rename it and test again in DebugView.

Two events for one action

Because names are case sensitive, Sign_Up from one tag and sign_up from another become two events. Pick one spelling and fix every tag that sends the others.

Using a reserved event name

Naming your button tracking click or your form tracking form_submit mixes your data with GA4's own enhanced measurement events. Use a name of your own, such as cta_click or quote_form_submit.

Parameter value cut off or missing

Long values like full page titles, search queries or product lists can pass the 100-character limit. Send shorter values, or split the information into two parameters.

Custom dimension can't be created

GA4 refuses some parameter names when you register a custom dimension — reserved ones such as user_id, session_id or gclid, and names with symbols or non-English letters. Rename the parameter in your tag first.