How a key event works
In GA4 everything a visitor does arrives as an event. A key event is one of those events with a switch flipped: you have told the property that this particular action represents business value. Collection does not change — the same data was already being recorded — but the event now appears in key event reporting and becomes available wherever conversions are needed.
The name is new; the idea is not. GA4 previously called these conversions, and the rename separates what analytics measures from what an advertising platform counts and pays for. Google Ads still calls its own imported version a conversion, so the two words describe the same underlying action at different points in the chain.
You mark one in the property’s events list, or create the event first if it does not exist yet. Marking applies from that moment forward and does not reclassify what came before.
Why key events matter
They are how a business separates the handful of actions that matter from everything else the site records. Reporting collapses to a short list anyone can read, and comparisons between channels start to mean something, because every channel is being judged against the same defined outcome.
They also feed bidding. Import a key event into Google Ads and its automated strategies will optimise towards it, spending more wherever that action happens. That is useful when the marked action really is valuable and damaging when it is not, which is why the choice deserves more thought than a tick box invites.
Common mistakes with key events
Marking too many is the most common. When page views, scrolls, video plays and newsletter sign-ups are all key events, the report says nearly everything is a conversion and nothing stands out. It also leaves any bidding strategy fed from that list with no clear target.
Marking the wrong thing is worse. A thank-you page view is a proxy that fires whenever the page loads, including on a refresh or from a bookmark, while the form’s own confirmation is the real signal. Counting a tap on a phone number as a completed call, or a WhatsApp tap as an enquiry, overstates results in a way nobody notices until the sales figures disagree. And marking an event without testing the underlying event first inherits every fault in the tracking beneath it.
How to act on it
Choose a small set — the actions you would genuinely report to the business — and split them into primary outcomes and supporting steps. Mark the primary ones, and leave the supporting ones as ordinary events you can still analyse without dressing them up as results.
Test each one end to end before marking it: in DebugView first, then with a real submission you can find afterwards in the inbox or the CRM. Where a monetary value exists, send it with the event so revenue reporting works rather than just counting. Review the list whenever the site or the offer changes, and check that smaller supporting actions have not quietly been promoted. Anyone rebuilding measurement will normally redo this list as part of a GA4 setup.
