How to Set Up Enhanced Measurement in GA4

One of the more pleasant surprises for anyone new to GA4 is that a meaningful set of tracking works before you write a single line of custom code. Enhanced Measurement is GA4's built-in system for automatically capturing common interactions — scrolling, clicking outbound links, downloading files — without any manual event implementation. Getting it configured correctly saves you from re-inventing tracking that GA4 already gives you for free.

This guide covers what Enhanced Measurement tracks, how to configure it, and when you should turn a specific feature off.

What Enhanced Measurement Covers

When enabled on a web data stream, GA4 automatically tracks these events:

• scroll — fires once when a user scrolls to 90% of a page's depth.
• click (outbound clicks) — fires when a user clicks a link leading to a different domain.
• view_search_results — fires when a user performs an internal site search (GA4 detects this from URL query parameters like ?s= or ?q=).
• video_start, video_progress, video_complete — fire for embedded YouTube videos, tracking start, 10/25/50/75% progress milestones, and completion.
• file_download — fires when a user clicks a link to a common downloadable file type (PDF, DOCX, XLSX, ZIP, and similar).
• form_start, form_submit — fire when a user begins interacting with a form and when it's submitted.
• page_view — the baseline event, always on and not part of the toggle list.

Enabling and Reviewing Enhanced Measurement

1. Go to Admin → Data Streams.
2. Click your web data stream.
3. Under Enhanced measurement, confirm the toggle is on (it's enabled by default for new data streams).
4. Click the gear icon next to it to see and adjust individual toggles for each of the events listed above.

Each sub-event can be turned off independently, which matters because not every feature is useful for every site.

Configuring Internal Site Search Detection

By default, GA4 detects site search from common query parameter names (q, s, search, query, and a few others). If your site uses a non-standard parameter — say, find — you need to tell GA4 explicitly:

1. In the Enhanced measurement settings, click the gear icon.
2. Under Site search, add your custom query parameter to the list.
3. Save.

Without this, searches on your site simply won't register as view_search_results events, and you'll lose visibility into what people are actually looking for.

When to Turn Off Specific Features

• Turn off outbound click tracking if your site links out to affiliate or partner domains at extremely high volume — the event volume can clutter your Events report without adding much analytical value, especially if you already track those clicks with dedicated custom events carrying more context.
• Turn off video tracking if you don't embed YouTube videos, or if you use a different video platform (Vimeo, self-hosted) — Enhanced Measurement's video events only work with YouTube's embedded player.
• Turn off form tracking if you're already sending more specific custom form_submit-style events with richer parameters (like the specific form name or lead type) — otherwise you can end up with duplicate, less-useful signals for the same action.
• Leave scroll and file download on for almost every site — they're low-noise and genuinely useful for content sites without requiring any additional implementation.

Verifying Enhanced Measurement Events

Confirm events are firing correctly using Admin → DebugView:

1. Install the Google Analytics Debugger Chrome extension or add ?gtm_debug=x to your URL if using GTM's preview mode.
2. Browse your own site — scroll a page, click an outbound link, submit a form.
3. Watch the corresponding events appear in DebugView in real time, along with their parameters.

Layering Custom Events on Top

Enhanced Measurement is a starting point, not a replacement for purpose-built tracking. For example, the automatic file_download event captures that a file was downloaded, but if you want to distinguish a whitepaper download from a pricing sheet download with more specific business context, a custom event gives you more control:

document.querySelectorAll("a.download-whitepaper").forEach((link) => {
  link.addEventListener("click", () => {
    gtag("event", "whitepaper_download", {
      whitepaper_name: link.dataset.title,
      lead_source: "resource_library",
    });
  });
});

Running both — Enhanced Measurement for broad, low-effort coverage, and custom events for your highest-value interactions — gives you the best of both without redundant implementation work.

Common Configuration Mistakes

• Not customizing site search parameters, leading to a permanently empty view_search_results report despite an active search feature.
• Assuming all video tracking works automatically — it only works for the standard YouTube embed, not custom video players.
• Leaving redundant custom events running alongside Enhanced Measurement equivalents, inflating event counts without adding insight.
• Not testing after a redesign — a new frontend framework or component library can change how forms or links are rendered in the DOM, occasionally breaking Enhanced Measurement's detection logic silently.

Auditing Enhanced Measurement After a Redesign

Enhanced Measurement relies on GA4 recognizing certain patterns in your page structure — link elements, form elements, query parameters — and a site redesign or a migration to a new frontend framework can quietly break some of that detection without any obvious error. After any significant frontend change, it's worth re-running a quick manual audit:

1. Open DebugView and browse the redesigned site.
2. Confirm scroll events still fire near the bottom of representative long pages.
3. Click a handful of outbound links and confirm click events with outbound: true appear.
4. Submit a real form and confirm both form_start and form_submit fire as expected.

This takes a few minutes and catches a class of silent tracking regression that's otherwise very easy to miss until someone asks why a report looks emptier than it should.

Enhanced Measurement and Single-Page Applications

Because several Enhanced Measurement features rely on detecting standard DOM patterns and page-load behavior, single-page applications (React, Vue, Angular) can behave inconsistently — a client-side route change doesn't trigger the same lifecycle as a full page load, which can affect scroll and form detection in particular. If your site is a SPA, it's worth verifying each Enhanced Measurement feature specifically within your app's actual navigation flow, rather than assuming it behaves the same as a traditional multi-page site.

FAQ about Setting Up Enhanced Measurement in GA4

Do I need Google Tag Manager to use Enhanced Measurement?

No — it works with a direct gtag.js installation as well as through GTM. It's a property/data-stream-level setting, not a GTM-specific feature.

Will Enhanced Measurement track scroll depth on every page?

Yes, by default it tracks the standard 90% scroll milestone on all pages within the data stream, unless you've disabled the scroll tracking toggle.

Can I customize the scroll depth threshold?

No — the built-in scroll event fires at a fixed 90% depth. If you need custom thresholds (like 25%, 50%, 75%), you'll need to implement a custom scroll-tracking event instead.

Why isn't my internal site search showing up in reports?

Your search results URL likely uses a query parameter GA4 doesn't recognize by default — add it manually under the Site Search settings in Enhanced Measurement.

Does Enhanced Measurement work on single-page applications?

Mostly, but SPAs can behave inconsistently with automatic detection since there's no full page reload — it's worth verifying each Enhanced Measurement feature in DebugView specifically on your SPA before relying on it.

Is there a cost to enabling all Enhanced Measurement features?

No direct cost, but very high event volume from features you don't need (like outbound clicks on a link-heavy page) can make your Events report noisier and slightly harder to navigate.

Conclusion

Enhanced Measurement is the fastest path to useful Google Analytics tracking without writing custom code, but it's worth reviewing rather than leaving on autopilot. Configure site search detection for your actual URL structure, turn off what doesn't apply to your site, and layer custom events on top of the interactions that matter most to your website's business goals.