What Changed With Key Events vs Conversions in GA4

What is the difference between key events vs conversions in GA4?

Google uses key events vs conversions in GA4 as names for two different objects in two different products: a key event is an event you mark as important inside Google Analytics, and a conversion is the Google Ads object you build from that key event. Google's help article on the change writes the relationship as a chain, "Event → Key Event → Conversion", and states the reason for it: "To create a simpler and more intuitive experience in the way conversions are measured and reported across Google Ads and Analytics, we're unifying how conversions are defined" (Analytics Help, Conversions vs. key events in Google Analytics).

The rename is not cosmetic. One word used to cover both the thing you configured in Analytics and the thing Google Ads bid on. Now Analytics owns "key event", Ads owns "conversion", and the same help page adds a hard dependency: "A linked Google Ads account is required to create a new Google Analytics conversion from a key event." Without that link, your property has key events and no conversions at all.

The rename chain

Event

Key Event

Conversion

What is a key event in Google Analytics?

Google defines it in one line: "A key event is an event that measures an action that's particularly important to the success of your business" (Analytics Help, About key events). The mechanism is a flag, not a new collection path. Any event the property already collects becomes a key event when you mark it as one in Analytics, so the signup, purchase or form submit you were already sending needs no new tag (Analytics Help, Create or modify key events).

Key events surface in the reports you read every day. Google names two of them directly: "the Landing pages and User acquisition reports, include a Key events column." If your event tracking already fires clean names, marking key events is an admin job, and it is the same decision you make when you set up goal and event tracking in any analytics tool.

What does "conversion" mean in GA4 now?

Google Ads owns the word. Its help center defines a conversion as "An action used to measure the performance of your ad campaigns and optimize your bidding strategy" and separates it from a key event on exactly one axis: conversions "are eligible for bidding and reporting in Google Ads" (Google Ads Help, Key event, Conversion & Purchase definition). The Analytics side repeats the same scope: "A 'conversion' now refers to an important action that you want to use to measure the performance of your ad campaigns and optimize your bidding strategy."

A conversion is a bidding input first and a report row second. If nobody at your company buys ads, every number you care about lives under the key events label.

Did Google publish a date for the rename?

Google's own help article does not carry one. It announces the change in the present tense, "From now on, events that measure actions that are important to the success of your business are now called 'key events'", and gives no month or year for when the column headers flipped (Analytics Help, Conversions vs. key events in Google Analytics). Third-party posts circulate dates that Google's documentation does not state. If you need the date for a compliance note or a client report, take it from your own property's report history, not from a blog post.

Which reports show key events, and which show conversions?

Standard Analytics reports show key events, and Google Ads conversions appear in Analytics only inside the Advertising section. Google is explicit about both halves: "Google Ads conversions created from Analytics key events appear as conversions in the Advertising section in Google Analytics", and "Google Ads conversions don't appear in standard Google Analytics reports."

Question	Key event	Conversion
Where you create it	Google Analytics, by marking an existing event	Google Ads, from a key event, with a linked Ads account
Google's definition	"an event that measures an action that's particularly important to the success of your business"	"an important action that you want to use to measure the performance of your ad campaigns and optimize your bidding strategy"
Shows in standard Analytics reports	Yes, as a Key events column	No
Shows in the Analytics Advertising section	Yes, in attribution and pathing reports	Yes, as conversions
Eligible for Google Ads bidding	No, until a conversion is created from it	Yes
Historical data when created	Uses the event's existing history	Google Ads conversions shared with Analytics "don't have historical data associated with them"

Read the table as a routing rule. A founder asking how many signups landed last week wants the key events column; a media buyer asking the same question wants the Ads conversion count.

What happens when GA4 and Google Ads are linked?

Linking does not turn key events into conversions on its own; you import them. Google's instruction is direct: "To import a Google Analytics event into Google Ads as a conversion, it must first be marked as a 'key event' in your Google Analytics property" (Google Ads Help, Create conversions from Google Analytics events in Google Ads). You can start the import from either interface, and Google warns about lag on both the data and the labels: "it can take up to 24 hours before conversion data is available in Google Ads after importing a Google Analytics key event", and a renamed key event takes up to 24 hours to show its new name in Ads.

A key event marked this morning with zero conversions in Ads this afternoon is not a broken link; it is that window.

How do you measure a key event rate?

Google exposes a Session key event rate metric alongside the Key events metric in explorations (Analytics Help, About key events). The arithmetic is a share of sessions:

Session key event rate = sessions with at least one key event / total sessions

If Analytics records 4,000 sessions and 260 of them contain at least one key event, the session key event rate is 260 / 4,000, or 6.5 percent. Check the counting method before you compare that figure week over week: "You can choose how many times Google Analytics counts a key event if someone triggers it more than once in a session", with "Once per event (Recommended)" counting every trigger and "Once per session (Legacy)" counting one (Analytics Help, Change the counting method of key events). The same split starts most conversion rate formula arguments between two teams on one dashboard.

Why do the two numbers still disagree?

Different definitions produce different totals, and modeling widens the gap. Google states that "Google uses modeling to estimate online key events that can't be observed directly", including cases where a user has not consented to advertising cookies or where the ad click and the key event happen on different devices (Analytics Help, About modeled key events). Your consent mode setup feeds that estimate.

Before you file the gap as a bug, rule out GA4 data thresholding withholding rows, missing website traffic in GA4, and sessions landing in direct / none after a stripped referrer. Flowsery records every session and groups matching ones into a single ranked issue, so a broken checkout step arrives as a replay you can watch instead of a number that shrank.

Is this the Universal Analytics migration again?

No. The key event rename changes vocabulary and ownership between two products that already existed. The move from sessions and goals to an event-based schema is a separate story, covered in Universal Analytics vs GA4 differences and the steps to convert UA goals to GA4. If you migrated goals into GA4 conversions and then watched the label flip to key events, the underlying events did not move.

Frequently Asked Questions

Are key events and conversions the same number?

No. A key event counts in Google Analytics as soon as you mark the event; a conversion counts in Google Ads only after you create it from that key event, under Ads attribution. Google keeps them apart on purpose: conversions "don't appear in standard Google Analytics reports."

Do I need a Google Ads account to use key events?

No. Marking key events works in any Google Analytics property. You need the Ads link only to create conversions, since Google states that "A linked Google Ads account is required to create a new Google Analytics conversion from a key event."

Where did the old Conversions column in GA4 reports go?

It carries the key events label now. Google's help center lists the Key events column in the Landing pages and User acquisition reports, and the Advertising section keeps the word conversions for Google Ads conversions created from your key events.

Does creating a conversion from a key event backfill history?

Not for the Ads side. Google states that "Google Ads conversions that are shared with Google Analytics, however, don't have historical data associated with them." The key event itself keeps the history of the underlying event.

How long does an imported key event take to show up in Google Ads?

Up to 24 hours, per Google: "it can take up to 24 hours before conversion data is available in Google Ads after importing a Google Analytics key event." Renaming a key event or its property also takes up to 24 hours to appear in Ads.

Why is my key event count higher than it was last quarter?

Check the counting method before you check the tag. "Once per event (Recommended)" counts a key event every time it fires in a session, while "Once per session (Legacy)" counts it once, so switching methods changes the total without any change in user behavior.

What is a session key event rate in GA4?

Session key event rate is the share of sessions that contain at least one key event, calculated as sessions with a key event divided by total sessions. Google's example works out to 260 of 4,000 sessions, a rate of 6.5 percent. The metric sits next to the raw Key events count in explorations.

What causes GA4 to model a key event instead of counting it directly?

Google models key events it cannot observe directly, most often when a user has not consented to advertising cookies or when the ad click and the key event happen on different devices. Your consent mode setup feeds directly into that estimate. The modeled number sits alongside the observed count, one reason the two totals rarely match.

Can a key event trigger Google Ads bidding on its own?

A key event alone carries no bidding eligibility until you create a conversion from it in Google Ads, per the comparison table's bidding row. The key event still shows in the Key events column of standard Analytics reports while it waits. Bidding eligibility on the account depends on the conversion, not the key event.

Is the key events rename part of the Universal Analytics migration?

The key events rename only changes vocabulary and ownership between Google Analytics and Google Ads, two products that already existed. The Universal Analytics migration moved GA away from sessions and goals into an event-based schema, a separate and earlier change. If you converted UA goals into GA4 conversions before the rename, the underlying events never moved, only the label did.