Why Your Conversion Data Differs Between Google Analytics and Meta Ads
by Edward Upton

Meta Ads Manager and GA4 will never report the same number of conversions for the same campaign. They count different things, credit them on different rules, and report them on different dates. Below are the eight reasons the numbers differ, the ones that are tracking faults rather than design, and how to compare the two like for like.
TL;DR: Most of the gap comes from attribution. Meta credits purchases after ad views and models conversions it cannot see, while GA4 only credits visits that reach your site. The rest comes from tracking: in-app browsers, ad blockers, consent and duplicate events. Fix the tracking, then compare Meta's 1-day click conversions with GA4's Paid Social purchases on a last-click basis.
If you run Meta Ads for a Shopify store, you have probably seen Ads Manager claim far more purchases than GA4 credits to Paid Social. Neither platform is lying. They are answering different questions.
There are two numbers to compare: link clicks against GA4 sessions, and Meta purchases against GA4 purchases and revenue. Each has its own causes.
Why Meta link clicks don't match GA4 sessions
1. The shopper leaves before the GA4 tag runs
Meta records a link click the moment someone taps the ad. GA4 only records a session once the landing page loads and the GA4 tag fires. On mobile, that gap can be several seconds, and shoppers who do not know your brand often go back to the feed before the page finishes.
As a result, link clicks are always higher than sessions. The gap grows with slow landing pages and heavy themes, where tracking scripts queue behind everything else on the page.
- What to check: compare Meta's "Landing page views" metric with GA4 sessions instead of link clicks. Landing page views only count visits where the page loaded, so it is the closer match.
- What to fix: mobile page speed. Each tracking script on the page adds load time, so remove the ones you no longer use.
2. The visit arrives without campaign information
Facebook and Instagram open links in their own in-app browser. GA4 often cannot see Meta as the referrer there, so without UTM parameters the session lands in Direct or Unassigned rather than Paid Social.
The bigger problem comes later. The in-app browser keeps its own cookies. A shopper who clicks an ad, browses in the Instagram browser, and buys the next day in Safari arrives as a new, direct visitor. GA4 has no way to connect that purchase to the ad.
- What to fix: add UTM parameters to every ad, using Meta's URL parameters field so they are applied automatically, for example
utm_source=facebook&utm_medium=paid_social&utm_campaign={{campaign.name}}. Check that your GA4 channel group maps that source and medium to Paid Social.
3. Ad blockers and consent block the GA4 tag
A shopper who blocks trackers, or declines cookies on your consent banner, still clicks the ad and still counts in Meta. GA4's browser tag either does not load or sends limited data. Consent mode modeling fills in some of this in GA4 reports, but not at the session or campaign level you need for comparisons.
Why Meta conversions don't match GA4 conversions
4. Meta credits ad views, GA4 only credits visits
Meta's default attribution setting is 7-day click and 1-day view. Any purchase within 7 days of a click, or 1 day of seeing an ad without clicking, is credited to that ad.
GA4 never sees ad views. It only knows about visits that reach your site. Its default model is data-driven attribution, which shares credit for a purchase across the channels that brought the shopper back. If a shopper clicks a Meta ad, then returns through a Google search, GA4 gives Google part or all of the credit. Meta gives itself all of it.
- Brand campaigns inflate the gap, because the people who see them often buy through search or direct anyway.
- Retargeting inflates it further. Shoppers who were already going to buy see an ad on the way, and Meta's view-through window credits the ad.
5. Meta models conversions it cannot see
Since Apple's App Tracking Transparency, Meta cannot observe every purchase from iOS users who opted out of tracking. It estimates them with statistical modeling and includes the estimate in Ads Manager. GA4 reports only what it recorded, plus its own separate modeling for consent.
As a result, part of the Meta number is an estimate with no matching event anywhere else. That is not a fault, but it means the two can never reconcile exactly.
6. Meta tracks across devices, GA4 mostly doesn't
People stay logged in to Facebook and Instagram on every device. Meta can connect an ad seen on a phone to a purchase made on a laptop the next day. GA4 can only join those visits if the shopper logs in to your store on both and you send a user ID.
7. The two platforms report on different dates
Meta reports a conversion on the date of the ad click or view. GA4 reports it on the date of the purchase. A shopper who clicks on Monday and buys on Thursday shows up on Monday in Ads Manager and on Thursday in GA4. Daily comparisons look worse than weekly ones for this reason.
Check time zones too. If your Meta ad account and GA4 property use different time zones, orders shift across days even when nothing else differs.
8. Purchases are counted twice, or not at all
This is the one cause that is purely a tracking fault, and the one worth fixing first.
- Meta Pixel plus Conversions API without deduplication. Sending purchases from the browser and the server is the recommended setup, but Meta can only remove the duplicate if both events share the same event ID. If they do not, every order counts twice.
- Two installs of the same pixel. A pixel pasted into the theme years ago, plus the Meta sales channel or an app, doubles purchases.
- Two GA4 tags. GA4 in Google Tag Manager plus the Shopify Google channel sends each purchase twice to the same property.
- The purchase event missing from some checkouts. Shopify's checkout runs tracking in a sandboxed pixel. A tag that was never moved to the new checkout stops recording purchases from it entirely.
To check, compare the purchase count in each platform with Shopify's online order count for the same week. A platform above Shopify is double counting. GA4 far below Shopify is missing purchases. The Littledata Tracking Audit lists every pixel on your storefront and flags duplicates.
How to compare GA4 and Meta Ads like for like
You will not get the numbers to match. You can get them close enough to trust the trend.
- Fix duplicates first. Each platform should record each Shopify order once.
- Tag every ad with UTM parameters so Meta traffic lands in Paid Social in GA4.
- Align time zones between the ad account, GA4 and Shopify.
- Compare Meta's 1-day click conversions (from the attribution setting comparison in Ads Manager) with GA4 Paid Social purchases on a last-click basis.
- Use a full week or more, never a single day.
- Compare order counts before revenue. Revenue adds definition differences, such as tax, shipping and currency, on top of tracking ones.
If the gap is stable from week to week, the tracking is sound and the difference is attribution. If the gap jumps, something on the storefront or checkout changed.
Where the Conversions API fits
The Meta Conversions API sends purchases to Meta from the server, so ad blockers, consent restrictions on the browser and in-app browser cookies do not stop the event. With hashed email, phone and address attached, Meta matches more of those purchases to the person who saw the ad. Meta shows this as Event Match Quality in Events Manager.
The Conversions API improves what Meta sees. It does not change what GA4 sees. If GA4 is still tracked only in the browser, adding the Conversions API can widen the gap between the two, because Meta now counts orders that GA4 still misses.
The data layer for Shopify closes that gap from both sides. It records each order once, server-side, with the shopper's original session and customer details attached, and sends the same record to GA4 and to Meta. That is what Littledata does for Meta and Google Analytics. The attribution differences remain, but they are the only difference left.
Frequently asked questions
Why does Meta Ads report more conversions than GA4?
Meta counts purchases after someone views an ad, not just clicks it, and credits any purchase within its attribution window (7-day click and 1-day view by default). It also models conversions it cannot observe directly. GA4 only sees visits that arrive on your site, and by default shares credit for a purchase across every channel that brought the shopper back.
Why does GA4 show fewer sessions than Meta's link clicks?
A link click is recorded when someone taps the ad. A GA4 session only starts once the page loads and the GA4 tag runs. Shoppers who leave during a slow load, browse with an ad blocker, or decline cookies are counted by Meta and not by GA4.
Should GA4 and Meta Ads ever match exactly?
No. They use different attribution models, windows and reporting dates, so some gap is expected. What you can check is that each platform records every purchase once, and that the gap stays stable from week to week. A sudden change in the gap usually means tracking broke.
How do I compare GA4 and Meta Ads conversions like for like?
Use UTM parameters on every Meta ad, set both platforms to the same time zone, and compare Meta's 1-day click conversions with GA4 purchases from the Paid Social channel on a last-click basis, over at least a week. Then compare order counts with Shopify rather than revenue.
Does the Meta Conversions API make Meta and GA4 match?
Not on its own. The Conversions API sends purchases to Meta from the server, so Meta sees orders the browser pixel missed. That narrows one gap and can widen the difference with GA4 if GA4 is still tracked only in the browser. Sending both platforms the same server-side order record is what brings them closer.
Why does GA4 attribute Meta ad sales to Direct?
Usually because the purchase happened outside the session the ad started. Shoppers who click in the Facebook or Instagram in-app browser and buy later in Safari or Chrome arrive with no campaign information, so GA4 records the visit as Direct.
The short version
GA4 and Meta Ads disagree by design: views versus visits, modeled versus observed, click date versus purchase date. Accept that part. Then make sure the rest is not a tracking fault, by checking that every platform records every Shopify order once.



