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.
What this means
Enhanced measurement is a toggle in a GA4 web data stream. When on, the tag automatically emits events for: page views, scrolls (90% depth), outbound clicks, site search, video engagement (embedded YouTube), and file downloads — plus form interactions. You get these without writing event code.
Limits and control
Auto-collection only recognises standard patterns: site search is detected from common query parameters, scroll fires at a fixed depth, video needs the supported embed. Anything bespoke still needs a custom event. Each option can be turned off individually, which matters when, for example, site-search queries might contain personal data you do not want stored.
- Covers scroll, outbound click, site search, video, downloads, forms
- Detects standard patterns only — bespoke needs custom events
- Each option is individually toggleable
How it appears in analytics and logs
Enhanced-measurement events appearing without any code means auto-collection is on. Unexpected scroll or click counts usually mean an enabled option is matching more than you intended.
Diagnostic use case
Decide which automatic events to enable so you get useful interaction data without noise, and know which actions still need explicit custom events.
What WebmasterID can help detect
WebmasterID favours explicit, tagged events over broad auto-collection, so what you measure is intentional and free of PII-shaped parameters by design.
Common mistakes
- Assuming auto events cover every interaction.
- Leaving site_search on when queries may contain personal data.
- Double-counting by adding custom events that duplicate auto ones.
Privacy and accuracy notes
Auto events still follow the same rule: no personal data in parameters. Site-search terms in particular can contain personal data, so review what site_search captures. This is educational, not legal advice.
Related pages
- The click event and outbound clicks
A click event records that a visitor activated a link or element. The most common analytics use is the outbound click — a click on a link leaving your domain — which a normal page_view can never capture because the destination is another site. This page covers what to record on a click, how outbound detection works, and which properties stay privacy-safe.
- The scroll event and depth tracking
A scroll event records that a visitor scrolled to a depth on the page. In GA4 enhanced measurement, a single scroll event fires once per page when the visitor reaches 90% of the page height. It is a coarse engagement signal — useful for spotting content people do not reach, but limited because the default is one threshold, not a continuous read-depth curve.
- 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 Explorer
See exactly which events are being collected.
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.