Skip to content
All field notes
Measurement
Published
Oct 30, 2026
Updated
Nov 3, 2026
Reading time
11 min read

GA4 Purchases but Zero Revenue? Audit Values and Item Scope

Diagnose GA4 purchase events with missing or incorrect revenue by checking event names, numeric values, currency, item prices and comparable order totals.

AP
AdProof Research
Independent measurement desk
A purchase receipt separates into an order-value ledger and item-price cards, with a magnifying glass checking an empty currency field.
A recorded purchase, event value and item revenue need separate payload and reporting checks. Conceptual illustration without store results.
In this guide (9 sections)

When GA4 records purchase activity but revenue is zero or wrong, inspect the actual event name and monetary parameters before changing attribution or adding another purchase tag. Confirm that the event sent is purchase, its event-level value is numeric, its event-level currency identifies the transaction currency, and each item has the intended unit price and quantity. Then compare the exact revenue metric with an order total using the same definition.

A firing tag proves less than a correct monetary event. A purchase count, Event value, Item revenue and Total revenue can disagree because they use different fields or include different populations.

An older ticketing-platform question reports item revenue but zero purchase conversion value. Another advertiser reports Event value with zero Total revenue while using a custom event name. These are verified evergreen problems, not evidence of a new GA4 incident. Their replies suggest checks; the diagnostic below follows current Google references and verifies each boundary separately.

Name the metric and freeze one accepted order#

Start with one authorized test order or a restricted business record. Record its accepted status, merchandise value after discounts, tax, shipping, currency, effective time and nonidentifying order reference. A checkout attempt or thank-you-page visit is not sufficient proof of a completed business transaction.

Save the property, stream, date range, timezone, report filters and extraction time. State whether the reference contains orders made during the period or a different financial population. A bank settlement can include fees, timing differences or other adjustments that are outside a purchase event's merchandise value.

MetricWhat you are inspectingWhy another total may differ
Event countRecorded occurrences of the selected eventDoes not validate monetary fields
Event valueSum of the event parameter named valueA custom event's value is not automatically ecommerce revenue
Ecommerce purchasesCompleted purchase eventsDifferent unit from item quantities
Gross purchase revenuePurchase-side revenue before refund subtractionDifferent population from all monetary event values
Gross item revenueItem unit prices multiplied by quantitiesExcludes tax and shipping
Total revenueRevenue from the relevant purchase, subscription and advertising sources, after applicable refundsBroader than one web purchase cohort

Google's Data API metric schema defines these separately. Use gross measures for a purchase-side investigation where you intentionally exclude refunds, then reconcile later changes separately. Do not turn this into another refund or duplicate-transaction investigation unless the evidence points there.

Related guide

Trace the purchase values to GA4

Record the event name, value, currency and item fields for one accepted order.

Use the tracking QA checklist

Opens a practical guide. No email required.

Confirm the event name, not just its key-event status#

The emitted name needs to match the recommended ecommerce event. A tag called “Purchase” in GTM can send an event called purchase-test; the friendly tag name does not establish the destination event name.

Google's ecommerce validation guide explains that incorrect event names or missing required parameters can prevent ecommerce interpretation even when an event is visible. Marking a custom event as a key event does not fill in its missing ecommerce structure.

The custom-name discussion includes advice to use purchase. Use the current event contract and test your own implementation rather than treating an older reply as proof of the cause in your property. Its legacy menu instructions are not a current setup specification.

For a purchase derived from a pageview rule, verify where the order fields come from. Renaming a thank-you-page view cannot conjure an order amount or item array. A separate question about ecommerce capture without GTM reflects that confusion. GTM is one implementation route; the site or integration still needs to supply the business data.

Check the event-level value and currency together#

Inspect the emitted payload for the selected order. Google's missing-revenue guide distinguishes event-level revenue, calculated using value and currency, from item-level revenue, which needs the relevant item fields. If order revenue is present but product rows split across shopping steps, reconcile item identity, variant mapping and report grain across events. A populated monetary field does not establish a consistent product key.

For event-level reporting, verify:

  • value is a number, not a formatted display string.
  • currency is a string containing the intended three-letter ISO 4217 code.
  • Both fields are at the event level with the correct lowercase names.
  • The value represents the intended merchandise amount, rather than a default, stale cart total or payment attempt.

For example, numeric 105 and currency USD are separate fields. A value containing a currency symbol, thousands separator or localized display formatting needs investigation before it is used as the monetary parameter. Do not “fix” that by blindly replacing punctuation: establish how the source represents numbers and what the integration actually emits.

A Stack Overflow question about visible purchase values but no revenue includes an incomplete monetary payload. The current official parameter contract, rather than an old answer's formatting shortcut, should govern the repair.

Trace the mapping all the way to the outgoing event#

Use a small receipt with one row per checkpoint: accepted business order, application or data-layer event, tag mapping, outgoing request, receiving diagnostic and processed report. At each checkpoint retain the event name, destination, value, currency and item totals.

A field can exist in the application object yet never reach GA4. It can be nested under a different path from the one a GTM variable reads. A tag may read the previous cart state or replace a missing value with zero. Compare actual values at the selected event time rather than inspecting variable definitions in isolation.

Google's ecommerce implementation guide shows event-level currency and mappings for ecommerce fields. If using GTM, compare both the site's data layer and the tag's event parameters. If a plugin or backend owns the send, ask that owner for the same evidence instead of introducing a second sender.

Keep consent and collection coverage visible. A corrected monetary mapping does not explain an order whose event was never collected. Use the marketing tracking QA checklist to test the authorized success path and relevant failure paths.

Keep item prices inside the items array#

For each item, inspect its identity, numeric unit price and quantity. The purchase event reference specifies items as an array, requires an item ID or name, and describes price and quantity at item scope. Quantity defaults to one if not supplied, so omitted quantities can conceal a multi-unit order.

An item-level currency field is not a substitute for the event-level transaction currency required when sending value. Check the event currency and item monetary values as one coherent transaction; do not combine different currencies in a single merchandise sum.

The Help Center missing-revenue checklist contains an inconsistent “event-level price” bullet, but its detailed price subsection and the developer schema place price on the item. Follow that corroborated item scope rather than inventing a top-level price field to satisfy the checklist wording.

Inspect every array entry, not only the first product. A truncated array, missing quantity or line total mistakenly sent as unit price can produce plausible but wrong item revenue. Preserve item evidence separately from the order-level value; one field should not be assumed to repair the other automatically.

Reconcile discounts, merchandise, tax and shipping#

Google's discount implementation reference specifies the actual discounted unit price in price and the unit discount amount in discount. Analytics does not automatically subtract the latter from the former. A coupon label also does not perform the monetary calculation.

Consider this hypothetical USD order, with no refunds or currency conversion in the comparison:

ItemOriginal unit priceUnit discountEmitted unit priceQuantityMerchandise value
A501040280
B25025125
Total3105

The merchandise total is 40 × 2 + 25 × 1 = 105. The discount is 10 × 2 = 20, already reflected in that merchandise total. Subtracting it again would incorrectly produce 85.

Suppose tax is 8 and shipping is 7. The charged total is 120, but Google's purchase contract defines event value as the sum of item price times quantity, excluding tax and shipping. For this example, the monetary event fields are:

{
  "transaction_id": "DEMO_ORDER_A",
  "value": 105,
  "currency": "USD",
  "tax": 8,
  "shipping": 7,
  "items": [
    {"item_id": "DEMO_A", "price": 40, "discount": 10, "quantity": 2},
    {"item_id": "DEMO_B", "price": 25, "quantity": 1}
  ]
}

This is an educational parameter object for a purchase event, not a complete integration or real order. It represents one purchase and three item units. Setting event value to 120 while the items sum to 105 would mix merchandise and charged totals; it would not be evidence of three purchases, missing tax collection or advertising fraud.

Keep that GA4 merchandise-value contract separate from another integration's order-value mapping. The Meta and Shopify amount audit traces native or third-party purchase values to the actual order field and payment state before comparing them with gross sales, total sales or collected cash.

Use your commerce system's documented allocation for order-wide discounts and rounding. Do not invent per-item amounts that fail to reconcile with the authorized order record. When the next question concerns Ads profit columns, audit the separate Google Ads cart and cost joins; a correct GA4 purchase event does not establish those product and cost inputs.

Check reporting currency before chasing a small difference#

Separate the transaction currency from the currency used to display the report. Google's currency reference explains that the property currency determines displayed values and Analytics converts local transaction currencies using the prior day's exchange rate. Changing the reporting currency can affect historical displayed data too.

Record the sent currency, property reporting currency and any currency requested by an export. A payment processor or finance report may apply a different rate or timestamp. Do not use that possible difference to excuse a missing currency field or a large unexplained value error.

Where BigQuery is available, distinguish local transaction values from reporting-currency measures. Never add raw amounts from different currencies as though they share one unit. Retain the original amounts and the conversion basis used by the comparison.

Verify the repair at collection and reporting boundaries#

In an authorized test environment, create a distinct synthetic order and inspect the complete outgoing event. Google's validation guide recommends DebugView for event-level and item-level parameters; the items view is useful when order-level value looks correct but products do not.

Retain the tag or application release version. Check the released implementation separately from an unpublished preview. Test at least a single-unit order, a multi-unit order and a discounted order under the applicable consent paths. Those cases expose different mistakes without requiring production customer information.

Then inspect the mature processed report with the frozen property, dates, metrics and filters. If the event is absent entirely, follow the successful request but missing GA4 data diagnostic. If accepted business outcomes and channel credit differ, use the platform measurement comparison.

Do not repeatedly resend a historical purchase just to see whether a new value replaces it. A new tag configuration is not proof of a historical correction. Preserve the original evidence and have the implementation owner assess the supported correction path separately.

Close with a specific receipt: demonstrated defect, changed field or mapping, validated test cases, observed reporting result and remaining unknowns. A corrected report does not prove increased sales.

For campaign-delivery questions, discuss a scoped AdProof review with dates, timezone, delivery definitions and comparable exports. Its supported campaign/event/report exports can help investigate delivery where integrated. The anonymized fashion-retail delivery-quality case illustrates that scope; it does not establish checkout revenue, ecommerce integration coverage or sales uplift.

Frequently asked questions#

Why can Event value exist while Total revenue is zero?

Event value can sum a custom event's value parameter. Ecommerce revenue needs the appropriate event and monetary fields. Check the emitted event name, event-level value and currency, and the exact report population.

Is currency inside each item enough?

No. When sending purchase value, provide the transaction currency at event level. Check that the item prices and event value use that currency consistently; a property display setting does not repair an incomplete payload.

Should purchase value include tax and shipping?

Google's purchase reference defines value as the sum of item price times quantity, excluding tax and shipping. Send those separately and compare the report with a merchandise total using the same basis.

Does fixing the tag correct old revenue automatically?

Do not assume it does. Verify new collection and processed reporting separately, preserve the historical evidence, and assess any correction through its supported workflow rather than replaying orders experimentally.

Your next step

Trace the purchase values to GA4

Record the event name, value, currency and item fields for one accepted order.

Use the tracking QA checklist

Opens a practical guide. No email required.

Back to all field notes