GA4 Purchase Revenue Is Wrong: How to Troubleshoot Value and Currency
When GA4 purchase revenue is wrong, the purchase event fires but the value or currency is incorrect. The event reaches GA4, so the tracking flow works, but the number is off. The problem is in how the order total is calculated and passed from the store through the data layer to the GA4 event. Find where the value changes unexpectedly.
Table of Contents
- 01.Where the value can change
- 02.What to check first
- 03.Define what the purchase value should be
- 04.Tax, shipping and discounts
- 05.The data layer value field
- 06.The GTM variable mapping
- 07.Currency and formatting
- 08.How to test it
Where the value can change
The purchase value travels from the store order total through the data layer and a GTM variable into the GA4 purchase event. The value can change at any step. The store calculates the order total one way, the data layer may store a different figure, the GTM variable may read the wrong field, and the GA4 event sends whatever it receives. A wrong revenue value means one of these steps passed a different number than you expected.
| Step | What holds the value | Where it can go wrong |
|---|---|---|
| Store order total | Backend calculates the total | Tax, shipping or discount included or excluded differently |
| Data layer | value field in the purchase object | Wrong field or stale value |
| GTM variable | Variable reads the value | Variable maps the wrong data layer field |
| GA4 event | value parameter in the request | Value not sent or sent as text |
| GA4 revenue | Reported revenue in GA4 | Currency mismatch changes the figure |
What to check first
- Complete a test order and note the exact order total in the store backend.
- Inspect the data layer value field on the confirmation page.
- Confirm the GTM variable reads the correct data layer field.
- Check the value and currency parameters in the GA4 request.
- Compare the GA4 reported revenue against the store order total.
Define what the purchase value should be
Before you troubleshoot, decide what the purchase value should represent. Some businesses want the product total, others want the order total including tax and shipping, others want it after discounts. GA4 records whatever value you send. There is no single correct definition. The problem is when the value GA4 receives does not match the definition you intended. Confirm your intended definition first, then check whether each step passes that same figure.
Tax, shipping and discounts
The most common value mismatch comes from tax, shipping and discounts being included or excluded differently. The store backend may show the order total including tax, while the data layer value field holds the product total excluding tax. Or a discount applied at checkout may not be reflected in the value pushed to the data layer. Compare the store order total against the data layer value and identify which components are included in each. The difference is usually here, not in the tag.
The data layer value field
Inspect the data layer on the confirmation page and find the value field in the purchase object. This is the number the GA4 tag will send. If this field already holds the wrong figure, the tag is not the problem, the data layer is. Confirm the value field matches your intended definition. A data layer value that excludes shipping when you want the full order total is a data layer issue, not a GA4 issue.
The GTM variable mapping
If the data layer value is correct but GA4 receives the wrong number, the GTM variable may be reading the wrong field. The variable has to point at the correct data layer path for the value. A variable that reads a different field, like the product price instead of the order total, sends the wrong value. Check the variable configuration in GTM and confirm it reads the value field you inspected. The data layer structure is covered in the guide on GA4 ecommerce data layer not working.
Currency and formatting
A wrong currency can make the value look wrong even when the number is correct. Confirm the currency parameter in the purchase event matches the store currency. Also check that the value is sent as a number, not as text with a currency symbol. A value sent as a string with a symbol can be recorded incorrectly or rejected. The value and currency have to be clean numbers and a valid currency code.
How to test it
- 1.Complete a test order and record the exact store order total.
- 2.Inspect the data layer value field and compare it to the store total.
- 3.Confirm the GTM variable reads that value field.
- 4.Check the value and currency in the GA4 request in GTM preview.
- 5.Compare the GA4 reported revenue to the store total and explain any difference.
Frequently Asked Questions
Why is my GA4 purchase revenue different from my store order total?
The value sent to GA4 may include or exclude tax, shipping or discounts differently than the store total. Compare the data layer value field to the store total to find which components differ.
Should GA4 purchase value include tax and shipping?
There is no single correct answer. GA4 records whatever value you send. Decide what the value should represent and ensure each step in the flow passes that same figure consistently.
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
GA4 Product Name, ID, Price or Quantity Is Wrong: How to Audit Ecommerce Parameters
When the items array exists but specific values are wrong, build a field-by-field audit. Compare each field against the page and trace the wrong value to its source in the data layer or tag variable.
GA4 Ecommerce Revenue Does Not Match Store Revenue: Why the Numbers Can Differ
GA4 revenue and store revenue will not always be identical. Reconcile the two by separating missing purchases, duplicate purchases and value definition differences before treating a gap as a tracking error.
GA4 Ecommerce Data Layer Not Working: How to Find the Problem
The data layer is the foundation under every GA4 ecommerce event. If the push is missing, mistimed or malformed, no tag configuration can recover the data. Find where the data stops.