Recommended vs custom events
GA4 events come in three tiers: automatically collected, recommended, and custom. Automatic events fire without setup; recommended events have Google-defined names and parameters that unlock standard reports; custom events are ones you invent. The practical rule is to prefer a recommended name whenever one fits, because custom names miss out on prebuilt dimensions, reports, and predictive features.
The three tiers
Automatically collected events (like page_view or first_visit) require no code. Recommended events have predefined names and parameters Google publishes for specific industries (retail, gaming, jobs, travel). Custom events are names you define yourself when no recommended event fits.
The hierarchy matters because GA4's standard reports, default dimensions, and some predictive metrics are keyed to recommended (and automatic) event names.
Why prefer recommended
When you fire a recommended event with its documented parameters, GA4 recognises it and powers the relevant reports without extra setup. A custom event with a different name carries the same data but stays invisible to those prebuilt surfaces until you build custom reports. Reserve custom events for genuinely unique actions, and follow naming conventions for those.
- Automatic: no setup (page_view, scroll, etc.)
- Recommended: Google-defined names unlock reports
- Custom: your own names for unique actions
How it appears in analytics and logs
If an action has a recommended event, using a custom name instead means GA4 will not map it to its standard reports — a self-inflicted reporting gap.
Diagnostic use case
Decide whether to use a recommended event name or a custom one, favoring recommended names so reports populate automatically.
What WebmasterID can help detect
WebmasterID encourages consistent, documented event names so first-party analytics stays interpretable regardless of platform.
Common mistakes
- Inventing a custom name when a recommended one exists.
- Ignoring recommended parameter names, breaking report mapping.
- Using inconsistent custom names across pages.
Privacy and accuracy notes
Whichever tier you choose, event parameters must stay PII-free. Naming tier does not change privacy obligations. Educational, not legal advice.
Related pages
- Custom events: tracking what matters to you
Custom events capture meaningful actions a pageview cannot — a CTA click, a signup, a video play, a form submit. The value is in a consistent naming taxonomy and well-chosen properties. The risk is putting personal data into event names or properties, which turns analytics into surveillance. This page covers both.
- Event naming conventions
An event naming convention is the agreed rule for what events are called: the case, the separators, and the vocabulary. It sounds trivial but it is the difference between clean analytics and a fragmented mess where signup, sign_up, and SignUp count as three things. This page covers the conventions that work, reserved names to avoid, and why a documented taxonomy matters more than any single rule.
- Enhanced measurement (auto events)
Enhanced measurement is a GA4 setting that automatically collects a set of interaction events — scrolls, outbound clicks, site search, video engagement, file downloads, and form interactions — without extra code. It is convenient but not magic: it only covers standard patterns, can over- or under-count, and each option can be toggled. This page explains what it does and its limits.
- Event tracking docs
Choose event names that map to reports.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.