Google Ads conversions vs GA4 conversions: why they never match

Google Ads conversions count important actions that can be credited to a Google Ads interaction: a purchase, a signup, a call. GA4 conversions count important actions your Google Analytics tag actually saw, from every channel that produced them. Google built the two tools so you can measure a campaign and understand your site, and Google's own documentation says the numbers are different metrics whose differences are rooted in their distinct purposes. An exact match is not the design.

• Google Ads reports its conversions on the day of the ad interaction, then lets conversion delay land the rest over time. GA4 counts on the date the action happened on your site.
• Google Ads counts Every conversion or One per click, per conversion action. GA4 counts a key event once per event or once per session.
• By default GA4 conversions can receive credit from paid and organic channels. Google Ads only credits interactions from its own account.
• Time zones, processing delays, consent, blocked tags and invalid conversions add distance on top of that.

Google Ads reports conversions to show how often an action followed an ad interaction. Its own troubleshooting guide describes the reporting as tied to the ad: you choose the conversion action and how it counts, and Google Ads only reports conversions when there were interactions from the same Google Ads account.

• Google Ads counts conversions on the ad interaction date, then shows them over time as conversion delay clears. It can take up to about 7 days for conversion data to fully appear after big changes or a fresh account link, and Google recommends allowing 24 to 48 hours of synchronization between Google Analytics and Google Ads before comparing.
• Every conversion action selects a count: Every counts all conversions after an interaction, One counts a single conversion per ad click. The choice changes the column you see.
• Primary conversion actions run bidding and appear in the main Conversions columns; Secondary actions are for observation only and may need the All conversions column to show at all.
• Google Ads removes invalid conversions from its reports after the fact, and it does not include view-through conversions in the Conversions column by default.
• Cross-device conversions are modeled, and changing the attribution model changes how much credit each interaction receives.

Google Ads answers one question well: which conversions did my ads actually drive. Its numbers only exist where an ad interaction from your account happened.

Google Analytics 4 marks events that matter to your business as key events, and a conversion is then created from a key event and shared with Google Ads. Google describes conversions as event-scoped: they can use data-driven attribution instead of last non-direct click, and by default they can receive credit from paid and organic channels.

• GA4 conversions are built from events, so they only exist where the GA4 tag ran. Where consent is missing, Google can use behavioral modeling and Consent Mode, so the count may be modeled rather than simply absent.
• Key events count once per event (recommended) or once per session, and the choice changes the totals. Conversions created from those key events inherit the counting method by default.
• GA4 conversion windows follow the key event lookback window: 30 days by default for the first_open and first_visit key events, and 90 days by default for all other key events. For those other key events you can choose 30, 60 or 90 days, and the acquisition events can switch to 7 days.
• GA4 reports in the Google Analytics property time zone, and it counts a conversion from every channel that produced the event, including organic search, email, social or a direct type-in.
• Google says conversions and key events serve different audiences: conversions for a cross-channel advertising view, key events for traffic, behaviour and site journey analysis.

GA4 answers a different question: what important things happened on my site, from whatever route the visitor took. Some of those routes have nothing to do with an ad, which is the first reason the columns separate.

Google's own pages for the two tools name most of the causes below; the final one is a practical check you can apply to your own reports. Some push Google Ads higher, some push GA4 higher, and most of the time several act at once:

• Different jobs, different credits. GA4 conversions can receive credit from paid and organic channels by default, so conversions from email, social, organic search and direct visits count in GA4 even with no ad interaction involved. Google Ads counts only conversions that follow interactions from that same Google Ads account.
• Conversion delay. Google Ads reports conversions on the ad interaction date, while GA4 reports on the conversion date. The newest days on the Google Ads side can still be filling in, and Google recommends allowing 24 to 48 hours of synchronization before comparing the two.
• Counting options. Google Ads counts Every conversion or One per click, per action. GA4 counts once per event or once per session. If the Ads action counts Every while the GA4 key event counts once per session, the same purchases become different numbers.
• Different windows. Google Ads click-through and view-through conversion windows are set per conversion action. GA4 key events use a lookback window of 30 days by default for acquisition events and 90 days by default for other key events. A visitor who converts two weeks after a click can be inside one window and outside the other.
• Tag coverage and consent. A conversion imported from a GA4 key event shares the GA4 tag, so visitors who block it or leave before it loads create no event in either tool. When consent is missing, Google can use behavioral modeling and Consent Mode, so the count may be modeled rather than simply absent. A conversion tracked with Google's own Google Ads conversion tag has separate tag and consent coverage, which adds to the gap.
• Invalid conversions. Google Ads removes invalid conversions from its reports after the fact, which can look like a small drop over time, while GA4 keeps reporting the sessions and events those visits produced.
• Attribution settings. Switching the attribution model changes how the same actions are credited. Google says the settings for conversions created from Analytics events match across both platforms by default, but changes on either side stop that.
• Time zones. GA4 reports in the Analytics property time zone, Google Ads in the account time zone. The same day can mean different hours, so daily totals rarely line up cleanly.

None of this means either tool is broken. Each one is following its own rules for its own job. The gap only needs investigating when it changes suddenly, when one campaign shows conversions in one tool and almost none in the other for days, or right after a tag, window or attribution change.

• Compare the closest pair. Build or reuse the Google Ads conversion created from the same GA4 key event. Google's default settings then match counting method and windows across both tools, which removes most of the guesswork.
• Compare the same dates and time zone. Give the Google Ads side two or three days to clear conversion delay, skip the newest day or two, and remember the account time zone and the property time zone can differ. Google recommends the Conversions (by conv. time) column to line the two reports up by conversion date.
• Match the counting options. Check whether the Ads conversion action counts Every or One, and whether the GA4 key event counts once per event or once per session. Two actions measuring the same thing with different counts will never tie.
• Check the tag on the conversion page. The thank-you or confirmation page needs the Google tag with the event running. A page that is not tracked at all explains conversions Google Ads counts and GA4 never sees.
• Compare weeks, not days. Daily totals move because of delay, returning visitors and windows. A stable weekly direction is the honest signal, and a sudden jump in one tool while the other stays flat is what deserves a look.

If conversions exist in one platform and almost none in the other for several days on the same campaign, check the tag on its landing and confirmation pages, then the counting options and the time zones. Google lists tag setup, lookback windows, count settings, action optimization, attribution settings and invalid traffic among the usual discrepancy factors.

If you want a second, independent view of your conversions, add a tracking code you own. Hitsteps uses a single tag on the site that starts a real-time visitor list with pages, countries and referrers, UTM and ad attribution, actions, goals and heatmaps, all in one dashboard. It records the visits its tag sees as they happen, and it runs alongside Google Ads and GA4 for as long as you want all three.

That gives you an action and goal count that comes from your own site, next to the two Google numbers, with the same attribution caveat. Like any analytics tag, it only sees visits where the tag loads and JavaScript runs, so treat it as a second view, not a perfect total. Where your conversions disagree, you can look at the individual visits and see which ones actually arrived from your ads.

Definitions and causes above follow Google's own documentation, checked 12 November 2026:

• Google Ads Help: Data discrepancies, factors and troubleshooting (support.google.com, answer 7457111)
• Google Ads Help: About conversion counting options (support.google.com, answer 3438531)
• Google Ads Help: Measure web key events from Google Analytics properties (support.google.com, answer 9520128)
• Google Analytics Help: Conversions vs. key events in Google Analytics (support.google.com, answer 13965727)
• Google Analytics Help: Select attribution settings (support.google.com, answer 10597962)
• Google Analytics Help: Change the counting method of key events (support.google.com, answer 13366706)
• Google Analytics Help: Change the key event lookback window (support.google.com, answer 16291704)