Automatic vs manual events in GA4
GA4 events come in tiers by how much you do to get them: automatically collected events need no setup, enhanced-measurement events are toggled on per stream, recommended events you send manually using predefined names, and custom events you both name and send. Knowing which tier an event belongs to tells you whether it needs code, a toggle, or nothing — and prevents duplicate or missing events.
What this means
GA4 organises events into tiers. Automatically collected events (first_visit, session_start, user_engagement, and app lifecycle events) require no setup. Enhanced-measurement events (scroll, outbound click, site search, video, file download, form interactions) are collected when you enable that setting on a web stream. Recommended events have predefined names for common use cases but you must send them. Custom events are ones you name and send yourself.
Choosing the right tier
Before instrumenting anything, check whether GA4 already provides it. If it is automatic or covered by enhanced measurement, sending your own version duplicates it. If it is a common action, use the recommended event name so the platform understands it consistently — only fall back to a custom name when nothing fits. Getting the tier right avoids both gaps (assuming something is automatic when it is not) and double-counting (re-sending what already exists).
- Automatic: no setup (lifecycle, engagement)
- Enhanced measurement: toggle per web stream
- Recommended: predefined names you send; custom: you name + send
How it appears in analytics and logs
An event you instrumented manually that already exists automatically (or via enhanced measurement) appears twice; an event you assumed was automatic but is not simply never shows.
Diagnostic use case
Map each event you need to the right tier — automatic, enhanced measurement, recommended, or custom — so you collect it without duplicating it.
What WebmasterID can help detect
WebmasterID favours explicit, intentional events over broad auto-collection, so what you measure is deliberate and free of PII-shaped parameters by design.
Common mistakes
- Manually sending an event GA4 already collects automatically.
- Inventing a custom name when a recommended one exists.
- Assuming an action is automatic when it needs code.
Privacy and accuracy notes
Regardless of tier, the same rule applies: no personal data in event names or parameters. Automatic does not mean exempt from data minimisation. This is educational, not legal advice.
Related pages
- 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.
- 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.
- Reserved and restricted event names
GA4 reserves a set of event names, parameter names, and user-property names for its own use, plus reserved prefixes you cannot start your own names with. Reusing a reserved name (like a built-in event) or a reserved prefix (like ga_, google_, firebase_) causes the event to be dropped or mishandled. Knowing the restricted list keeps your custom events from silently failing.
- Events reference (docs)
How WebmasterID collects first-party events.
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.