Know which number to trust before you touch the budget.
GA4 calls it a key event and Google Ads calls it a conversion, and both are a tag's count of the same action. Your lead sheet is the record, and this page shows you when to read each one.
What is a key event in GA4?
A key event is an event you marked in GA4 as worth counting on its own. GA4 records an event for almost everything a visitor does on your site: page views, scrolls, clicks, form submissions. Most of that is activity. Flag one of those events, say form_submit or generate_lead, as a key event and GA4 counts it separately, reports it on its own, and lets Google Ads import it as a conversion.
Two things follow. A key event is an event first, so it exists only if a tag on your page fired it. It is a count, so a form submitted twice is two key events and a form whose tag never fired is none. That makes it measurement, not a record. The rest of this page is about that difference.
Why does GA4 say key events while Google Ads says conversions?
Google renamed them. In 2024 the word conversion in the GA4 reporting interface became key event, and conversion was reserved for the events Google Ads also uses. The intent was one meaning across both products: a conversion is an action Google Ads attributes to an ad and bids toward. A key event becomes an Ads conversion when you import it into the Ads account. From then on Ads counts it under its own attribution rules, so the two totals are expected to differ.
The rename stopped at the interface. The Google Ads API still reports the metric as conversions, and the GA4 Data API still answers to the older metric name conversions. The Command Center reads both through those APIs, so the same count can arrive under two labels depending on which door it came through. The view tells you which door: the analytics view reads GA4, the ads view reads Google Ads, and each says so in its caption.
Is a key event the same as a lead?
No. A key event is a tag's claim that something happened. A lead is a form your website received. On a site we build, the form handler emails your team and appends the submission to your lead sheet on the server in the same request, before the browser reaches the thank-you page. That row exists whether or not any tag on the page loaded. GA4 learns about the same submission only if the browser ran the tag and the tag fired the event, and either step can stop working after a site change without anyone noticing.
So the two counts are related, not equal. When the sheet has rows the tag never counted, the tag is wrong. A phone call is not a key event unless a tap on the number fires one, and the Command Center counts a phone lead only when your CRM records it, because there is no call-tracking system. Use a key event to ask what your traffic did. Use the sheet to decide whether a campaign produced customers. Lead source tracking covers where the record of a lead comes from.
How do I find out when the tag stops counting?
A watch reads all three every morning. On an instance whose forms feed the lead sheet, it runs at 7:20 Eastern and reads the sheet, the form_submit and generate_lead events GA4 recorded, and the conversions Google Ads recorded against the web lead action, plus the live pages and Search Console for two of its checks. Five checks run. Loader confirms the Google tag still loads and the conversion label is still on the page. Blind fires when leads landed in the sheet and GA4 recorded zero form events. Ads blind fires when leads arrived from a paid click and Ads recorded zero conversions. Stalled fires when a campaign that was reliably spending went to zero. Silent fires when organic search traffic continues and no leads arrive at all.
One account is the reason it exists, anonymised. A tag change silently stopped every conversion for six weeks. Twenty-one real leads landed in the sheet while Google Ads reported zero. The owner read the report, paused the campaign that carried every counted lead, and cut its budget by ninety percent. The lead count was right the whole time. The measurement was dead. The daily comparison makes that failure loud within days instead of six weeks later, and the loader check catches a missing tag on the first morning. The leads ledger shows the sheet.
Which number do I read on the dashboard?
Read all three, each labelled by its source. The analytics view shows GA4 key events by name for the range you pick, thirty days by default. The tile reads Conversions, the older GA4 name the Data API still returns, and on a lead-generation dashboard it reads lead actions, with plain names instead of snake_case. The ads view shows conversions as Google Ads counted them, by campaign, with cost per conversion. The leads view shows the sheet, newest first, with the source the visitor arrived from where the form records it. Nothing on the screen writes to GA4 or to Ads. The write paths from the dashboard are a question to the team where that view is offered, a lead outcome, a website change request, and a content or targeting request.
The freshness differs, and the page says so. The sheet is live, written the moment a form is submitted. GA4 and Google Ads are hours behind intraday, on Google's publishing schedule, and the header stamp says how old the numbers are. Read the sheet first. Then use key events and Ads conversions to ask where the leads came from. The GA4 connection lists exactly what is read from your property and how the access is granted.
Every label, and what it counts.
| Term | Where it is used | What it counts |
|---|---|---|
| Key event | GA4 reporting interface | An event you marked as important, counted when the site tag fires it. Hours behind intraday. |
| Conversion, GA4 Data API | The API the Command Center reads GA4 through | The same key event count under the older metric name. |
| Conversion, Google Ads | Google Ads interface and API | An action Ads attributes to an ad click, by conversion action, under Ads' own rules. Hours behind. |
| Lead | Your lead sheet, on the Leads view | A form your site received, written server-side at submission. Live. |
| Phone lead | Your CRM | Counted only if the CRM records it. No call tracking. |
A key event can read zero on a day your site produced leads, so the Command Center shows both counts and, on an instance whose forms feed the sheet, compares them every morning at 7:20 Eastern.
Questions, answered.
Are GA4 key events the same as conversions?
In GA4, yes: key events are what conversions used to be called. Google renamed them in 2024 and kept the word conversion for Google Ads, where it means an action Ads attributes to an ad click.
Why do my GA4 key events and Google Ads conversions not match?
Because they count differently on purpose. Google Ads counts a conversion only when it can attribute the action to an ad click. GA4 counts the key event every time it fires, from any source. Expect them to differ. One reading zero while the other does not is the case the daily watch raises.
Is a key event a lead?
No. A key event is what a tag counted. A lead is a form your site received, written to a lead sheet server-side at submission. The Leads view reads the sheet, and on an instance whose forms feed the sheet, the daily watch compares it with GA4 and Ads.
What happens if the tag stops firing?
The sheet keeps counting, because the form handler writes it on the server. The morning watch sees leads in the sheet and zero GA4 form events, and raises the site tag as dead.
Does the Command Center change my key events or conversion settings?
No. It reads GA4 and Google Ads through manager access you grant and never writes to either. You configure key events in your own GA4 admin.
Do phone calls count as key events?
Only if a tap on the phone number fires one, and that counts a tap, not a call. The Command Center counts a phone lead only when your CRM records it. There is no call-tracking system.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.