Don't have one? Create one ↗
Measurement planning & the dataLayer

Lesson 4 of 7

Event Naming Conventions

GA4 groups data by event and parameter name, so inconsistent names quietly fragment your reports: signup, sign_up and SignUp become three different things. Agree on a convention once and apply it everywhere.

User signs upAVOIDDOsignupSign_UpSignUpsign_upsame name on web, app & serverGA4 · EVENTSsignup12Sign_Up8SignUp53 rows, counts splitGA4 · EVENTSsign_up251 row, full count

Do use lowercase snake_case (add_to_cart), verb_noun in the present tense for actions, GA4 recommended events where they exist, and consistent parameters like value, currency and item_id. Avoid spaces, camelCase or mixed casing, vague names like click or event1, a new name for an event you already have, and different parameter names for the same value.

Where Google publishes a recommended event (such as purchase or generate_lead), use it: those names unlock built-in reporting and ad features.

Key takeaway

Pick one casing and pattern, prefer GA4 recommended names, and reuse parameter names across events.