A high-angle view of business charts with eyeglasses, smartphone, and pencil on a white background.
Photo by Yan Krukau on Pexels

Data Quality

Part of Ecommerce data quality

Detecting missing currencies and order values

Check purchase events for usable currency and value fields, distinguish genuine zeroes from missing data, and trace exceptions to orders.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Measurement.

Enable debug mode in the GA4 implementation and inspect purchase events in DebugView, which shows the events Analytics collects from a user in real time. For each purchase, check the event-level currency, value and transaction_id fields and inspect the items array, including each item's price and quantity.

Find incomplete purchase events

Google's Fix missing revenue data guidance says the purchase event must include the event-level currency and transaction_id parameters. If you set value, currency is required for revenue metrics to be computed accurately. For each event, record whether currency, value and transaction_id are present and non-empty.

Classify absent, empty, wrongly typed and unexpected fields separately. currency must be a string in the 3-letter ISO 4217 format, such as AUD. value must not contain a currency symbol; the dollar sign belongs nowhere in the payload, because the currency is carried by currency. A quoted amount such as "49.00" is a string and needs correction.

Compare currency with the order's checkout currency; treat a mismatch as unexpected. Check that value is usable as an amount, and compare it with the chosen order amount only after defining what that amount represents.

A zero value may reflect a legitimate transaction under the store's rules, so inspect the underlying order before calling it an error. Show the number of purchase events inspected alongside the number with unusable fields, and include incomplete purchases in the inspected total.

Verify purchase event completeness in GA4

  • Event-level `currency` present and non-empty
  • Event-level `value` present and non-zero
  • `transaction_id` present and unique
  • Items array includes `price` and `quantity` for each item
  • No currency symbol in `value` field

Purchase event validation metrics

  • Total purchase events inspected
  • Events with missing `currency`
  • Events with invalid `value` format
  • Events with empty `transaction_id`

Steps to validate ecommerce revenue data in GA4

  1. Enable DebugView in GA4
  2. Inspect each `purchase` event
  3. Verify `currency` is ISO 4217 code (e.g. AUD)
  4. Ensure `value` is numeric and without symbols
  5. Cross-check with Shopify order details

Compare amounts using the same definition

Choose the amount to compare before looking for mismatches. In Google's purchase example, value is the sum of price multiplied by quantity for all items. A commerce report may use another sales definition, so comparing event value directly with a tax-inclusive order total can create a false discrepancy.

Use transaction_id as the order identifier: it is the unique identifier of a transaction and helps avoid duplicate purchase events. Inspect the matching order's checkout currency, item amounts, discounts, tax and shipping alongside the sent payload. Check whether a blank mapping, a currency symbol inside value, or an amount from the wrong checkout stage explains the exception.

For multi-currency orders, keep the checkout currency with the original amount.

Match GA4 event `value` with order total using consistent definitions

  • GA4 `value` definition
  • Shopify Sales Report total
  • Discrepancy cause

Check item revenue separately

Google Analytics uses the purchase event's value and currency for event-level revenue metrics like Total revenue, and each item's price with currency for item-level metrics like Item revenue. If Total revenue is present and Item revenue is missing, or the reverse, inspect the corresponding part of the payload before changing a dashboard calculation.

After correcting a mapping, inspect an approved test event in DebugView and allow the report to process before assessing its totals. Mark the affected period. Do not silently replace missing historical payloads with estimates.

Further reading: Fix missing revenue data - Analytics Help (support.google.com).

More from Data Quality