Use one stable event name for each action, put changing details in parameters, and record both in a shared event dictionary. Google sets rules for valid names but does not require a universal team style such as snake_case, so agree on a house convention and apply it consistently.
What makes a useful GA4 event name?
Name the action the team wants to measure, not every detail about the circumstances. Keep the event name stable and put variable context—such as a form’s placement or type—in parameters. This makes one action easier to compare across locations and campaigns without multiplying near-duplicate event names.
As an Amazon Associate I earn from qualifying purchases.
For example, if a lead-form submission matches the meaning of Google’s recommended generate_lead event, use that event name and describe the form context with parameters. Confirm that the recommended event’s meaning and parameters suit your implementation before adopting it; the name is an illustration, not a Google-mandated convention. Google explains the role of event names and parameters in its custom events guidance.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Choose a team style, then apply Google’s naming rules
Google does not mandate snake_case or another universal casing style. A practical house style is lower-case words separated by underscores, such as form_submit: it is readable and uses permitted characters. Whatever style you choose, write it down and do not vary capitalization. GA4 event names are case sensitive, so names that differ only by capitalization are distinct events.
#1 Best Overall
- Start an event name with a letter.
- Use letters, numbers, and underscores; do not use spaces.
- Keep event and parameter names within 40 characters.
- Check event, parameter, and user-property names against Google’s reserved-name and reserved-prefix rules before implementation. The lists can change and Google says they are not exhaustive.
See Google’s current event naming rules for the full constraints and reserved lists. Do not treat an exception in a particular Analytics create-or-modify-event workflow as general permission to send reserved names from every collection method.
Check recommended events before creating a custom one
Before adding a custom event, search Google’s events reference. Use a recommended event when its documented meaning matches the action you need to measure and its parameters capture the context you need. If the meaning does not fit, or the required context cannot be represented appropriately, define a custom event rather than forcing a misleading match.
Rank #2
- Does the recommended event describe the same business action?
- Do its recommended parameters capture the necessary context?
- Does it suit the website or mobile-app implementation?
- Would a custom definition add reporting and maintenance work without adding useful meaning?
Respect collection limits for the implementation you use
Google’s developer references specify a 40-character maximum for event and parameter names. For Measurement Protocol, the reference also specifies no more than 25 parameters per event; parameter values can be up to 100 characters for standard Analytics properties and 500 characters for Analytics 360 properties. These value limits are specific to the Measurement Protocol reference, not a blanket statement about every collection method. Check the relevant implementation documentation before relying on method-specific behavior.
Keep one shared event dictionary
Google does not prescribe a particular registry format. As a team practice, keep a shared dictionary beside the tracking plan or implementation so analytics, product, marketing, and engineering use the same definitions. Record these fields for each event:
- Canonical event name: the exact spelling and casing to implement.
- Meaning and trigger: what the event represents and precisely when it fires.
- Parameters: each parameter’s definition, expected values, and when to send it.
- Owner: the person or team responsible for the definition.
- Implementation surface: website, mobile app, or other applicable collection path.
- Review status: whether the name and definition have been checked against recommended events, reserved names, and current limits.
Give the registry a review owner and revisit names when the product, implementation, or Google’s rules change. Link the current official naming rules in the registry so new proposals are checked against the same source.
Quick Recap
Best Value
Rank #4
A lightweight naming workflow
- Describe the action. Write in plain language what users do and what counts as the event trigger.
- Search recommended events. Compare the action and needed context with Google’s documented event meanings and parameters.
- Choose the canonical name. Use a suitable recommended name or a custom action name, following the team’s documented style.
- Move variable details into parameters. Avoid separate event names for differences that are only context, such as form type or placement.
- Validate before release. Check spelling, case, first character, allowed characters, 40-character name limits, reserved names and prefixes, and the applicable collection-method limits.
- Record and review. Add the definition, parameters, trigger, owner, and implementation surface to the shared dictionary before teams depend on the event in reporting.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
