Guide 174 · Conversions · GA4 + Tag Manager
Key events in GA4 advertising reports: Conversion performance, and what stays out
The Advertising section is where key events meet ad spend. Conversions created from GA4 key events appear there, in the Conversion performance report, while standard reports in the Reports section never show them. This guide finds the conversion in Advertising, reads its cost per conversion, and works out why the same key event shows a different number in the two places.
After the steps, the generate_lead key event appears under the Key events tab in Admin, and the standard reports show it within a day. The worked example below gives the count and the rate to expect.
Download the reference: the generate_lead key-event reference (JSON) (716 bytes, MD5 6794bad63ec8da21cbf02f39316ddb3a). It holds the event name, the counting method, the worked-example figures recomputed for this guide, and the checkpoints that prove the key event is recording. The figures in the file are the same figures shown on this page.
What you need
- A linked Google Ads account, with auto-tagging on. A conversion created from a GA4 key event needs the link; without it, there is nothing to create.
- A conversion created from the key event, in Advertising, then Conversion management, then New conversion. A key event on its own is not a Google Ads conversion.
- Marketer access or above in GA4, to create the conversion.
The trace
- Open Advertising, then Conversion performance. This report shows conversions, which are the key events shared with Google Ads, with the ad cost and the conversion count side by side.
- Find the generate_lead conversion row. In the worked example the week shows 96 conversions from generate_lead against 1,240 dollars of ad cost. The same key event in the standard reports shows 104 key events for the same week, and the two numbers are both correct.
- Work out the cost per conversion. Ad cost divided by conversions: 1,240 / 96 = 12.92 dollars per conversion, rounded to two places. That is the Advertising number the budget decision uses, not the standard-report count.
- Check why the counts differ. Google documents that conversions and key events are counted and dated differently: conversions are event-scoped and use data-driven attribution on the ad touchpoints, while key events are counted on the day they happen. The worked example gap is 104 − 96 = 8.
- Open Conversion management to check the settings. Advertising, then Tools, then Conversion management lists the conversions created from GA4 key events, with their counting method and conversion window. A conversion set to count One reports fewer conversions than the same key event counted once per event.
- Confirm the standard reports stay clean of conversions. Open Reports, then Engagement, then Events. The generate_lead row shows key events, and no conversion column appears. Google states that Google Ads conversions do not appear in standard reports or in Explore.
Dead ends
DEAD END — EXPECTING THE ADVERTISING COUNT TO MATCH THE STANDARD COUNT. The two counts are built differently, and a gap of a few percent is normal. Chasing an exact match wastes the week; the settings in Conversion management explain the gap.
DEAD END — READING STANDARD REPORTS FOR MEDIA PERFORMANCE. Google states the Reports and Explore sections analyze traffic acquisition, user behaviour, and site journeys, and are not the place to measure media performance. Use Conversion performance for the ad decision.
DEAD END — CREATING A CONVERSION AND EXPECTING PAST DATA. A conversion created this week does not restate last month. The Conversion performance report only fills from the creation date, and earlier weeks stay empty for that conversion.
End state
The week closes with 96 generate_lead conversions in Advertising at 12.92 dollars each, against 104 generate_lead key events in the standard reports. The gap of 8 is the counting and dating difference Google documents.
| Figure | Value |
|---|---|
| Ad cost in the week | $1,240.00 |
| Conversions in Advertising | 96 |
| Cost per conversion | $12.92 |
| Key events in standard reports | 104 |
| Gap between the two counts | 8 |
| Gap as a share of key events | 7.69% |
Cost per conversion is 1,240 / 96 = 12.92 dollars, and the gap is 104 − 96 = 8, which is 8 / 104 = 7.69% of the key event count, all recomputed in Python 3 and rounded to two places. The figures are a worked example, not a real property.
Sources
- Analytics Help — Conversions vs. key events in Google Analytics — what a key event is, the event to key event to conversion flow, and where Google Ads conversions appear
- Analytics Help — About key events — marking an event as a key event, the 30-event limit for a standard property, and 50 for Analytics 360
Checked 11 November 2026. The click path above is the one in Google's help pages, read 11 November 2026. Google Ads conversions appearing in the Advertising section and not in standard reports or Explore, and the counting and dating differences behind the gap, are as Google documents them. No step in this guide was run inside a live Analytics property or a live Google Ads account, because both need a Google sign-in and this site does not sign in as anyone. The figures on this page are a worked example recomputed in Python 3 with decimal arithmetic, not numbers from a real property. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.