How recommended events work
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.
Why recommended events matter
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.
Common mistakes with recommended events
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.
