Discrepancy between Facebook Ads and Google Analytics conversion tracking

Other Questions Google Analytics
1

Hello everyone,

I’m having trouble matching conversion data between Facebook Business Manager and Google Analytics. When I look at my Facebook campaigns, they show conversions happening. I’ve examined the attribution windows - both 1-day view-through and 28-day click-through conversions.

The 28-day click conversions should appear in my Google Analytics since these users actually clicked my ads and came to my site with UTM parameters. However, when I check Analytics for campaign sessions or source/medium reports, I don’t see any conversions attributed to my Facebook campaigns, even over extended date ranges.

I work in insurance and my Facebook Pixel runs in core mode due to compliance requirements. This means URL parameters get stripped away and tracking only works at domain level instead of specific page URLs. Could this be causing my reporting discrepancies?

Has anyone dealt with similar tracking issues? Any suggestions would be helpful. Thanks!

2

Had this exact problem running financial services campaigns. Core mode is definitely hurting you, but there’s another issue most people overlook. Facebook and GA4 count conversions completely differently - Facebook attributes based on ad interaction while GA4 defaults to last-click attribution. Your Facebook pixel in core mode also delays data processing, sometimes up to 72 hours. I got better results adding Conversions API alongside the pixel, though compliance might block this for you. Also check if your UTM parameters are getting stripped before Analytics fires - happened to me when our compliance scripts loaded too early on the page.

3

totally understand! core mode can mess up tracking big time. make sure ur UTM parameters are set up right. compliance can really complicate things, right? good luck!

4

The discrepancy you’re seeing between Facebook Ads Manager and Google Analytics for click-through conversions is likely a combination of factors, but your Facebook Pixel’s core mode setup is definitely a prime suspect.

The core mode pixel stripping URL parameters means that while Facebook is logging a conversion because its cookie or device ID matches a user who saw or clicked the ad, that same session might not be correctly attributed in Google Analytics.

When the UTM parameters are stripped, Google Analytics has no way to know that the session originated from your Facebook campaign and will likely attribute it to direct / none or referral / facebook.com, meaning the conversion is then attributed to the wrong source in Analytics, or worse, Facebook’s PageView, Lead, or Purchase standard events are firing, but the associated Analytics data is lost.

Even if you’re using a 28-day click-through window, if the initial click’s UTMs are lost, Analytics can’t connect the session to the campaign.

A powerful long-term solution to solve this and also future-proof your tracking against browser and iOS changes is to use the Facebook Conversions API (CAPI) in conjunction with your existing tracking.

Instead of relying solely on the browser-side Pixel, CAPI allows you to send conversion events directly from your server to Facebook.

You can implement this using a server-side tagging solution like Google Tag Manager (GTM) combined with a service like Stape or Google Cloud Platform to manage the server-side container.

This lets you enrich the event data with information that’s less susceptible to being blocked or stripped, improving the match rate for Facebook.

To then get this data into Google Analytics (GA4), you can leverage the Google Analytics Data API, although this is more about enriching your GA reports with data that was previously only available in Facebook, rather than correcting the source/medium issue which is best solved by ensuring your UTMs are not stripped, perhaps by using a URL shortener or a redirect service that preserves parameters before sending the user to the core mode domain.

The combination of Facebook CAPI + GTM + Stape or Google Cloud Platform essentially creates a robust, server-side data pipeline for Facebook, which is more reliable than the browser-side pixel, while still allowing you to focus on fixing the UTM issue for Google Analytics’ client-side tracking.

This approach helps reduce the discrepancy because it makes Facebook’s tracking much more resilient, even with your core mode limitation.