GA4 vs. Google Ads Reporting: Reconciling Conflicting Data

Why do Google Analytics 4 and Google Ads show different conversion numbers?

Google Analytics 4 and Google Ads report different conversion figures because they measure user journeys through fundamentally different analytical frameworks, attribution scopes, and reporting timelines. Google Ads exists to demonstrate the performance and commercial return of paid campaigns within its own ecosystem, while Google Analytics 4 (GA4) measures aggregate user activity across every acquisition channel touching a website or application. Discrepancies between the two platforms are normal, expected, and present in virtually every marketing tech stack.

A conversion is an action completed by a user that a business deems valuable, such as a purchase, lead form submission, or phone call. In Google Ads, conversions are measured through direct tracking tags or imported events, typically attributing value to specific ad interactions. In GA4, these actions are configured as key events—previously termed conversions in Universal Analytics—and evaluated against direct, organic, social, referral, and email channels alongside paid campaigns.

When marketing teams export client reports or evaluate return on ad spend, they frequently encounter scenarios where Google Ads claims 100 conversions while GA4 records only 60 attributed to Google Ads traffic. These variations do not necessarily indicate broken tracking code or invalid data collection. Instead, they arise from mathematical, structural, and temporal variations in how each system processes, credits, and logs commercial actions.

How does conversion timing differ between GA4 and Google Ads?

The most common technical cause of data misalignment is the difference in conversion timing: Google Ads records conversions against the date of the ad click, whereas GA4 records them against the date the conversion event actually took place. This fundamental distinction alters performance visualisations across any given reporting window.

Consider a consumer who searches for commercial conveyancing services on a Monday, clicks a Google Search ad, reviews the landing page, and departs without taking action. On Thursday of the following week, having reviewed competitor options, the user returns directly to the website via a saved bookmark and completes an enquiry form. Google Ads processes this action retrospectively, applying the lead to Monday's data because that is when the paid ad interaction occurred. GA4, by contrast, timestamps the event on Thursday, applying the conversion to the direct traffic channel or distributing fractional credit across touchpoints depending on the active attribution model.

If an analyst pulls a performance report covering only Monday to Wednesday of that first week, Google Ads will include that lead, whereas GA4 will show zero conversions from that specific session. If the reporting window is closed immediately after an ad campaign concludes, Google Ads data will continue to fluctuate for weeks into the future as late-converting users complete journeys within their allocated lookback windows. GA4 historical data remains comparatively static once initial processing finishes.

How do attribution models distort conversion reporting across platforms?

Attribution models dictate how credit for a conversion is distributed across user touchpoints, and the primary discrepancy stems from Google Ads operating a single-channel view while GA4 operates a cross-channel view. Unless manually adjusted, Google Ads ignores all external interactions that take place outside its advertising network.

In Google Ads, the default data-driven attribution model allocates fractional credit exclusively among Google Ads touchpoints, such as paid search impressions, YouTube views, and Performance Max clicks. If a user interacts with three separate Google Ads campaigns before purchasing, the platform divides 100 percent of that conversion value among those three campaigns. It remains blind to the organic search click, email newsletter link, or organic LinkedIn post that may have preceded or followed those ad engagements.

GA4 evaluates the complete cross-channel path. Its data-driven attribution model analyses touchpoints across all registered channels. In the same scenario, GA4 might determine that the organic search visit and the email newsletter interaction carried 70 percent of the algorithmic influence, leaving Google Ads with only 30 percent of the fractional conversion value. Consequently, when viewing the GA4 User Acquisition or Traffic Acquisition reports, Google Ads will receive a fraction of the conversion total that the dedicated Google Ads interface claims for itself.

Furthermore, if a marketer uses the 'Last Click' model in both platforms, the definitions remain conflicting. In Google Ads, 'Last Click' means the last Google Ads click prior to conversion. In GA4, 'Last Click' means the last click from any non-direct source across the entire internet landscape. Only when Google Ads is the solitary touchpoint in the conversion journey will both systems attribute the full unit of conversion to the campaign.

How do conversion counting methods and lookback windows cause discrepancies?

Discrepancies frequently emerge from conflicting conversion counting settings and mismatched lookback windows configured within the administrative panels of each platform. Both settings govern how many times an action is tallied and how far into the past a system looks to connect a click with an outcome.

In Google Ads, conversion actions can be counted as 'Every' or 'One'. The 'Every' setting is typically recommended for e-commerce, where every purchase completed by a returning customer represents incremental revenue. The 'One' setting is standard practice for lead generation, ensuring that multiple form submissions or page refreshes by a single user within a session are counted only once. GA4 offers a similar mechanical toggle for key events: 'Once per event' (equivalent to 'Every') or 'Once per session' (equivalent to 'One'). If Google Ads is configured to count 'Every' conversion and GA4 is set to count 'Once per session', a single user submitting two enquiries within 20 minutes produces two conversions in Google Ads and one in GA4.

Conversion windows—the maximum period between an ad click and the subsequent conversion—also introduce friction:

• Google Ads permits click-through conversion windows ranging from 1 to 90 days, with 30 days serving as the platform default.
• Google Ads offers view-through conversion windows, which attribute conversions to users who saw an ad impression but did not click, typically configured between 1 and 30 days.
• GA4 applies a maximum lookback window of 30 days for acquisition events and up to 90 days for key events, but it does not record view-through conversions from standard search inventory.
• GA4 ignores display impression views entirely unless specific Campaign Manager 360 or Display & Video 360 enterprise integrations are active.

If a user views a display ad on Tuesday, does not click, but returns via organic search on Wednesday to buy, Google Ads can register a view-through conversion. GA4 will attribute that transaction entirely to organic search, widening the reporting delta.

What role do consent management, modelling, and processing delays play?

Modern web analytics operates in an environment governed by strict privacy legislation, including the UK General Data Protection Regulation (UK GDPR) and the EU ePrivacy Directive, which introduce discrepancies through consent management frameworks, machine-learning data modelling, and varying processing schedules.

When a user declines consent via a cookie banner, platforms operating Google Consent Mode v2 respond differently. Google Ads employs behavioural and conversion modelling to estimate lost conversions caused by consent rejection, using ping data that contains non-identifying technical signals. These modelled conversions are integrated directly into standard Google Ads conversion columns. GA4 also deploys conversion and behavioural modelling, but it requires substantial data thresholds—such as 1,000 daily events with analytics_storage='denied' for at least seven consecutive days—before its predictive machine-learning models activate.

Smaller websites often qualify for Google Ads conversion modelling while falling below the volume threshold required for GA4 behavioural modelling. In these instances, Google Ads estimates conversions for non-consenting traffic, whereas GA4 records strictly observed, consented data, resulting in a lower conversion count in analytics.

Data processing latency introduces another operational variance. GA4 operates on a processing delay of 24 to 48 hours for standard properties. Although the platform offers a 'Realtime' report and intraday data streams, standard attribution and exploration reports can take up to two days to fully ingest, process, and attribute events. Google Ads conversion tracking generally processes clicks and reported conversions faster, often within 3 to 12 hours, though conversion adjustments and data-driven attribution calculations can continue to adjust figures for up to seven days.

How should marketers reconcile and audit conflicting conversion data?

Marketers should reconcile conflicting data by selecting an intentional source of truth for each specific reporting function, standardising collection architecture, and conducting systematic tracking audits. Attempting to force identical figures across both tools is a technical impossibility; the objective is reconciliation through understanding, not mathematical parity.

A structured auditing process requires four technical checks:

1. Audit the tagging mechanism: Determine whether Google Ads uses native Google Ads conversion tracking tags via Google Tag Manager or imported GA4 key events. Using native tags yields faster reporting, view-through metrics, and platform-specific optimisation signals. Importing GA4 events creates near-total alignment between platforms, but suppresses Google Ads view-through data and delays smart bidding adjustments.
2. Align counting settings: Ensure that counting rules reflect business reality across both platforms. If lead forms are tracked, set Google Ads to 'One' conversion and GA4 to 'Once per session'. For e-commerce transactions, set Google Ads to 'Every' and GA4 to 'Once per event'.
3. Harmonise lookback windows: Inspect the click-through lookback periods in Google Ads and set them to match GA4 key event windows, typically 30 days for general events. Remove view-through conversion metrics from primary Google Ads reporting tables when presenting paid search performance alongside analytics data.
4. Verify URL parameters: Confirm that auto-tagging is enabled in Google Ads to append the Google Click Identifier (GCLID) to destination URLs. Ensure manual UTM parameters do not conflict with auto-tagging, which can cause GA4 to misclassify paid search traffic as unassigned, direct, or organic.

Establish clear operational boundaries for stakeholders. Google Ads should be treated as a dedicated bidding engine and tactical campaign management tool. Its metrics explain how efficiently individual ads, keywords, and audiences interact with users who touch the paid ecosystem. GA4 must serve as the commercial source of truth for total business performance and budget allocation, providing the cross-channel perspective needed to evaluate how paid ads function in concert with organic search, direct visitors, and retention marketing.