Google Analytics conversion tracking means marking the events that matter in a GA4 property as key events and, when you advertise on Google, turning some of them into conversions that Google Ads can bid on. The two words used to mean the same thing. They don’t anymore. A key event is a GA4 flag for analysis. A GA4 conversion is built from a key event for ad measurement, and it needs a linked Google Ads account.
GA4 counts a key event when the marked event arrives. It doesn’t check that the action behind it was real, unique or paid. This guide sets up a lead and a purchase, explains how key events, GA4 conversions and Google Ads conversions relate, and ends with what GA4 can’t verify for you.
A key event is an event you flagged
GA4 is event-based. A page view, a click, a form submission and a purchase are all events, collected by the base tag and enhanced measurement, by your own code or Google Tag Manager, or by the Measurement Protocol from a server. Any event that reaches GA4 can be marked as a key event.
Some events start marked. purchase is on by default, and depending on the property’s history, others may be too. Check the current state in Admin before changing anything.
Set up a lead and a purchase
Send the event from the result, not from the click. For a purchase, fire purchase on the confirmed order with value, currency and a unique transaction_id:
gtag('event', 'purchase', {
transaction_id: 'order_1234',
value: 49.00,
currency: 'USD',
items: [{ item_id: 'container_pack', item_name: 'Container Pack', price: 49.00, quantity: 1 }]
});
value and currency give the key event revenue. A unique transaction_id lets GA4 deduplicate purchases on web streams; Google’s transaction ID help says this doesn’t apply to app streams.
For a lead, push the event from the form’s success callback, so it only fires when your backend accepted the submission. A thank-you page trigger is easier, but it fires again on every reload. In the push below, 5.00 is an illustrative lead value; use your own estimate of what a lead is worth.
dataLayer.push({ event: 'generate_lead', value: 5.00, currency: 'USD' });
Then finish the GTM side, because a trigger alone sends no value:
- Create two Data Layer Variables, one reading
valueand one readingcurrency. - Create a Custom Event trigger on
generate_lead. - Add a Google Analytics: GA4 Event tag with the event name
generate_lead, and map the event parametersvalueandcurrencyto the two variables. - Open Preview, submit the form once, and check that the tag fired once with both parameters filled. Then reload the confirmation and submit a second time, and confirm you get one event per real submission.
- Check the event and its parameters in DebugView, then publish the container.
Mark the event and choose how it counts
In Admin, under Data display, open Events. On the Recent events tab, select the star next to the event to mark it as a key event. If the event should only count under a condition, create a custom event with that condition first and mark the custom event. Google’s key events help (checked 2026-10-17) says Realtime shows a key event a few minutes after it fires and standard reports can take up to 24 hours.
Each key event counts Once per event or Once per session. Purchases usually count once per event. A lead that people can repeat sometimes counts once per session. Key events migrated from old Universal Analytics goals may still use once per session, so check.
Key events, GA4 conversions and Google Ads conversions
Three objects share one word, and most “my numbers don’t match” questions come from comparing two different ones.
Key events live in GA4’s standard reports and cover all traffic. GA4 conversions are created from a key event under Advertising > Conversion management, and Google’s conversions help (checked 2026-10-17) says “A linked Google Ads account is required” to create one. They’re reported in Advertising > Conversion performance and, per the same page, “don’t appear in standard Google Analytics reports in the Reports or Explore sections”. Google Ads conversions are what the Ads account counts for bidding, tied to an eligible ad interaction.
| GA4 key events | GA4 conversions | Google Ads conversions | |
|---|---|---|---|
| Where you create it | Admin > Data display > Events | Advertising > Conversion management | Google Ads, or imported from GA4 |
| Where you read it | Reports and Explore | Advertising > Conversion performance | Google Ads columns |
| Includes non-ad traffic | Yes | Depends on the channels you share it with | Not by default; Ads reporting uses Google paid attribution unless you switch it to Paid and organic |
| Attribution | Reporting attribution model in Admin > Attribution settings | Its own settings in Conversion management | The Ads action’s model and window |
Counting has two owners as well. Key-event counting is the Once per event or Once per session choice in Admin. For a conversion shared with “Paid and organic channels”, Google’s shared conversions help (checked 2026-10-17) says the conversion window and counting method are managed in Analytics, under Advertising > Conversion management. For “Google paid channels” the settings match by default, and some, like the window and counting method, “might not be editable in Google Ads”.
So before you call a gap expected, compare like with like: GA4 Conversion performance against Google Ads for the same action and period. Differences that remain usually come from attribution and eligible interactions. Google Ads can count view-through conversions, and GA4 key events include organic and direct visits that never touched an ad.
Bringing key events into Google Ads
Turn on auto-tagging so the click identifier reaches your site, and make sure it survives any redirect between the landing page and the conversion page. Then link GA4 to Google Ads and either import the key event or create the conversion from GA4’s Conversion management.
An import doesn’t make Google Ads bid on the action by itself. An imported action can land as secondary, for example to avoid double counting with goals that already use the same property. Google’s primary and secondary actions page (checked 2026-10-17) says secondary actions are “for observation only” and stay in the All conversions column. The exception: “if the secondary action is part of a custom goal, in which case it’s used for bidding.” After you import, check Action optimization, promote the action to primary in a standard goal or add it to the custom goal the campaign uses, and check that no other action counts the same sale.
When a new server-side Ads conversion stays empty, the Google Ads server-side troubleshooting checklist checks its action type, account authorization and reporting status separately.
Some events never arrive
Browser loss isn’t random. Blockers filter requests to known measurement domains, Safari limits how long script-set cookies last, and hosted checkouts on another domain hide the purchase page from your tag. Consent adds its own layer, which the Consent Mode v2 guide covers. Sending events from your server through the Measurement Protocol can help when consent was given, but it doesn’t override a declined choice, and session attribution still depends on the browser’s client and session IDs reaching GA4 in time. The server-side tracking guide covers that trade-off.
What GA4 can’t verify
GA4 counts the event it receives, not the outcome behind it. A duplicate, a test, automated traffic or a purchase tag that fired before a payment failed can all become key events. A unique transaction ID collapses repeated purchases on web streams. It doesn’t confirm the charge succeeded. Shopify adds its own trap when the Google & YouTube app and a custom GTM route both send ecommerce events; the Shopify sGTM duplicate-events guide covers that audit.
The fix is to compare GA4 with the system that knows the outcome, every day. On a Brazilian client’s Pix deposit funnel in September 2026, the bank side stayed normal while GA4 purchase coverage went from 97% to 67%, 26% and 18% over three days. A site change had started hashing the email that a server-side lookup used as its key, so the server purchase stopped finding its stored client_id, and GA4 discards a Measurement Protocol hit without one. Nothing errored. A daily GA4-to-bank ratio check is what caught it. The tracking monitoring guide covers that kind of check.
For a purchase or a qualified lead that has to be exact, send the key event from the system that records the outcome: a payment webhook on a successful charge, or the CRM stage your sales team uses. The Stripe conversion tracking guide walks through a purchase built on the payment webhook.
For automated visits that distort the funnel denominator, the bot traffic measurement guide explains how to calculate a suspected share from your own logs before filtering.