Definition
Google Analytics describes everything it records as events: page views, scrolls, clicks, form submissions, purchases. Most of them describe behaviour along the way. A key event is one the property owner has flagged as an outcome, an action the business would count as success if it happened. Flagging it gives the event a counting method and an optional value, adds it to the key events report, makes it available as a column in acquisition reports and a filter in attribution reports, and lets a linked Google Ads account import it.
The name is recent. The same mark used to be called a conversion. Google renamed it because the GA4 count and the Google Ads count of the same outcome are produced by different systems and were never going to agree, yet the shared label kept inviting people to reconcile them. Inside GA4 the word conversion now refers only to key events that have been shared with Google Ads.
In practice
The discipline is restraint. A property can hold only a small number of key events, and every one diluted with a micro-action weakens the figure the business reads as success. Good candidates are outcomes with commercial meaning: completed orders, submitted enquiries, booked appointments, started trials, qualified sign-ups. Poor candidates are steps that merely suggest interest, such as a page view, a scroll or a click on a menu, which belong in ordinary event reports.
The GA4 setup checklist places marking key events after the events themselves are firing correctly, and the key events and conversions guide covers choosing, marking and valuing them in full. Events are usually sent through GTMTag management system., so the event name in the container and the name marked in GA4 have to match exactly; a renamed tag silently stops the key event counting.
Key events versus Google Ads conversions
When a key event is imported into Google Ads it becomes a conversion action there, and from that point it is counted under Ads' rules: Ads' AttributionAssigning conversion credit to touchpoints. model, Ads' conversion windows, the click date rather than the event date, and only the outcomes Ads can connect to its own ad interactions. The GA4 and Google Ads integration guide explains linking and import, and why many accounts keep a native Ads tag as the primary action. The practical consequence is simple: the key event total in GA4 and the conversion total in Ads describe the same outcome through two lenses and should be explained, not forced to match.
Counting rules and reporting
Each key event is counted once per event or once per session. A purchase is normally counted every time it happens; a lead form is often counted once per session so that a double submission or a refresh does not inflate the total. Marking, unmarking and changing the counting method apply from the change onwards, which is why the guide to common GA4 mistakes lists a newly marked event as a frequent cause of a sudden jump or gap in the trend. Key event rates appear in reports as a session rate and a user rate, and both are forms of CVRShare of visits or clicks that convert. with different denominators. Which touchpoint receives credit for a key event is decided by the property's model and windows, described in the GA4 attribution settings guide.
A florist replaces a vanity key event
Hawkbit Florists marks views of its delivery-information page as a key event alongside orders. Its key event rate climbs from 2.1% to 18% of its 19,500 monthly sessions, and the team reports a breakthrough. Looking closer, 3,100 of the 3,510 key events are page views; completed orders are flat at 410. The florist unmarks the page view, keeps orders, and adds quote requests for wedding and corporate flowers, which run at about 50 a month. The new key event rate settles at 2.4% and moves with the order book. Because the change applies only from the day it is made, the team notes the date in its reporting so the drop is not mistaken for a sales slump.
Related terms
GA4Google's event-based analytics platform. is the platform in which key events live. GTMTag management system. is the usual route by which the underlying events reach it. CVRShare of visits or clicks that convert. is the rate a key event produces when divided by sessions or users, and AttributionAssigning conversion credit to touchpoints. decides which channel or campaign each key event is credited to. An analytics implementation audit treats the key event set as a gate: if the marked events do not match the business's real outcomes, every report built on them inherits the error.
Common confusions
- A key event is not a different kind of event. It is an existing event with a flag on it; nothing about collection changes.
- Key events are not Google Ads conversions. Imported ones become conversions in Ads, counted under Ads' own attribution, windows and dates.
- More key events are not better. Each micro-action marked as success makes the success figure less meaningful.
- Marking is not retroactive. History is not recalculated, so a new key event shows a gap before its marking date.
- The name must match exactly. A case or spelling difference between the sent event and the marked event leaves the key event at zero.
