Meta Can't See Half Your Sales. So It Can't Find Your Buyers.
Meta reports fewer purchases than you know your ads drive. Missing signal is why. TrueROAS captures conversions server-side, matches them to Shopify orders and sends them back to Meta so the algorithm learns again.
Tracks every major ad platform. Sends verified orders back to Meta and Google.
Sound familiar?
What you are probably seeing
Purchases in Ads Manager are far below Shopify orders you know came from ads
Cost per purchase looks worse than your unit economics suggest
Campaigns stay stuck in 'learning' or exit learning and stall
Post-purchase survey says 'Facebook' or 'Instagram' far more often than Meta reports
Why it happens
This is not a bug. It is how the platforms are built.
iOS App Tracking Transparency
Most iPhone users opt out of tracking. Meta loses the link between the click in the app and the purchase in Safari.
Browser tracking prevention and ad blockers
Safari caps pixel cookies at 7 days (24 hours in some cases). Ad blockers stop the pixel from loading at all on a meaningful share of desktop traffic.
Cross-device journeys
Click on a phone, buy on a laptop. Without a persistent server-side identifier the two events never meet.
Weak Conversions API setup
Many CAPI installs send events without the match keys (email, phone, external ID, click ID) that Meta needs to attribute them. Meta receives the event and discards it.
What it costs you
Meta's delivery system optimises toward the purchases it can see. When it sees half of them, it learns from a biased sample and bids for the wrong people. You pay more per real customer and turn off ads that were working.
How TrueROAS fixes it
Start from the order, not from the ad platform
Server-side tracking that survives iOS and ad blockers
TrueROAS records clicks and orders on your own domain, first-party, so Safari limits and blockers do not delete the trail.
Order-level matching
Each order is linked to its click with a persistent identifier, including across devices when the customer is identifiable at checkout.
Enriched conversions sent back to Meta
Every verified order is sent to Meta's Conversions API with the full set of match keys and order value. Meta's Event Match Quality rises and the algorithm gets the signal it lost.
Survey data fills the rest
A post-purchase survey catches the journeys no tracking can, like the ad someone saw but never clicked. TrueROAS cross-checks it against the tracked data instead of treating it as gospel.
Others track. We triangulate.
Tracking alone drops sales to iOS, ad blockers and dead cookies. Three signals catch every one.
Tracking
Surveys
AI MMM
How it works: three signals cross-check every sale.
Other tools: 1 bucket
Sales lost
Tracking
1 bucket → most sales missed.
TrueROAS: 3 buckets
Order-verified
Tracking
Surveys
AI MMM
3 buckets → far fewer sales lost.
Ask your data anything.
One trusted source of truth, wired into the AI you already use.
TrueROAS
data layer
Claude
ChatGPT
Cursor
MCP
“Which ad should I scale?”
"Meta said 1.5 ROAS. TrueROAS showed 4.5. I almost turned off a winner."
"Very good app. I almost turned off an ad set that had a 4.5 ROAS because Meta tracked not all of the sales and had a Meta 1.5 ROAS."
LederKur
Shopify store, Germany. Verified review
When you do not need this
If you already run a well-configured Conversions API with high Event Match Quality and most of your traffic is on Android or desktop Chrome, your gap may be small. Compare Ads Manager purchases to your survey results before paying for anything.
Questions media buyers ask
Straight answers
Is the Conversions API enough on its own?
It is necessary but not sufficient. CAPI only helps if the events carry strong match keys and are de-duplicated against the pixel. It also does nothing about credit being split between Meta, Google and email. TrueROAS handles both the sending and the attribution.
How fast does Meta pick up the extra signal?
Events arrive within minutes. The delivery system typically needs a few days of consistent, higher-volume conversion data before you see it in cost per purchase. Most stores see the change in Event Match Quality first, then in performance.
Does this work with Shopify's native Meta integration?
Yes. TrueROAS runs alongside it and de-duplicates by event ID so purchases are not double-counted.
Go deeper
Understand why this happens
Five-minute lessons, written by the founder, no jargon.
Related