GA4 Event Taxonomy: A Practical Guide to Naming Conventions

Everything in Google Analytics 4 is an event. Page views, transactions, button clicks, video plays, scroll depth, form submissions — all of them enter GA4 as an event with associated parameters. While this event-based data model offers unprecedented flexibility compared to Universal Analytics, it is also a double-edged sword. Without a strict, disciplined event taxonomy, your GA4 property quickly descends into an unusable mess of conflicting names (button_click vs click_button vs btnClick), orphan parameters, and broken reports. Here is how to design a rock-solid GA4 event taxonomy that scales effortlessly.

The Four Tiers of GA4 Events

Before creating a single custom event, you must understand the hierarchy of events in GA4:

1. Automatically Collected Events: Collected by default when the GA4 tag is loaded (e.g. first_visit, session_start, user_engagement).
2. Enhanced Measurement Events: Toggled on in your GA4 Web Stream settings (e.g. page_view, scroll, click, view_search_results, file_download).
3. Recommended Events: Standardized event names designed by Google for specific business verticals (e.g. generate_lead, purchase, sign_up, view_item). Always prefer recommended event names because they unlock built-in GA4 reporting tables and machine learning features.
4. Custom Events: Events you invent yourself when no recommended event fits the action (e.g. filter_applied, calculator_completed).

The 7 Golden Rules of Event & Parameter Naming

• 1. Strict snake_case Everywhere: Always use lowercase letters and underscores (e.g. generate_lead, form_name). GA4 is case-sensitive — Generate_Lead and generate_lead are treated as two distinct events.
• 2. Object + Action (Noun + Verb) Convention: Name events starting with the object followed by the action taken, or use Google's standard verb + noun convention (e.g. form_submit, file_download, cta_click). Be consistent across your entire organization.
• 3. Adhere to Hard Character Limits: Event names must not exceed 40 characters. Parameter names must not exceed 24 characters (or 40 characters for user properties).
• 4. Never Use Reserved Prefixes: Avoid starting custom event names with ga_, firebase_, or google_ — these prefixes are reserved for internal Google systems.
• 5. Reuse Parameter Names Globally: Don't create contact_form_name, newsletter_form_name, and quote_form_name. Use a single reusable parameter: form_name. This saves your 50 custom dimension quota in GA4 Standard.
• 6. Keep Event Volume Under Control: Standard GA4 properties have a limit of 500 uniquely named events per property. Aim for fewer, parameter-rich events rather than hundreds of distinct event names.
• 7. Never Pass PII: Never capture emails, phone numbers, full names, or physical addresses in custom event parameters.

Event Taxonomy Blueprint: Lead Gen & E-Commerce

Example: Clean GTM dataLayer Implementation

Here is an example of an enterprise-grade dataLayer push for a lead generation form submit:

window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  event: 'generate_lead',
  form_name: 'contact_consultation_form',
  form_id: 'contact_form_main',
  lead_type: 'enterprise_tracking_audit',
  lead_value: 0,
  currency: 'GBP'
});