Analytics and Tracking

Recommended Event

Also called Recommended events

A Google-defined event name with expected parameters, which you send yourself but should not rename.

Quick facts: Recommended Event

Category
Analytics and Tracking
Also called
Recommended events
Level
Intermediate
Affects
Ecommerce reports, audiences, ads imports, revenue reporting
Where to see it
GA4 (Events, DebugView), Google Tag Manager
In this article4
  1. How recommended events work
  2. Why recommended events matter
  3. Common mistakes with recommended events
  4. How to act on it

GA4 sorts events into three groups. Some it collects on its own. Some you can switch on per data stream. Everything else you send yourself — and within that last group, Google publishes a list of names it already understands, each with the parameters it expects to travel alongside. Names such as purchase, generate_lead, sign_up, add_to_cart and view_item belong to that published list.

They are not collected for you. You still have to fire them, usually through Tag Manager, exactly as they are spelled and with the expected parameters attached. A purchase event, for example, is only complete when it carries a value, a currency and the items involved. Send the name without those and it will still be recorded, but the reports built to use it will stay empty.

Because parts of GA4 are wired to these names specifically. Ecommerce reporting, the shopping and purchase journey views, and several ready-made audiences all look for the published names and their parameters. A custom name describing exactly the same action will not activate any of it, and no setting can be flipped later to make it do so.

The same holds outside GA4. Importing a key event into Google Ads, or sharing an audience with it, is far cleaner when the event and its value are already in the shape the advertising side expects. Choosing the published name at the start costs nothing; discovering the mismatch after months of data means retagging and a broken trend line.

Near-miss naming is the classic: purchase_complete, lead_generated, addtocart. To a person these read as the same thing. To GA4 they are custom events with no special behaviour at all, and the built-in reports stay blank while the tagging looks finished. The rule is simple — if a published name exists for the action, use it exactly.

The other is sending the name without its supporting parameters. A purchase with no value cannot report revenue. A value with no currency cannot be converted or compared. And on the lead-generation side, a generate_lead event fired on every form on the site, including a newsletter box, hands automated bidding a target that is much easier to reach than a real enquiry — worth thinking about before you connect it to conversion tracking in Google Ads.

How to act on it

Before tagging, check whether the action already has a published name. If it does, take the name and the full parameter list together rather than the name alone. If it does not, invent a custom name in the same lower case, underscore style so the property reads consistently.

Then confirm in DebugView that the parameters arrive, not just the name. On a shop this matters most, because ecommerce tracking depends almost entirely on the published events being sent correctly the first time.

Do and do not

Do

  • Check for a published name before inventing your own
  • Send the expected parameters, not just the name
  • Confirm value and currency arrive on purchase events

Do not

  • Use a near-miss spelling of a published name
  • Fire generate_lead on every form including newsletters
  • Expect ecommerce reports to fill from a custom name

Questions people ask about this

Are recommended events collected automatically?

No. Google publishes the names and the parameters it expects, but you have to send them yourself, normally through Tag Manager or by a developer adding the call to the site. Only two groups are collected without you: the basic automatic events, and the optional enhanced measurement group toggled inside each data stream.

What happens if I invent my own name instead?

The event is still recorded and you can still report and build audiences on it. What you lose is everything wired to the published names: the ecommerce reports, the purchase journey views, and the smoother handover to advertising platforms. Since using the published name costs nothing extra, the only good reason to invent one is that no published name fits the action.

Which recommended events should a lead generation site use?

Usually generate_lead for a genuine enquiry, and sign_up where an account or registration exists. Keep generate_lead for actions that represent real commercial intent — a quote request, a contact form, a booking — and use a different name for lighter actions such as a newsletter subscription, so bidding and reporting are not trained on the easiest thing to click.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.