GA4 recommended, automatic and custom events: which to use when

Short answer: if Google publishes a recommended event name for the thing you're measuring, send that name, spelled exactly as Google spells it, even when it reads oddly for your business. Recommended events "automatically update predefined dimensions and metrics", and sending the ecommerce set "populates the Ecommerce purchases report" while the lead-generation set "populates the Lead acquisition report" (Analytics Help, checked 13 August 2026). An invented name carrying byte-for-byte identical data populates none of that. The cost of inventing one isn't the quota everybody warns you about, either: Google's limits page states there is no limit on distinctly named events for web data streams, and puts the 500 figure on app streams only (Analytics Help, checked 13 August 2026). Nothing stops you. That's the problem.

Two of the four event types arrive whether you ask for them or not

You are choosing between four categories, and only two are yours to decide.

Automatically collected events come with the tag. Google lists page_view, session_start, first_visit and user_engagement among the events collected for web streams "as long as you use the Google tag or the Google Analytics for Firebase SDK", alongside click, scroll, file_download, the video_* set, form_start, form_submit and view_search_results (Analytics Help, checked 13 August 2026).

Enhanced measurement is the layer that switches most of those on. It "lets you measure interactions with your content by enabling options (events) in the Google Analytics interface", and "no code changes are required" (Analytics Help, checked 13 August 2026). Eight options sit behind toggles in the data stream settings.

Recommended events are Google's published names for behaviours it can't detect on its own. The help page is blunt about why they aren't automatic: "Because these events require additional context to be meaningful, they're not sent automatically" (Analytics Help, checked 13 August 2026). Google knows a purchase happened only if you tell it, and it knows what the purchase was worth only if you send the prescribed parameters with it.

Custom events are everything else. They're the right answer for genuinely bespoke behaviour — a configurator step, a saved quote, a specific in-app action nobody else has. They're the wrong answer for anything on Google's list.

Inventing an event name costs you the report shelf, not a quota

The report shelf is prebuilt and it's wired to specific strings.

This is where the standard advice undersells the decision. People imagine the penalty for a custom name is a limit somewhere. There isn't one on web: Google's own limits table reads "There is not limit on the number of distinctly named events for web data streams", with "500 per app user" applying to app data streams (Analytics Help, checked 13 August 2026, typo Google's). You can send four hundred invented names and GA4 will take all of them.

What you forfeit is everything downstream. Recommended events "automatically update predefined dimensions and metrics", and specific reports are keyed to specific event sets: the ecommerce events populate the Ecommerce purchases report, the lead-generation events populate the Lead acquisition report, the games events populate the games reports (Analytics Help, checked 13 August 2026). Name your checkout completion order_complete instead of purchase and the revenue figure exists in your property but the ecommerce reporting stays blank, because nothing told it where to look.

Then the work starts. Your parameters are inert until you register them as custom dimensions, and that's a real budget: 50 event-scoped custom dimensions on a standard property, 25 user-scoped, 10 item-scoped, rising to 125, 100 and 25 on 360 (Analytics Help, checked 13 August 2026). Registration isn't instant either — "after 24-48 hours, you can start to report on and advertise with the custom dimension or metric" — and if you fill the quota, "you'll need to wait 48 hours after deleting" before you can add another (Analytics Help, checked 13 August 2026).

So the true price of a bespoke name is one of your fifty dimension slots, a two-day wait, and an exploration you have to build by hand to answer a question the prebuilt report would have answered for free. Multiply that by a team that named twelve things its own way.

Enhanced measurement is probably already collecting what you're about to tag twice

Check the toggles before you write a single tag, because duplicate collection is the most common self-inflicted wound here.

The eight enhanced measurement options cover page views, scrolls, outbound clicks, site search, video engagement, file downloads and form interactions (Analytics Help, checked 13 August 2026). Two behave in ways that catch people out. Scroll fires once per page at 90% vertical depth, so it's a "reached the bottom" flag rather than a scroll-depth metric — if you need quartiles you're building them yourself. Form interactions produce form_start and form_submit automatically, which is exactly the pair most teams hand-tag in GTM on day one, and then wonder why submissions read double.

Turning individual options off is a two-minute job in the interface: Admin, then Data streams, then your stream, then the settings icon under Enhanced measurement, where you "edit individual options as needed" (Analytics Help, checked 13 August 2026). Page views are the exception — Google states they "are collected automatically" and "you cannot turn off collection" (Analytics Help, checked 13 August 2026).

The sequence that avoids the mess: open the toggles, write down what's already firing, then decide what genuinely needs a tag. Anything you disable and replace should be replaced with the recommended name, not a house one.

Key events are the Analytics word; conversions now belong to Ads

The rename was not cosmetic and it changed which tool owns which number.

Google's stated reason: "We've aligned how we define the term 'conversion' between Google Ads and Analytics to make it simpler to measure the performance of your Google Ads campaigns across the two platforms" (Analytics Help, checked 13 August 2026). A key event is "an event that measures an action that's particularly important to the success of your business", and a conversion is now the thing "created from a Google Analytics event" that measures important actions "in both Google Analytics and Google Ads" (Analytics Help, checked 13 August 2026).

The practical consequence is a reporting boundary people keep walking into: "Google Ads conversions don't appear in standard Google Analytics reports" (Analytics Help, checked 13 August 2026). Two numbers, two homes, one underlying event. If your weekly report puts an Ads conversion count next to a GA4 key event count and someone asks why they differ, the answer starts here rather than with a tagging fault.

One trap worth writing on a sticky note. Event names are capped at 40 characters, and Google adds: "If you mark an event as a key event and the event exceeds 40 characters, then the event will not be reported" (Analytics Help, checked 13 August 2026). Not truncated. Not warned about. A descriptive custom name like newsletter_signup_from_blog_footer_variant_b is 44 characters, and marking it as a key event is the moment it disappears. The recommended names are all short, which is one more quiet argument for using them.

What to do this week

Open your Events list and sort by name. Every event that has a recommended equivalent gets renamed at the tagging layer, and you accept the discontinuity in the reports rather than living with the split forever. Renaming is cheap now and expensive in a year.

Then open the enhanced measurement toggles and reconcile them against your GTM container. Anything collected twice gets one source turned off. Anything you meant to collect and didn't gets added with Google's name for it.

Finally, check the length of any custom event you've marked as a key event, because the 40-character rule fails silently and it will not tell you. If the numbers still disagree after all that, the fault is usually further upstream than naming — in what the consent layer allows to fire, and what the bidding platform ends up seeing. That repair work is what we do. The same naming discipline governs anything you push in server-side, which is where the Measurement Protocol gets interesting.

Sources

1. 1.Analytics Help — [GA4] Recommended events · Checked 2026-08-13
2. 2.Analytics Help — [GA4] Automatically collected events · Checked 2026-08-13
3. 3.Analytics Help — [GA4] Enhanced measurement events · Checked 2026-08-13
4. 4.Analytics Help — [GA4] Analytics data collection and configuration limits · Checked 2026-08-13
5. 5.Analytics Help — [GA4] Custom dimensions and metrics · Checked 2026-08-13
6. 6.Analytics Help — [GA4] Key events · Checked 2026-08-13
7. 7.Analytics Help — [GA4] Conversions vs. key events · Checked 2026-08-13