- Meta and GA4 use different attribution rules, so totals will differ.
- Meta can count people who saw an ad but never clicked.
- UTM tags make Meta traffic visible and comparable in GA4.
- Judge direction and trend; use lift tests for the real answer.
How do Meta attribution windows work?
Meta reports a conversion when someone takes an action within a set period after interacting with your ad. The common default is 7-day click and 1-day view. If a person clicks your ad on Monday and buys on Friday, Meta counts it. If they only see the ad and buy the same day, Meta also counts it as a view-through conversion.
Meta has narrowed what counts as a click. In 2026 it began limiting click-through attribution for website conversions to link clicks, and moved conversions after likes, shares or saves into a separate engage-through measure. Longer view windows have also been removed from reporting. Rollouts vary by account, so check the attribution setting in your own Ads Manager columns before comparing anything.
How does GA4 attribute conversions?
GA4 only knows about sessions it can track on your site. It assigns credit for a key event using its own attribution model, usually data-driven by default, across every channel: Google search, email, direct visits and Meta. If someone clicks a Meta ad, leaves, and later returns through a Google search, GA4 may credit Google while Meta credits itself.
GA4 also misses visits it cannot record. Ad blockers, declined cookie consent, in-app browsers and cross-device journeys all create gaps. Meta, meanwhile, can match conversions using its own logged-in data and the Conversions API, so it sees some purchases GA4 never connects to a Meta visit. Neither tool is lying; each sees a different part of the journey.
Where the numbers diverge
Most of the gap comes from a few predictable differences.
Difference | Meta Ads Manager | GA4 |
|---|---|---|
Views without clicks | Can count a 1-day view conversion | Cannot see ad impressions |
Credit across channels | Counts its own touch, regardless of others | Shares or assigns credit across all channels |
Reporting date | Usually the date of the ad interaction | The date the conversion happened |
Tracking source | Pixel plus Conversions API and Meta's own matching | Site tag, limited by consent and blockers |
Modelled conversions | May include modelled results | May include modelled data under consent mode |
What are view-through conversions?
A view-through conversion is a purchase or lead from someone who saw your ad, did not click it, and converted within the view window. Some of these people were genuinely influenced. Others would have bought anyway, for example loyal customers who see an ad while scrolling the morning they had already planned to order.
View-through is why Meta totals often look higher than GA4. It is not wrong, but it is generous. You can switch your reporting columns to click-only attribution to see a stricter number, and compare the two. If most reported conversions are view-through, ask how many of those buyers were already customers.
How should I set up UTM tags?
Consistent tags make Meta traffic readable in GA4.
- Use URL parameters at ad levelAdd utm_source, utm_medium and utm_campaign in the ad's URL parameters field so every link carries them.
- Use Meta's dynamic valuesDynamic parameters can fill in campaign, ad set and ad names automatically.
- Keep naming consistentPick lowercase names such as facebook or instagram and paid_social, and never change them mid-month.
- Tag every destinationInclude website, landing pages and links in Instant Form thank-you screens.
- Check in GA4Look at the traffic acquisition report after launch to confirm sessions are arriving with the right tags.
Which numbers should I trust for decisions?
Use each tool for what it does well. Meta's numbers are the best guide for comparing campaigns, ad sets and ads with each other, because they use the same rules throughout. GA4 is better for seeing how Meta fits beside other channels and what visitors do on the site. Keep the comparison within one tool where possible.
For the overall question of whether Meta is paying for itself, look at your real sales or CRM data over time against your spend. If total revenue rises when Meta spend rises and holds when it is cut, that tells you more than either dashboard. For a stricter answer, run a test, as explained in how to know if Meta ads are causing sales.
Common tracking mistakes
These make the gap wider than it needs to be.
Pixel firing twice
Duplicate purchase events inflate Meta results. Deduplicate browser and server events with a shared event ID.
No Conversions API
Browser-only tracking loses events. Our guide on whether you need the Conversions API explains why.
Missing UTM tags
Meta visits show up as referral or direct traffic in GA4.
Comparing different windows
Comparing Meta's 7-day click with GA4's last click on a different date range will never match.
Unverified event setup
Events sent from the wrong domain or with missing values distort reporting.
How we handle this for clients
We audit tracking on both sides before discussing any numbers. On Meta, we check the pixel, the Conversions API, deduplication and which attribution setting each column uses. On GA4, we check key events, consent behaviour and whether Meta traffic carries clean UTM tags. Where sales close offline, we also check how confirmed orders or qualified leads are recorded, because that is usually the most reliable number of all.
We then agree with the client which source answers which question, and write that down so monthly reviews do not become a debate about whose dashboard is right. Set-up and repairs fall under our Meta Pixel and Conversions API setup service, part of our wider Meta Ads management work. That agreement saves time every month.
Pakistan, Gulf and UK advertisers
In Pakistan, many orders are placed through WhatsApp or confirmed by phone, and cash on delivery orders can be cancelled after the website records them. Neither Meta nor GA4 sees that reality unless you send confirmed orders back as offline or CRM events. Compare dashboards against delivered orders, not checkout events.
In the UK and parts of the EU audience, cookie consent banners reduce what GA4 records, so the gap with Meta is often wider. In the Gulf, cross-border shopping and multiple currencies can confuse revenue reporting. Make sure your purchase event sends the correct currency code for each store. Check this before blaming either tool.

