← Blog·Paid Media

Paid Media

Why Meta reports more or fewer conversions than GA4

Why Meta reports more or fewer conversions than GA4, what changed in Meta attribution in 2026, and how to find duplicates, blocked events, and lost UTMs.

David PombarSwiss army knife at Trackingplan
8 min read · 1729 words

Short answer Meta credits conversions to its own ads within the attribution setting of each ad set, view-through included if you chose it. GA4 credits the same conversions across every channel, from what it observes on your site. So Meta usually reports more, even with healthy tracking. When Meta reports fewer, you are usually comparing its attributed count with every purchase GA4 saw, under a click-through definition that since March 2026 counts link clicks only, or the Pixel isn’t reaching Meta. Align the settings first. If the gap is still larger than they explain, or it jumped on a specific day, look at Pixel and Conversions API deduplication, blocked or late events, UTMs, and consent.

Meta and GA4 answer different questions. Meta asks which conversions its ads can claim. GA4 asks which channel gets the credit for a conversion it saw. Expecting the same number is the first mistake.

Why Meta and GA4 disagree when tracking works

Meta counts by its attribution setting. With standard attribution, each ad set has an attribution setting: events within 1 or 7 days of a link click, within 1 day of an impression, or within 1 day of an engagement, such as a click that isn’t a link click or a video watched for 5 seconds. A purchase from someone who saw the ad and never clicked can count in Meta. GA4 never sees that link between them.

Each ad set can count differently. The setting is chosen per ad set, and Meta notes that results from ad sets with different attribution models can’t be compared directly in the campaign overview. Two ad sets, two rules, one total.

Incremental attribution is modeled. If an ad set uses incremental attribution, Meta reports conversions from models that predict whether a conversion was caused by an ad, not from a click-and-window rule.

GA4 shares the credit. GA4 assigns each key event to channels under its reporting attribution model, with a lookback window of 90 days by default for most key events. A Meta-driven purchase that ends with a branded search can land on paid search in GA4 and on the ad in Meta. Both are right by their own rules.

Consent changes what each one observes. GA4’s behavioral modeling for Consent Mode estimates users and sessions for visitors who decline analytics cookies, not event counts, and only with the Blended reporting identity. When a visitor declines, GA4 observes less of what they do. What Meta counts depends on the consent logic you apply to the Pixel and the Conversions API.

Why Meta can report fewer conversions than GA4

Meta reporting fewer conversions than GA4 is as normal as the opposite, and it has its own causes. The first four are about what you compare; the last three are about tracking.

You compare all purchases with attributed ones. GA4’s purchase count includes every channel. Meta’s count includes only the purchases it attributes to its ads. Compare Meta with GA4’s purchases from Meta traffic, not with the total.

Click-through now means link clicks. In March 2026 Meta changed click-through attribution for website and in-store conversions to exclusively include link clicks. Purchases after a like, a share, or a save moved to engage-through attribution, and a video counts as engaged after 5 seconds instead of 10. If your report reads click-through only, it shows fewer conversions than before, with no change in performance. Meta rolled it out over several weeks, so the date of the drop varies by account.

Short windows against a long lookback. A 1-day click setting, or no view-through at all, counts a narrow slice. GA4 looks back 90 days by default for most key events, so it can credit Meta with purchases that fall outside Meta’s own window.

Reports that lost the view windows. From 12 January 2026, Meta’s Ads Insights API no longer returns the 7-day view and 28-day view windows. A dashboard or connector that pulled them now shows fewer conversions, or none, for those columns.

The Pixel doesn’t reach Meta. A browser extension or privacy setting that blocks the Pixel sends Meta nothing. Without the Conversions API, those purchases never arrive; with it, they arrive only if the server sends them. A release that breaks the Purchase event cuts Meta’s count on a specific day while GA4’s stays flat. See why the Meta Pixel isn’t firing.

Consent gates Meta and GA4 differently. If your consent banner treats GA4 and Meta as separate vendors, a visitor who accepts analytics but declines advertising is counted by GA4 and not by Meta. That gap is expected; don’t close it by sending what the visitor declined.

Meta can’t match the purchase to a person. Meta attributes a conversion only when it can connect it to someone who saw or clicked the ad. Server events with few customer parameters, or a lost fbclid, match fewer people. See Meta Event Match Quality.

Align before you compare

In MetaIn GA4
The Purchase event and the ad sets you compareThe purchase key event, filtered to Meta traffic
The attribution setting of each ad setThe reporting attribution model and lookback window
Click-through only, if you can, to remove view-throughPaid social rows with your Meta UTMs
The same datesThe same dates and time zone

If you need one view, Meta itself suggests evaluating performance in your external analytics tool when you use one. If you need Meta’s view, read it with its attribution setting written next to the number.

When the gap is a tracking problem

The same purchase, counted twice. Most setups send a purchase from the browser Pixel and from the Conversions API. Meta keeps one only when the Pixel’s eventID matches the server’s event_id and the event names match, within 48 hours of the first event. Events sent from only one channel are never deduplicated, even when identical. A server that generates a new event_id, or none, doubles purchases in Meta while GA4 counts one. More on that in CAPI deduplication issues.

Late server events. Meta asks for Conversions API events in real time or within an hour, and warns that events sent 24 hours or more after they happened may have significant attribution issues. A batch job that sends yesterday’s orders at midnight changes what Meta can attribute.

Missing or broken UTMs. GA4 can only credit a Meta campaign it can read from the URL. Google recommends always setting utm_source, utm_medium, and utm_campaign, and missing UTM parameters show up as (not set). An ad without them, or with the wrong source, sends its conversions to another channel in GA4 while Meta still claims them.

Payment redirects. A buyer who returns from a payment provider can appear in GA4 as a referral from that provider, unless you list it as an unwanted referral. GA4 loses the Meta campaign; Meta keeps the conversion.

Different values. Meta receives the purchase value with tax and shipping, GA4 without, or the other way round. The counts match and ROAS doesn’t. Check value and currency for the same order in both.

Different consent logic. Meta recommends using the same consent logic for the Conversions API as for the Pixel. If the server sends events for visitors the browser tag respected, the gap is a compliance problem before it is a reporting one. Respect the visitor’s choice; never send what they declined to recover a conversion.

A five-step check

  1. Write down the definitions: the attribution setting of each ad set, GA4’s model and lookback window, the dates, the event.
  2. Compare click-through only where you can. If most of the gap is view-through, there is nothing to fix. If Meta is the one reporting fewer, compare its count with GA4’s purchases from Meta traffic, not with GA4’s total.
  3. Reconcile a sample against the backend. Take a day’s orders and check which ones reached Meta and GA4, and how many times. The backend confirms the order exists; it doesn’t decide who earned it.
  4. Inspect the purchase hits for those orders: browser and server copies, event_id, value, currency, UTMs on the landing, and the consent state.
  5. Line up the date of any jump with the releases, GTM versions, CMP changes, or server-side changes around it.

Where Trackingplan fits

Trackingplan doesn’t reconcile Meta’s attribution with GA4’s. It checks the signal both of them count. It watches the purchase hits your site and server send to Meta, GA4, and the other platforms, on real traffic, and compares Pixel, CAPI, and GA4 for the same purchase: counted once, with the same value, on every platform. Ask the agent why Meta shows more, or fewer, purchases than GA4 and it compares both counts for the same period, finds the cause, such as purchases sent twice after a change in the server-side container, and ends with the fix to ask for.

For the same question across Google Ads, Meta, and TikTok, see why GA4 and ad platforms report different conversions.

Frequently asked questions

Why is Meta reporting fewer conversions than GA4?

Usually because you are comparing a narrow Meta count with a broad GA4 one. Meta counts only conversions it attributes to its ads within each ad set’s attribution setting, and since March 2026 click-through counts only link clicks. GA4 counts every purchase it observes, from every channel, with a 90-day lookback. If the gap appeared on a specific day, check whether the Pixel or the Conversions API stopped sending purchases.

Why is Meta reporting more conversions than GA4?

Meta can credit a purchase to an ad seen or engaged with but not clicked, and it doesn’t share the credit with other channels. GA4 credits the same purchase to the channel its model picks. A larger gap than that usually comes from purchases sent twice by the Pixel and the Conversions API, or from missing UTMs.

Did Meta’s attribution change in 2026?

Yes. From March 2026, click-through attribution for website and in-store conversions counts only link clicks; conversions after likes, shares, or saves moved to engage-through attribution, and an engaged video view dropped from 10 to 5 seconds. Since 12 January 2026, the Ads Insights API no longer returns the 7-day view and 28-day view windows.

The gap between Meta and GA4 is permanent. The part of it your tracking adds doesn’t have to be.

David PombarSwiss army knife at Trackingplan

Read more from David, a Senior Product Strategist with 18+ years in digital product development and an atypical error detection knack.

Read next

All Blog →

Trackingplan

See everything. Miss nothing.

Your implementations audited around the clock with real-time, real-user data. Real-time alerts about errors or changes in your data, campaigns, pixels, privacy and consent. Let AI flag issues before they cost you.