Why is Meta Ads purchase value missing or wrong?

Quick answer: Meta can count a purchase without receiving the right revenue value

If Meta Ads shows purchases but purchase value is missing, zero, duplicated, or lower than your ecommerce platform, the conversion event is not passing trustworthy revenue data. Meta may know that a purchase happened while losing the value, currency, order status, or deduplication details needed to report revenue correctly.

Do not optimize from ROAS until the value signal is reliable. Diagnose the event payload, Pixel and Conversions API setup, checkout path, refunds or cancellations, and the source-of-truth report you are comparing against.

The causes to check first

Missing or wrong purchase value usually comes from a few repeatable tracking and reporting issues. Work through these before rebuilding campaigns or changing the ROAS target:

• The purchase event is firing without value or currency parameters, so Meta records the conversion but cannot calculate revenue correctly.
• Pixel and Conversions API events are not deduplicating, which can double-count purchases or keep the wrong version of the event.
• Checkout apps, payment redirects, subscriptions, upsells, or post-purchase pages send different order totals than the ecommerce backend.
• Currency, tax, shipping, discounts, or bundle logic differs between Meta, Shopify, the CRM, and finance reporting.
• Refunded, cancelled, failed, or test orders are included in one report but removed from another.
• Campaigns optimize against the wrong dataset, Pixel, domain, or custom event, so the value signal does not match the live purchase flow.

How to diagnose whether the issue is tracking or reporting

Start with a small set of real orders from the same date range. Compare order ID, purchase timestamp, subtotal, discounts, taxes, shipping, currency, customer status, and final payment state across Meta Events Manager, browser Pixel events, server-side CAPI logs, ecommerce orders, and your analytics tool.

Then test the exact checkout path that customers use. A direct card payment, PayPal redirect, subscription checkout, one-click upsell, or delayed payment confirmation can each create a different event sequence. The goal is to find whether Meta receives no value, the wrong value, or the right value at the wrong time.

• Use Meta test events to confirm the purchase payload includes value, currency, event ID, content IDs, and event source URL.
• Check whether browser and server events share the same event ID so Meta keeps one clean purchase instead of two conflicting records.
• Compare gross revenue, net revenue, discounts, taxes, shipping, and refunds before saying Meta is wrong.
• Segment the mismatch by payment method, device, country, product type, subscription status, and checkout app.
• Look for site releases, app installs, tag-manager edits, consent changes, or checkout updates that happened before value reporting changed.

What to fix before trusting ROAS again

Fix the measurement layer before making budget decisions from purchase value. Pass a consistent value and currency on every confirmed purchase, deduplicate Pixel and CAPI with a shared event ID, align the value definition to your reporting goal, and exclude test or failed orders from performance analysis.

Also decide what revenue number the team should optimize toward. Some ecommerce teams want gross order value in Meta for bidding, then use finance reports for margin. Others need net revenue or subscription-adjusted value for decision-making. The important part is that everyone knows which definition Meta is receiving.

• Repair missing value and currency parameters in the purchase event payload.
• Validate CAPI and Pixel deduplication before comparing ROAS week over week.
• Document whether Meta value includes discounts, taxes, shipping, refunds, and subscription adjustments.
• Audit every checkout path, not only the default desktop purchase flow.
• Pause major scaling decisions until purchase value matches the source of truth closely enough to guide optimization.

How an AdSpecIt-style audit helps diagnose purchase value gaps

A useful audit should connect conversion tracking, value parameters, Pixel/CAPI deduplication, ecommerce order data, attribution settings, and business reporting instead of stopping at platform ROAS. It should show whether Meta is missing revenue, overcounting events, using the wrong dataset, or comparing against a different revenue definition.

That turns “purchase value is wrong” into a practical fix list: repair event parameters, align value definitions, validate checkout paths, clean up deduplication, reconcile source-of-truth orders, and only then use ROAS to decide which campaigns deserve more spend.