A recommended event is an event name, with a set of expected parameters, that Google has defined in advance for a common action such as signing up, generating a lead or making a purchase, and which you implement yourself in GA4. Using Google’s exact names and parameters lets GA4 fill its built-in reports and features with your data without extra configuration.
How recommended events work
GA4 sorts events into four groups. Automatically collected events, such as first_visit and session_start, are sent by the tag with no extra work. Enhanced measurement events, such as scrolls, outbound clicks and file downloads, switch on with a setting. Recommended events come next: Google publishes the names and parameters, but nothing is sent until you add the tracking. Anything outside those lists is a custom event, named by you.
Google groups its lists by type of business. Some apply to almost any site, such as login, sign_up, search and share. For lead generation there is generate_lead, plus later stages such as qualify_lead and close_convert_lead for businesses that send CRM progress back to GA4. Ecommerce has the whole shopping journey, from view_item and add_to_cart through begin_checkout and add_payment_info to purchase and refund. There are further sets for games and other app types.
Each event comes with expected event parameters. A purchase needs a transaction_id, value, currency and an items array describing the products. generate_lead accepts a value and currency, so a lead can carry an estimated worth. When names and parameters match Google’s specification exactly, GA4’s monetisation and product reports, and imports into Google Ads, understand them straight away.
Why it matters
Many GA4 reports only work if data arrives in the expected shape. The ecommerce purchases report stays empty if your shop sends “order_complete” instead of purchase, and product reports show “(not set)” when item details are missing. Getting the names right at the start avoids rebuilding later, and avoids history that cannot be repaired, because GA4 does not rename events that have already been collected.
Standard names also make your setup readable by other people. A UK business that changes agency, or brings in a freelancer for a few months, benefits when the tracking uses Google’s names rather than a private scheme that only the original installer understood.
Common mistakes
- Inventing a custom name for an action Google already covers, such as “contact_form_success” where generate_lead fits.
- Small differences in spelling, such as “Purchase” with a capital letter or “add-to-cart” with hyphens. Event names are case sensitive, so GA4 treats these as separate custom events.
- Sending the right event name with missing or badly formatted parameters, such as a value sent as text with a pound sign in it.
- Implementing every ecommerce event on a business that only takes enquiries, producing reports nobody uses.
- Assuming a recommended event becomes a key event by itself. You still choose which events represent business outcomes and mark them.
How to act on it
Write a short measurement plan before touching any tags. List the actions that matter to the business, match each to a recommended event where one exists, and create custom events only for what is left. Note the parameters each event needs and where the values will come from, usually the site’s data layer or your shop platform’s GA4 integration.
Implement through Google Tag Manager or the platform integration, test each event in DebugView, and only then mark the outcome events as key events. I build this mapping as part of the tracking setup in performance marketing, so GA4 and the ad platforms count the same actions in the same way.