Facebook Ads and GA4: Fixing the Attribution Gap
The gap between Facebook Ads Manager reporting and GA4 is one of the most persistent frustrations in digital marketing measurement. Facebook regularly reports two to five times more conversions than GA4 for the same campaigns, and understanding why is the first step to making useful decisions from either dataset.
Why Facebook and GA4 Count Conversions Differently
The discrepancy is structural, not a tracking error. Facebook and GA4 use fundamentally different attribution approaches.
Facebook's default attribution window is 7-day click and 1-day view, it claims credit for any conversion that happens within 7 days of a click on a Facebook ad or 1 day of seeing the ad (even without clicking).
GA4 uses session based, last click or data driven attribution without a view through window.
This means Facebook claims conversions that happened via organic search, direct, or other channels within the 7-day window after a user was exposed to a Facebook ad.
A user who saw a Facebook ad on Monday, forgot about it, and then searched Google and converted on Friday would be counted by Facebook (view through or click attribution) but not by GA4 as a Facebook conversion.
Additionally, Facebook uses its own pixel data for attribution, which may see conversions that GA4's GA cookie cannot track, for example, conversions on mobile Facebook in app browsers that block third party cookies, or conversions by users who are logged into Facebook across devices.
The Impact of iOS Privacy Changes
Apple's App Tracking Transparency (ATT) framework, introduced with iOS 14. 5, significantly impacted Facebook's ability to track conversions via its pixel.
Users who opt out of tracking on iOS devices cannot be tracked by the Facebook pixel after the browser session ends.
Facebook partially compensates for this with modeled conversions, statistical estimates of conversions it can no longer observe, but these models are imperfect and their accuracy varies by campaign and audience.
For advertisers with a high iOS audience share, Facebook Ads Manager may show modeled conversions that significantly overstate actual performance.
Implementing Facebook's Conversions API (CAPI), which sends conversion data from your server directly to Facebook rather than relying entirely on the browser pixel, improves measurement accuracy for iOS users and provides a more reliable signal for Facebook's bidding algorithm.
Running both pixel and CAPI simultaneously with event deduplication is the recommended implementation.
Building a Reconciliation Framework
Rather than treating the discrepancy as a problem to eliminate, treat it as two lenses measuring the same phenomenon.
GA4 provides an accurate picture of the last touch journey and is useful for understanding the user's decision path.
Facebook Ads Manager provides Facebook's estimate of its contribution to the conversion journey, including upper funnel influence that GA4's last click model misses.
The ground truth is your backend: how many actual orders were placed, with what revenue, on which days.
Comparing both Facebook and GA4 conversion counts against backend orders for the same period gives you the absolute magnitude of each system's inflation or deflation.
From there, you can build a consistent ROAS calculation methodology, typically using GA4 or backend data as the denominator, that you apply consistently across channels for fair comparison.
Ready to audit your GA4 property?
Run a full GA4 audit in under 10 minutes. Free to start.
Start Free Audit