GA4 renamed Conversions to Key Events — what breaks and what doesn't

Google renamed GA4 "Conversions" to "Key events," and through 2026 the API caught up to the UI: the Admin API resource moved from conversionEvents to keyEvents, and the Data API now exposes the count as the keyEvents metric. If you have scripts, dashboards, or BI tools reading GA4, some of them are about to quietly return nothing.

What renamed, and what didn't

• UI: "Conversions" is now "Key events" (a separate, Google Ads-aligned "Conversions" concept now exists).
• Admin API: the conversionEvents resource is deprecated in favor of keyEvents.
• Data API: prefer the keyEvents metric; the legacy conversions metric still resolves on many properties for now.

What breaks

Anything that hardcodes the old names. A Looker Studio field, a scheduled export, a homegrown script hitting the Admin API for conversionEvents — these return empty or 404 as properties migrate. And because the values default to zero rather than throwing, a dashboard can look "fine" while reporting no conversions at all.

⚠️ Warning: Zero is the most dangerous value in analytics. A metric that reads 0 looks like a bad week; a metric that errors gets fixed. This rename produces the former.

How to make your integrations survive it

1. In API calls, prefer keyEvents and fall back to the legacy conversions / conversionEvents only if the property has not migrated yet (the new resource 404s).
2. Audit your Looker Studio and BI fields for hardcoded "Conversions" metrics and repoint them.
3. Add a sanity alert: if the key-events count drops to exactly 0 for a day, page someone. A zero is a signal, not a silence.

TagEasy's GA4 integration already prefers the keyEvents resource and metric, falling back to the legacy names only when a property has not migrated — so reporting survives both sides of the rename with no code change on your end.

The bigger lesson

Platform renames are a recurring tax on anyone who tracks conversions. The defense is the same every time: prefer the new name, fall back to the old, and alert on suspicious zeros. Build that muscle once and the next rename is a non-event.