On this page
Google Ads and GA4 both report conversions, so the totals should look alike. They rarely do. Each tool dates the conversion differently, credits different sources, and applies its own counting and tagging rules. None of those differences is a bug, but each one changes the number.
Why Google Ads and GA4 conversions don’t match
The gap usually comes from definitions. A click on the 30th that converts on the 2nd lands in different months in the two tools. Google Ads puts the conversion on the 30th, where the ad interaction happened. GA4 puts it on the 2nd, where the conversion event happened. Over a full month the totals can still differ, even when both tools count the same people.
| Mismatch | Google Ads view | GA4 view | Report rule |
|---|---|---|---|
| Date | Date of the ad click | Date the conversion event happened | Pick one date basis and label it |
| Credit scope | Google Ads interactions only | All channels, including organic, email, and direct | Compare channel credit, not raw totals |
| Attribution and windows | Its own model and conversion window | Its own model and lookback window | Match the settings or state the gap |
| Counting | Every or One conversion per click | Once per event or once per session | Match the counting rule before comparing |
| Tags | Google Ads conversion tag | GA4 event on its own trigger | Confirm both fire on the same action |
| Clicks vs sessions | Counts clicks | Counts sessions | Expect gaps from bounces, consent, and blockers |
| Time zone and currency | Account setting | Property setting | Align both before comparing revenue |
Credit, models, and counting rules
Credit scope is the largest source of disagreement. Google Ads only credits Google Ads interactions. GA4 credits across all channels, so organic search, email, or direct can take credit for a conversion that Google Ads also claims. Both tools can be right by their own rules and still disagree about the same sale.
Attribution settings compound the problem. Each tool has its own attribution model and its own lookback or conversion window. If one is set to a longer window or a different model, totals will move even when the underlying clicks and events are identical. Counting rules matter too. A Google Ads conversion action can count every conversion per click or only one. GA4 key events can count once per event or once per session. A lead action set to one per click in Ads and once per event in GA4 will diverge as soon as a visitor submits twice.
Google Ads also reports columns that GA4 does not show in the same way. Its “All conversions” figure includes more than the “Conversions” column, and it can include cross-device and modeled conversions. GA4 cannot see the same signed-in signals, so comparing the broadest Ads column with GA4 will overstate the gap.
Tags, clicks, and auto-tagging
If Google Ads uses its own conversion tag and GA4 uses a separate event, the two fire on different triggers and can fail independently. Importing GA4 key events into Google Ads aligns the definition, but those conversions are still credited using Google Ads rules. The definition matches while the credit does not.
Clicks and sessions also differ. Google Ads counts clicks and GA4 counts sessions. Bounces before the tag loads, consent denials, ad blockers, and several clicks inside one session all push the two apart. Auto-tagging with gclid is what lets GA4 connect a session back to the ad. Without it, or when a redirect strips the gclid, GA4 can record paid traffic as organic or as (not set).
Reconcile before the review
- Name each conversion action in Google Ads and the matching GA4 event or key event.
- Write down the date basis, attribution model, and window in both tools.
- Confirm the counting rule for each action, including one per click versus once per event or session.
- Check that auto-tagging is on and that redirects keep the gclid intact.
- Align the account time zone and currency, then state the expected gap in the report.
Where Google Ads should win
Google Ads should be the source of truth for bidding, spend, and in-platform optimization. Smart bidding and campaign decisions run on Google Ads conversion data, so the number used to set budgets should come from there. Keep the Ads definition stable so the optimization signal does not change under the team without a note.
Where GA4 should win
GA4 should be the source of truth for cross-channel behavior and for comparing channels side by side. It sees organic, email, and direct alongside paid, which Google Ads cannot do. Revenue reporting belongs to the CRM or backend, with GA4 used to explain the web journey behind it. The problem comes when a team uses GA4 to set bids or Google Ads to claim every channel’s credit.
Go further with the platform mismatch guide, the dynamic UTM guide, and the HubSpot and GA4 comparison. If you want a second pair of eyes on the numbers, book a tracking audit: bring the disputed report and we’ll map the first rule your team can trust.
Frequently asked questions
Why does Google Ads show more conversions than GA4?
The two tools date and credit conversions differently. Google Ads uses the ad click date and only credits Google Ads interactions, while GA4 uses the event date and credits all channels. Counting rules, tags, and lookback windows can also differ.
Should Google Ads or GA4 be the source of truth?
Use Google Ads for bidding, spend, and in-platform optimization. Use GA4 for cross-channel behavior and channel comparisons. Use the CRM or backend for revenue. Pick one documented rule for each metric.
How much difference between Google Ads and GA4 is normal?
Some difference is expected because dates, attribution models, windows, clicks versus sessions, and consent all vary. A large or sudden gap usually points to a changed setting, a broken tag, or a counting rule that no longer matches.
Can MetricMaven reconcile Google Ads and GA4?
Yes. We map each conversion action to its GA4 event, compare the date basis, attribution settings, counting rules, and tags, and document the expected gap so the team can explain it without rebuilding the report by hand.