The short version: Meta Ads Manager will tell you it drove far more revenue than your bank deposited. That isn't a glitch — it's how every ad platform counts. Admaxxer cross-checks Meta three ways so you always know the real number: server-side conversions with strong match quality, side-by-side reconciliation against your own pixel and store, and incrementality testing that proves what your ads truly caused. All three are included on every plan.
An ad platform is grading its own homework. It has three structural reasons to inflate the revenue it claims, and none of them are dishonest — they're just optimistic by design:
The fix isn't to distrust Meta — it's to triangulate. Admaxxer holds three independent views of every sale and shows them together, so you can see exactly where the platform's number is real and where it's optimistic. The next three sections are those three views.
The single biggest lever on Meta attribution accuracy is the quality of the data you send Meta in the first place. Get this right and every downstream number improves — including Meta's own optimization.
Event Match Quality (EMQ) is the score Meta gives each conversion you send server-side. It measures one thing: how confidently Meta can match the buyer to a real person on their side. The richer the customer details attached to a purchase — email, phone, name, location — the higher the score, the more sales Meta credits to the right ad, and the smarter its delivery gets. Admaxxer forwards every identifier your checkout collects, hashed and privacy-safe, so your job is simply to make sure your checkout is collecting them.
In Meta's Events Manager, each event source carries an Event Match Quality rating from Poor to Great (Meta shows it on a 0–10 scale; 8.0+ reads as Great). It is not a measure of how many sales you made — it is a measure of how well Meta can tie each sale back to a person. Higher match quality means more of your true conversions get attributed and fed back into Meta's optimization.
Example. Two stores each sent Meta 1,000 purchases. Store A only sent an email; Store B sent email + phone + name + zip. Meta matched 71% of Store A's purchases and 94% of Store B's — so Store B's ROAS looks higher and its campaigns learn faster, on the exact same sales.
Why server-side delivery beats the browser pixel alone: iOS App Tracking Transparency, Safari's tracking prevention, and ad blockers quietly drop a large share of browser-only conversions. Admaxxer sends every purchase a second way — server-side, with the same de-duplication ID — so Meta still receives it even when the browser pixel was blocked. This is what typically recovers 20–40% of conversions that would otherwise vanish, and it's included on every plan. See the server-side conversions setup guide for the one-toggle walkthrough.
Admaxxer shows three independent numbers for every channel, campaign, ad set, and ad — never one figure that hides the disagreement. When the platform's claim runs ahead of reality, you see exactly by how much and why.
Worked example. Meta reports $11,400 from a campaign. Your pixel followed real clicks worth $4,100, and your store ledger banked $4,600 attributable to it. The $6,800 gap is mostly view-through and modeled credit Meta claimed — real awareness, but not dollars you can bank twice.
Why three numbers, not one. Admaxxer never collapses these into a single figure that hides the disagreement. Instead it shows all three per channel — down to the individual campaign, ad set, and ad — and a plain-English note on every row explaining the gap ("platform claims more than pixel — likely view-through behind iOS" or "within 10% — clean"). You decide which lens answers your question: pixel for what you can defend, store ledger for cash, platform for reach.
The marquee number — True ROAS. Because Admaxxer holds both your real spend and your store's banked revenue, it computes the one number neither the platform nor your store can show alone: True ROAS — the revenue your store actually recorded for a campaign divided by what you actually spent on it. The platform can't compute it (it never sees your spend the way you do, and it divides its own inflated revenue); your store can't compute it (it never sees ad spend). Admaxxer ships it on every plan.
For the full lens-by-lens breakdown — including how the store's order journey is stitched and how the synthesis lens picks the best source per cell — see the Sources & Attribution deep-dive and Attribution Models.
Attribution answers "which ad got the click that led to the sale?" Incrementality answers a harder, more valuable question: "how many of those sales would have happened anyway, even if I had run no ads at all?" A loyal customer who was going to buy this week might click your ad on the way in — attribution credits the ad, but you didn't actually cause that sale. Incrementality measures the sales you truly caused. It's the difference between "what happened" and "what I made happen."
Even a perfect attribution model can over-credit ads, because some buyers would have purchased without ever seeing one. Incrementality strips that out by measuring the lift your ads add on top of what would have happened anyway. It's the only way to know whether scaling a campaign will grow your business or just pay to reach people who were already coming.
Pick a region to keep advertising in (the test region) and a set of comparable regions to use as a baseline. Admaxxer builds a synthetic "twin" of your test region from the baseline regions — one that tracked your revenue almost perfectly before the test. During the test, the gap between your real test region and its synthetic twin is the lift your ads actually caused. No twin store to set up, no engineering — you choose the regions and the dates.
Worked example. You keep ads on in the West and use the Midwest and Northeast as the baseline. Before the test the synthetic twin tracks West revenue within 1%. During a 28-day test the West runs $40k ahead of its twin — that $40k is incremental revenue your ads caused, not just revenue they took credit for.
Every result comes with a confidence read so you don't act on a fluke. Admaxxer reports the lift percentage, a significance score (a p-value — below 0.05 means the lift is very unlikely to be random chance), and a range showing the realistic best and worst case. A clearly significant positive lift is your green light to scale; a result indistinguishable from zero tells you the spend isn't moving the needle.
Attribution is your daily steering wheel — fast, granular, per-ad. Incrementality is the periodic gut-check that keeps the steering honest — slower, causal, per-channel. Run attribution every day to allocate budget, and run a geo-lift test each quarter (or before a big scale-up) to confirm the channel is genuinely growing the business. Admaxxer ships both, included, so you never have to choose. The full method and a step-by-step setup live in the Incrementality Testing guide.
Each pillar answers a different question, and together they give you a number you can defend at every altitude:
Use attribution every day to allocate budget. Use reconciliation to sanity-check the platform's claim. Use incrementality before a big scale-up. Admaxxer ships all three — included on every plan, no enterprise quote required.
Q: Why does Meta report more revenue than my pixel or my store?
Because Meta grades its own homework. It counts view-through conversions (someone who saw your ad but never clicked), it models conversions it can't directly observe, and it claims full credit even when other channels also touched the buyer. Your first-party pixel counts only real clicks and your store ledger counts only banked orders — so both are lower and closer to reality. Admaxxer shows all three side by side with a plain-English note on every row explaining the gap.
Q: What is Event Match Quality (EMQ) and how do I raise it?
EMQ is Meta's score for how confidently it can match each conversion you send to a real person — not how many sales you made. You raise it by attaching more customer details to each purchase: email (the biggest lever), phone number (the fastest win, since most stores leave it off), and name plus city/state/zip. Admaxxer forwards everything your checkout collects, hashed and privacy-safe, automatically. If your score is yellow, the usual fix is enabling phone capture at checkout — scores typically climb to green within 24–48 hours.
Q: Will adding phone and other fields expose my customers' personal data?
No. Admaxxer hashes every identifier — email, phone, name, address — inside the browser before it is ever sent, so the raw value never leaves in plain text. Meta receives only the irreversible hash, which it uses to find a match on its side. This is the standard privacy-safe method for server-side conversions and is what lets you raise match quality without sharing readable personal data.
Q: Which number should I trust — pixel, store, or platform?
It depends on the question. Use your first-party pixel for the number you can defend to a CFO (real clicks only, conservative). Use your store's order ledger for actual banked cash. Use the platform's claim to understand reach and to feed the platform's own optimization. Admaxxer's marquee number, True ROAS, divides your store's banked revenue by your real ad spend — the honest efficiency figure neither the platform nor your store can compute on its own.
Q: What is incrementality and how is it different from attribution?
Attribution asks "which ad got the click that led to this sale?" Incrementality asks "how many of these sales would have happened even with no ads at all?" Some buyers were always going to purchase; crediting an ad they happened to click overstates the ad's true value. Incrementality measures only the lift your ads actually caused. Run attribution daily to steer budget; run an incrementality test before a big scale-up to confirm the channel is really growing your business.
Q: How does a geo-lift test work, and do I need to set anything up?
You pick a region to keep advertising in and a set of comparable regions as a baseline. Admaxxer builds a synthetic "twin" of your test region from the baseline regions — one that matched your revenue closely before the test — and the gap between your real region and its twin during the test is the lift your ads caused. There's no twin store to build and no engineering: you choose the regions and the dates, and Admaxxer reports the lift with a confidence score so you know whether it's real.
Q: Does server-side tracking really recover lost sales?
Yes. iOS App Tracking Transparency, Safari's tracking prevention, and ad blockers silently drop a large share of browser-only conversions. Admaxxer sends every purchase a second way — server-side, tagged with the same de-duplication ID so nothing double-counts — meaning Meta still receives the sale even when the browser pixel was blocked. This typically recovers 20–40% of otherwise-lost conversions and is included on every plan.
Q: Do I need to connect my ad accounts to see any of this?
No — Admaxxer is source-additive. With just the pixel installed you get conservative, click-based attribution from day one. Add your store connection and you unlock pixel-vs-store reconciliation. Add Meta and you unlock platform-vs-pixel comparison and EMQ visibility. Each source you connect adds a lens; nothing is gated behind connecting everything first.
Connect Meta with a paste-token in about two minutes, turn on server-side conversions, and watch your three-source reconciliation populate. No App Review, no implementation fee.
Sources & Attribution (3-lens drill-down) · Attribution Models · Server-side conversions setup · Incrementality Testing · Tracking Health · Connect Meta Ads (paste-token) · Documentation home