Google Analytics 4 · Troubleshooting
GA4 shows purchases but no revenue: what to inspect
Diagnose a purchase event with missing revenue by checking values, currencies, item data, and the report you are using.
A purchase event name alone is not enough to describe revenue. Inspect the event’s monetary parameters and item data, then distinguish transaction-level revenue from item-level reporting before changing the implementation.
| What you see | Where to start |
|---|---|
| Purchase count, no value | Event-level monetary parameters |
| Revenue exists, item report is empty | Items array and product fields |
| Values look inflated | Unit, quantity, and transaction mapping |
Start with the event, not the chart
Google’s ecommerce specification uses event-level purchase data alongside an items array. Monetary values need the relevant currency, while item details carry their own attributes. Its missing-revenue guidance separates event-level and item-level problems because the reports do not all use the same inputs.
Use DebugView or your implementation’s debugging workflow to inspect a controlled purchase. Check the actual values being sent rather than assuming that a field named “total” in the store maps correctly to the analytics event.
Inspect the minimum useful evidence
- Confirm the event is the intended purchase event.
- Inspect the transaction reference, purchase value, and currency.
- Check that product details are sent in the items array with the relevant item identifiers, prices, and quantities.
- Compare those values with the test order.
- Recheck the appropriate report after processing.
For example, a monetary amount should not contain a currency symbol in place of the separate currency parameter. Follow Google’s current event specification when implementing the exact field names and formats.
A useful ecommerce test
Use an order with more than one unit of a product and a clear discount. That makes it easier to spot whether the implementation confuses unit price, line-item total, and transaction value. This is a diagnostic example, not a recommendation to change the store’s accounting treatment.
Agree on the revenue definition before comparing dashboards. A store total, an item revenue metric, and an advertising conversion value can differ for reasons that go beyond a broken tag. The goal is an explained comparison, not forcing every visible number to match.
Fix the producer of the bad data
If the wrong value comes from an ecommerce integration, correct its mapping or configuration there. Adding a second purchase event can create another issue without repairing the first. Keep a record of the event owner, expected values, and test order so a later theme or checkout update can be checked against the same example.
EP4P uses sales measurement to decide where advertising money should go. Reliable purchase values matter more than a dashboard that merely reports a plausible-looking ROAS.
Sources and implementation references
Sources checked November 9, 2026. Platform interfaces and policies can change; use the current notice and documentation for your implementation.
Let our team handle the marketing.
You do not have to become the tracking department. EP4P connects purchase measurement, reporting, and the campaign decisions that depend on them.
We build, fund, and manage your campaigns. You pay an agreed percentage only on ecommerce sales directly tracked to clicks on our ads. Our work and the ad spend are included. No monthly retainer or setup fee.