A GA4 key event does not become an Ads bidding goal by itself

Name the three layers before comparing numbers

A purchase event is the measurement record sent to GA4. A key event is a GA4 event that you marked as important to the business. A Google Ads conversion is an action with its own source, goal settings, counting rules, and optimization status. Google's current product flow lets you create an Ads conversion from an Analytics key event. The same site can also have an independently tagged Ads website conversion.

Write down the exact source for every conversion action in the Ads account. A GA4-sourced purchase and a directly tagged Ads purchase can both observe the same order. If both are primary in the selected campaign goal, bidding may optimize against two signals for one sale. Audit the goal before adding another tag or importing another event.

Why both products can show different counts

GA4 key event reports can cover paid and organic traffic. Google Ads conversion reports are organized around ad interactions, selected actions, and configured attribution. Ads commonly reports the conversion against the date of the ad click in standard conversion columns, while Analytics reports the event on the date it occurred. A shopper who clicks Monday and buys Tuesday can shift the daily totals without any broken pixel.

Counting method, conversion window, attribution model, time zone, eligibility, and modeling can also affect the comparison. Check those settings before treating the gap as dropped requests. Google's documentation describes how GA4 conversions shared with Ads can have settings managed across both products, with availability varying by property. Avoid assuming an older import workflow exactly matches your current account interface.

Choose the Ads action that matches the bidding question

If the business wants bidding on completed purchases, select a conversion action that represents confirmed purchases with a stable value and transaction ID. If you create it from GA4, confirm that the Analytics event is reliable and the Ads action has the intended goal and Primary setting. Google says Analytics-created actions can be Secondary by default, so verify the actual Ads action rather than assuming import means optimization.

Keep a second action as Secondary when you want diagnostic visibility without putting both into the normal bidding goal. Secondary actions generally appear in All conversions; a custom goal is an exception that can use them for bidding. Decide which action is the business source for campaign optimization and document that choice next to the order event contract.

Debug the source event before attribution

Place one test order and record its transaction_id. Confirm the GA4 purchase event arrived with the correct value, currency, and ID. If using a direct Ads tag, inspect its conversion ID, label, value, currency, and transaction_id too. Then check whether the Ads action sourced from Analytics or from the direct tag, and whether its status shows receipt. A green tag debugger with no purchase event in the intended property is a wiring problem, not a model problem.

When the raw events exist in both destinations, compare like for like: same date range, account time zones, by-conversion-time column when appropriate, action, and attribution settings. Google Ads and GA4 still need not produce identical credited totals. Pixellint can validate a captured hit or payload; account settings and attribution require a separate check in Google Analytics and Google Ads.

Keep the purchase ledger as the control

Export completed, non-test order IDs from your backend. Count unique confirmed orders before comparing either ad platform. The ledger answers how many sales occurred; GA4 answers which events it observed; Google Ads answers which configured conversions it credits to eligible ads. Compare the corresponding layer instead of adding platform totals.

A practical reconciliation sheet has one row per order ID and columns for backend status, GA4 purchase observed, direct Ads hit observed, GA4-sourced Ads action, and selected campaign goal. This makes missing events, duplicate tags, and attribution-only differences visible without changing bidding settings to chase a single day's report.

Sources

• Google Analytics: Conversions versus key events
• Google Analytics: Conversion flow from event to Ads
• Google Ads: Create conversions from Analytics events
• Google Ads: Primary and secondary actions

Check the artifact

Paste the pixel URL or JSON body into the playground. Same engine as pixellint validate. Artifacts you test may be stored; see privacy.