Are GA4 Key Events Retroactive?

The short answer

No. GA4 key events (the feature Google used to call conversions) are not retroactive. Google's own help centre puts it plainly: marking an event as a key event "affects reports from time of creation. It doesn't change historic data."

So if an event fired 50 times last month and you mark it as a key event today, your reports will show zero key events for last month, forever. Only occurrences after the moment you ticked the box are counted. The reverse is also true: unmark a key event and its past occurrences keep showing as key events.

This sounds obvious written down. In practice it produces a zero that looks exactly like a broken setup, and that is how it caught us.

How this caught us

Our GA4 property tracks a trial_download event when someone downloads the desktop app. In early September 2026, every GA4 report we pulled said the same thing: 202 sessions in the last 28 days and 0 key events on every row, every landing page, every channel.

That was precisely what the property would show if nobody had ever marked trial_download as a key event. It had already been flagged as a setup problem twice. We had drafted a third note saying, in effect, "this was marked as done, and it is demonstrably not done."

Then we checked the setting instead of the report. The key event had been created at 18:46 UTC on 8 September 2026. Our only two trial_download events that month had fired on 31 August and 3 September, both before the box was ticked, and none had fired since. Nothing could have counted. The setup was correct, the zero was correct, and the note we nearly sent would have been wrong.

How to check your own property

Reports cannot tell you whether a key event is configured. They can only tell you how many were counted. To see the configuration, read it directly.

1. In the interface: go to Admin, then Data display, then Key events. Every key event is listed there. If the event is missing, it is not marked.
2. Through the API: request GET https://analyticsadmin.googleapis.com/v1beta/properties/<property-id>/keyEvents. Each row returns eventName, countingMethod and createTime. The read-only Analytics scope is enough; you do not need edit access.
3. Compare the timestamps. Put the key event's createTime next to the dates your event actually fired (Reports, then Engagement, then Events, and filter to the event). If every occurrence is older than the createTime, a zero is the expected result.

What to do about the missing history

You cannot backfill key events in GA4. If you need the older numbers, the event itself is still there: report on the raw event count for the period before the key event existed, and label that part of the chart clearly. Do not add the two together as if they were the same metric.

The better habit is to mark key events the day you create the event, before any of the traffic you care about arrives. On a small site that matters more than it sounds: if your conversion volume is a handful a month, a week of missed counting can be most of your data.

The wider point

A reporting number and a configuration setting answer different questions. A zero in a report is evidence about what happened, not about how things are set up. We apply the same rule to crawling: Crawl Cove shows the evidence behind every issue it reports, because you should be able to check a number before acting on it. For another example of a report that looks complete and is not, see anonymised queries in Search Console.