Meta CAPI Event Value Does Not Match Pixel Value: What to Check
When the CAPI event value and the Pixel event value do not match, Meta receives two different numbers for the same purchase. The values diverge because the browser and server pull from different sources or calculate the value differently. The fix is to make both paths pull from the same source of truth.
Table of Contents
- 01.Two paths, two values
- 02.What to check first
- 03.Find where the values diverge
- 04.Tax, shipping and discounts
- 05.Currency mismatches
- 06.How to test it
Two paths, two values
The browser event and the server event both carry a value for the same purchase. If they pull that value from different places or apply different calculations, the values will not match. Meta then has inconsistent data for the same action, which can affect reporting and optimization.
| Path | Source | Risk |
|---|---|---|
| Browser event | Data layer on confirmation page | May exclude tax or shipping |
| Server event | Order data from the platform | May include the grand total |
| Both | Different sources | Values do not match |
What to check first
- Compare the value in a test order's browser event and server event.
- Identify where the browser value comes from, usually the data layer.
- Identify where the server value comes from, usually the order data.
- Confirm whether one includes tax, shipping or discounts and the other does not.
- Confirm the currency matches on both events.
Find where the values diverge
Trace the value on each path. The browser event typically pulls from a data layer variable on the confirmation page. The server event typically pulls from the order data the platform sends. If the data layer value is the subtotal and the server value is the grand total, the two will never match. Find the exact figure each path uses and compare them.
Tax, shipping and discounts
The same disagreement that causes wrong purchase values causes value mismatches between paths. If the browser value excludes tax and shipping and the server value includes them, the values differ. Decide on one definition for the purchase value, as covered in the guide on Meta Purchase value being wrong and apply it to both paths.
Currency mismatches
Even if the numeric value matches, a different currency code on each event makes the values effectively different to Meta. Confirm the currency sent on the browser event and the server event is the same and matches the order currency. This is especially important for multi-currency stores.
How to test it
- 1.Place a test order with a known total.
- 2.Capture the value and currency in the browser event.
- 3.Capture the value and currency in the server event.
- 4.Compare the two and identify which component differs.
- 5.Align both paths to the same value source and currency and re-test.
Frequently Asked Questions
Why does my CAPI value not match my Pixel value for the same order?
The two paths pull the value from different sources. The browser event usually reads the data layer, while the server event reads the order data. If one includes tax or shipping and the other does not, the values will not match.
Which value should I use, the browser value or the server value?
Use the same definition on both. Decide what the purchase value should represent for your business and make both the browser event and the server event pull that exact figure with the same currency.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Meta Purchase Value Is Wrong: How to Troubleshoot Value and Currency Tracking
A wrong purchase value is a definition and mapping problem, not a tag bug. Decide what the value should represent, confirm the tag pulls that exact figure and make the currency match.
Meta CAPI Purchase Events Missing: How to Trace the Server-Side Event Flow
A missing CAPI Purchase is a server-side flow problem. Confirm the order triggers the server logic, confirm the payload carries the order data and check the CAPI response.
Meta Browser Events and Server Events Do Not Match: How to Audit the Difference
Browser and server counts will not always be identical because the paths face different restrictions. Find unexpected differences, confirm event names and deduplication, then investigate.