/ seo-glossary / What is a Key Event in GA4? SEO Guide
seo-glossary 6 min read

What is a Key Event in GA4? SEO Guide

Learn what key events are in Google Analytics 4, why Google renamed conversions to key events in 2024, and how to choose which actions deserve the flag.

What is a Key Event in GA4? SEO Guide

A key event is Google Analytics 4's name for an event you've flagged as important, a purchase, a signup, a submitted contact form, a booked demo. Everything in GA4 is an event, page views, clicks, scrolls, all of it. Marking one as a key event tells GA4 this is an outcome worth counting, reporting on separately, and building funnels toward.

If the term feels new, it is, sort of. These were called "conversions" in GA4 until March 2024, when Google renamed them to key events. Same feature, same toggle, new word, and an actual reason behind the rename rather than pure rebranding weather.

Why Google Renamed Conversions to Key Events

The word "conversion" meant different things in Google Analytics and Google Ads, and the mismatch produced years of confused reconciliation meetings. Analytics counted its conversions per its own rules, Ads counted conversions per its rules, attribution and counting differed, and the two numbers never matched for anyone who looked closely.

The 2024 rename split the vocabulary on purpose. In the post-rename world, "key event" is the analytics-side term, an important action measured in GA4. "Conversion" now refers to the Ads-side concept, key events that get shared to Google Ads for bidding and performance measurement. An action can be both, a purchase key event that also feeds Ads as a conversion, but the words finally point at distinct things.

Not going to pretend the transition was smooth, dashboards, docs, and muscle memory all said "conversions" for years, and half the industry's written material still does. But the underlying distinction is genuinely useful once it clicks, measurement vocabulary and bidding vocabulary were always different things wearing one word.

How Key Events Work Mechanically

The flow has two halves, an event must exist before it can be key:

  1. The event fires. Either automatically (GA4's enhanced measurement covers page views, scrolls, outbound clicks, file downloads, video engagement out of the box), or as a custom event you send, generate_lead, sign_up, purchase, with whatever parameters you attach.

  • You flag it. In Admin, under Events (or Key events), toggle "Mark as key event" on the event name. From that moment, occurrences count as key events in reports. Historical data doesn't retroactively convert, the flag applies going forward.

  • Counting has one setting worth knowing, per event or per session. "Once per event" counts every occurrence, right for purchases. "Once per session" counts at most one per session, more honest for things like lead forms where a double-submit isn't two leads.

    That's the machinery. The judgment call is which events deserve the flag, and this is where most setups go sideways.

    Choosing Key Events That Mean Something

    The flag should mark outcomes, moments where real value changed hands, not engagement along the way. A workable test, would you email someone about this number weekly? Purchases, qualified leads, signups, booked calls pass. Scroll depth does not.

    A sane starter set for a content site with something to sell looks like, one key event for the primary action (purchase or signup), one for the lead-capture action (newsletter, contact form), possibly one micro-outcome that genuinely predicts the rest (starting checkout, beginning a trial). Three-ish. Sites running double-digit key events have usually flagged engagement noise, every video play and scroll milestone, and the reports degrade into everything-is-key-nothing-is.

    For SEO work specifically, key events are what turn ranking reports into revenue arguments. Organic sessions are a vanity number until they're organic sessions that produced key events, and the conversion funnel from landing page to key event is the report that justifies content budgets. This site's own reporting leans on exactly that chain, entry page to email capture, nothing fancier.

    Common Mistakes to Avoid

    • Flagging engagement as outcomes. Scrolls, video plays, and time-on-page milestones describe attention, not value. Key events full of them inflate the counts and bury the numbers that matter.

    • Expecting GA4 and Ads to match anyway. Even post-rename, key events measured in GA4 and conversions imported to Ads count differently, attribution models and timing differ by design. Reconcile directions, don't expect equality.

    • Forgetting the flag is forward-only. Mark an event as key today and last month's occurrences stay unflagged. Set up key events at property creation, not at the first reporting deadline.

    • Building funnels to unflagged events. Funnel and advertising features key off the flag. A perfect sign_up event nobody marked is invisible to half the reporting surface.

    • Still writing "conversions" in GA4 documentation. Minor, but new team members now learn the new vocabulary, and mixed usage in internal docs recreates the exact confusion the rename existed to kill.

    In Practice

    The honest setup ritual for a new property takes an hour. List the two to four actions that constitute the site succeeding, instrument them as custom events with clean names, flag them as key events the same day, choose per-session counting for forms, and leave the enhanced-measurement noise unflagged. Then stop touching it. Analytics configurations rot through accumulation, someone flags one more event each quarter, and two years later nobody can say what "key events" measures anymore. A short list defended beats a long list explained, and I'd take three defensible key events over eleven negotiable ones any week.

    Key Takeaways

    • Key events are GA4's flagged important events, renamed from "conversions" in March 2024 to unglue analytics vocabulary from Ads vocabulary.
    • "Conversion" now means the Ads-side concept; a key event can feed Ads as a conversion, but the terms are distinct.
    • Any event can be flagged in Admin; the flag applies forward only, and per-session counting suits lead forms.
    • Flag outcomes, not engagement, a defensible handful beats a bloated list, and funnels only see what's flagged.

    Sources