A key event in GA4 is any event you have explicitly marked, under Admin > Events, as representing a real business outcome - a demo request, a trial signup, a purchase. Google renamed this from "conversion" to "key event" in the GA4 interface, and the overlap with the conversion terminology still used in Google Ads causes genuine confusion for B2B marketers auditing their own setup. This guide is for marketers without a dedicated analytics team who need to know exactly what changed, why it is not just cosmetic, and how to verify their property is configured correctly. ClimbPast connects to GA4 and can flag key event misconfigurations automatically, which is covered further down. If you are still setting up your property, /guides/getting-started-with-ga4 covers the basics first, and /request-access gets you a live audit of your own account.
Key event vs. conversion: what actually changed
For years, GA4 called any event you flagged as important a "conversion," borrowing the same term Google Ads and Universal Analytics used. Google renamed this to "key event" in the GA4 interface to separate GA4's own event-marking mechanism from the advertising-specific meaning of "conversion" used elsewhere in Google's products. Functionally, nothing about the mechanism changed: you still go to Admin > Events, toggle an event as a key event, and it appears in conversion-style reports and can be imported into Google Ads as a conversion action. The confusion comes from mixed terminology across the product suite. Google Ads still calls its own tracked outcomes "conversions." GA4's own API and BigQuery exports still reference "conversions" in some fields. A marketer auditing their setup today may see "key event" in the GA4 UI, "conversion" in Google Ads, and "conversion" again in an old GTM tag name, all describing the same underlying signal. Treat "key event" as GA4's current name for the events that matter to your business, and "conversion" as the broader Google Ads term for that same signal once it is imported downstream.
Why this distinction matters for B2B marketing teams
The terminology confusion is not just semantic. Teams that assume "key event" is a brand-new, separate concept sometimes think they need to rebuild tracking from scratch, when GA4 automatically carries forward any previously-marked conversion as a key event. Skipping the check means pipeline-critical events can quietly go unmarked after a property reset or a fresh GA4 setup, because key events are never enabled by default - they have to be flagged manually for every property. A B2B team that migrates to a new GA4 property, spins up a new subdomain, or rebuilds tracking after a site redesign can lose key event flags entirely while every other metric keeps reporting normally. That is a dangerous failure mode: sessions, pageviews, and engagement all look healthy while the metric leadership actually cares about - demo requests, signups, pipeline-qualifying form fills - quietly reports zero. Nobody notices until someone asks why last month's marketing-sourced pipeline number does not match what sales closed.
How to check and correctly mark key events in GA4
Start in GA4 Admin, under Events. Every event GA4 has collected in the last several days appears in this list with a toggle labeled "Mark as key event." Go through the list and confirm that every business-critical action - form submissions, demo requests, trial signups, pricing page CTAs - has the toggle enabled. If an event you expect to see is missing from the list entirely, the problem is upstream: the event is not firing or not reaching GA4, which is a tracking issue rather than a key-event configuration issue, and /guides/how-to-set-up-ga4-event-tracking walks through diagnosing that separately. For events that are firing but not marked, toggling key event status takes effect within a few hours and requires no code change. Avoid over-marking: flagging every event as a key event dilutes conversion reports and makes it harder to see which actions actually predict revenue. Limit key events to actions that represent a real, trackable business outcome - typically three to six per property for most B2B sites.
How ClimbPast keeps key events accurate without manual audits
Manually re-checking the Admin > Events list after every site change or property migration is easy to forget, and B2B teams without a dedicated analyst often only discover a missing key event when a monthly report shows an unexplained conversion drop. ClimbPast's GA4 integration audits key event configuration on an ongoing basis and flags when an expected event stops firing or loses its key event status, so the gap surfaces the same week instead of the same quarter. Through ClimbPast's MCP server, covered at /docs/mcp, you can also ask directly which events are currently marked as key events and when each one last fired, without opening GA4 Admin at all. Getting the terminology right is a five-minute fix. The return is a conversion report your team can actually trust when it is time to defend the marketing budget.