If your Google Ads conversions don’t match GA4, you’re not looking at a tracking error. You’re looking at two measurement systems built on fundamentally different rules. The GA4 vs Google Ads conversions discrepancy is one of the most common sources of confusion in paid search, and it trips up experienced marketers as much as beginners. The short answer to why your Google Ads conversions are different from GA4 is this: they use different attribution models, different counting methods, and different timing logic. Neither number is wrong. They’re just answering different questions.

They Are Not Measuring the Same Thing

This is the most important thing to accept before comparing any numbers. Google Ads is built to measure the value of your ads. GA4 is built to understand user behavior across your entire site or app. These are related goals, but they produce different outputs almost by design.

When Google Ads reports a conversion, it’s asking: which ad interaction deserves credit for this outcome? When GA4 reports a key event, it’s asking: did this event fire during this session or user journey? The framing is different, so the numbers will be different.

Attribution: The Biggest Driver of GA4 Conversion Discrepancy

Attribution is where the gap starts. By default, Google Ads uses data-driven attribution (DDA) for most conversion actions. DDA distributes fractional credit across multiple touchpoints in the path to conversion, using Google’s machine learning to weight each interaction. That means a single conversion might assign 0.4 credit to one click and 0.6 to another.

GA4 also supports data-driven attribution, but it applies it differently. GA4’s attribution model covers all channels, not just paid search. It considers organic search, direct, email, and referral traffic alongside Google Ads. If a user clicked a Google Ads link three weeks ago, then converted through an organic search visit, GA4 might give Google Ads partial or no credit depending on the model and lookback window configured.

Google Ads, by contrast, only distributes credit among its own ad interactions. It doesn’t dilute its numbers with other channels. So the same conversion can appear as a full conversion in Google Ads and as a partial or zero contribution in GA4.

Google Ads measures the value of its own clicks. GA4 measures the full journey. Neither perspective is wrong, but they will never produce identical numbers.

Last-Click vs Data-Driven in GA4

If your GA4 property is still configured with last-click attribution rather than data-driven, the gap can widen further. Under last-click, GA4 gives all the credit to the final touchpoint before conversion. If the last click was organic or direct, Google Ads gets zero credit in GA4 for that conversion, even if a Google Ads click earlier in the funnel played a meaningful role.

It’s worth checking your GA4 attribution settings under Admin > Attribution Settings. Many accounts are still on last-click without realizing it, which systematically underrepresents paid channels in GA4.

Conversion Counting: One Per Click vs One Per Session vs All

Even when attribution is aligned, counting logic creates discrepancies. Google Ads lets you configure each conversion action to count every conversion or one conversion per click. For purchase tracking, most advertisers use one per click to avoid inflating numbers when users hit a thank-you page multiple times. For lead forms, every conversion is often the right choice.

GA4 counts key events differently. By default, a key event fires every time the trigger condition is met in a session. So if a user visits your thank-you page twice in the same session, GA4 might count two key events. If your Google Ads conversion action is set to one per click, you’ll see one conversion in Google Ads and two in GA4.

The reverse also happens. Some Google Ads accounts count every conversion from a single click, while GA4 might deduplicate events using its own session logic. The result is Google Ads over-reporting relative to GA4.

The Practical Impact

Imagine a user clicks your ad, lands on your site, and completes a purchase. They then refresh the confirmation page. Google Ads (set to one per click) records one conversion. GA4 may record two key events. Now multiply this across thousands of sessions and you can see how counting alone creates a persistent, structural gap between the two platforms.

Timing and the Conversion Window

Google Ads applies conversions to the date of the ad click, not the date the conversion happened. This is called click-date attribution. If someone clicks your ad on March 1st and converts on March 20th, Google Ads records that conversion against March 1st. GA4 records the key event on March 20th.

This creates a visible mismatch when you compare date ranges. Looking at a report for the first week of a month in Google Ads will often show more conversions than GA4 for the same period, because Google Ads is pulling in conversions that happened later in the month and assigning them back to click dates within that week.

The reverse is also true. GA4 will show more conversions in a given period when users who clicked ads before that period finally convert. Neither platform is reporting a tracking failure. They’re just using different anchors for the same event.

This timing difference is especially pronounced in industries with long consideration cycles: B2B software, financial products, travel. If your lookback window is 90 days and you have a 30-day sales cycle, the click-date vs event-date gap can be significant across any weekly or monthly comparison.

Tracking Implementation Gaps

Beyond the methodological differences, there are practical reasons data doesn’t match. These are actual tracking gaps rather than expected discrepancies.

• Tag firing failures: GA4 tags and Google Ads conversion tags are separate. One can fire while the other doesn’t. This is common on pages with complex JavaScript, slow load times, or aggressive ad blockers.
• Consent mode: If you’ve implemented Google’s Consent Mode, users who decline tracking may be modeled into Google Ads conversions but excluded from GA4 entirely. This is by design, but it inflates Google Ads numbers relative to GA4 observed data.
• Cross-device journeys: A user who clicks an ad on mobile and converts on desktop is handled differently by each platform. Google Ads uses signed-in Google account data to stitch these together. GA4 relies on User-ID or Google Signals, which may not be active or accurate.
• GA4 key events not imported into Google Ads: You may have configured GA4 key events that you haven’t imported as conversion actions in Google Ads. The numbers will then be structurally different because they’re not tracking the same events.

GA4 Key Events vs Google Ads Conversion Actions

When Google rebranded GA4 conversions as key events in 2024, it reinforced the distinction between the two platforms. In GA4, a key event is simply an event you’ve marked as important. It has no relationship to your Google Ads account unless you explicitly import it.

When you import a GA4 key event into Google Ads, it becomes a conversion action. At that point, Google Ads applies its own attribution model, counting logic, and click-date timing to that imported event. So the same underlying event produces different numbers in each platform, because each platform processes it through its own measurement layer.

This is worth making explicit to anyone who assumes that importing a GA4 key event into Google Ads means the two platforms will now agree. They won’t. The import just connects the signal. The divergence in reporting remains.

A Practical Reconciliation Routine

Rather than trying to make the numbers match, the goal is to understand what each number represents and use each one appropriately.

Step 1: Audit Your Attribution Settings

Check the attribution model in both platforms. In Google Ads, go to Tools > Measurement > Attribution. In GA4, go to Admin > Attribution Settings. If they’re different, that explains a large portion of the gap.

Step 2: Check Counting Methods

In Google Ads, review each conversion action and confirm whether it’s set to every conversion or one per click. Cross-reference with how GA4 is counting the equivalent key event. For purchase events, both should be set to count once. For micro-conversions like page views or scroll depth, the right counting method depends on your reporting goals.

Step 3: Compare Same-Period Data Carefully

When comparing date ranges, use a date range long enough to reduce the timing distortion from click-date vs event-date attribution. A 90-day window is more reliable than a 7-day window. For recent data, understand that Google Ads numbers will shift as delayed conversions are attributed back to earlier clicks.

Step 4: Identify the True Tracking Gaps

Use GA4’s DebugView and the Google Tag Assistant to verify that tags are firing correctly on confirmation pages and other conversion points. If GA4 is recording fewer events than Google Ads, check whether Consent Mode or ad blocking is likely to explain the difference.

Step 5: Decide Which Number Drives Each Decision

For bidding and campaign optimization within Google Ads, use Google Ads conversion data. The bidding algorithms are calibrated against this number. Using GA4 data to judge campaign performance introduces attribution mismatch into your optimization loop.

For understanding actual user behavior, funnel performance, and cross-channel contribution, use GA4. It gives you a more complete picture of the customer journey, free from the channel-specific bias of Google Ads reporting.

Which Number to Trust

There’s no single correct answer, because the question itself is too broad. It depends on the decision you’re making.

• If you’re evaluating whether to increase budget on a campaign, trust Google Ads conversions. That’s the number its Smart Bidding is optimizing toward.
• If you’re assessing whether paid search is contributing to revenue relative to other channels, trust GA4 with a multi-touch attribution model.
• If the two numbers diverge by more than 20-30%, investigate before trusting either. That level of discrepancy often points to a real tracking issue rather than expected methodology differences.

A reasonable rule of thumb: use Google Ads data to run your campaigns, and use GA4 data to understand your business.

Where Adsroid Copilot Fits Into This

One practical challenge with the GA4 vs Google Ads data mismatch is that most tools only read one source at a time. You end up switching between platforms, manually reconciling numbers before you can decide whether to act.

Adsroid Copilot connects to your Google Ads account and surfaces optimization opportunities based on actual campaign performance data. Within the Adsroid AI Chat, you can ask questions about your campaigns and get answers that draw on Google Ads data directly, without having to export reports or cross-reference spreadsheets.

When Copilot detects an opportunity, such as a keyword exceeding your configured Critical CPC threshold or a campaign that’s significantly outperforming others on budget, it proposes a specific action. In Copilot mode, you review and approve that proposal through the dashboard, by email, or through the AI Chat. In Autopilot mode, supported actions execute automatically within the rules you’ve configured.

This isn’t a replacement for understanding your data. If your Google Ads conversions don’t match GA4 because of a tracking problem, Copilot won’t fix the underlying measurement gap. But for the operational side of running campaigns, having your Google Ads data readable in one conversation rather than spread across multiple reports reduces the friction between insight and action.

FAQ

Why are my Google Ads conversions higher than GA4?

Google Ads commonly reports more conversions than GA4 for three reasons. First, Google Ads uses data-driven attribution across its own clicks only, while GA4 may distribute credit across other channels, reducing the share assigned to paid search. Second, Consent Mode can allow Google Ads to model conversions for users who declined tracking, while GA4 records nothing for those users. Third, Google Ads assigns conversions to the date of the click rather than the date of the conversion event, which makes recent periods look more active in Google Ads than in GA4.

Should I import GA4 key events into Google Ads?

Importing GA4 key events into Google Ads is a valid setup, particularly if you want a single source of truth for event definitions. However, importing a GA4 key event does not make the two platforms report the same number. Google Ads applies its own attribution model, counting logic, and click-date timing to the imported event. The reporting will still diverge. The main benefit of importing is consistency in event definition, not consistency in reported volume.

What is a normal discrepancy between GA4 and Google Ads conversions?

A 10 to 20 percent difference is common and usually explained by attribution and timing methodology. A discrepancy above 30 percent, especially if it’s consistent rather than period-specific, often indicates a tracking implementation issue such as a misfiring tag, incorrect Consent Mode setup, or a counting configuration that doesn’t match your intentions. At that point it’s worth auditing both tracking setups before trusting either number for decisions.

Which attribution model should I use in GA4?

For most advertisers, data-driven attribution in GA4 is the most accurate model available. It distributes credit across touchpoints based on actual conversion path data rather than arbitrary rules. Last-click tends to undervalue upper-funnel activity and can systematically underreport paid channels if users frequently return through organic or direct sessions before converting. If your GA4 property is still on last-click, switching to data-driven will usually bring GA4 numbers closer to what Google Ads reports, though a gap will always remain.

Can I ever get GA4 and Google Ads to show exactly the same conversion number?

No, not in practice. The platforms are built on different measurement philosophies. Even with identical attribution models, the click-date versus event-date difference alone will cause divergence in any finite reporting window. The goal isn’t to reconcile the numbers into one figure. The goal is to understand what each number represents and use each one for the decisions it’s suited to inform.