The short answer
GA4 works out revenue from two fields on the purchase event: value, sent as a number, and currency, a three-letter code like USD. Open your thank-you page with DevTools, find the request to /g/collect with en=purchase, and look for epn.value and cu. If you see ep.value instead, your value is being sent as text. If cu is missing, so is your currency. The table below covers the other shapes.
Read the purchase hit in two minutes
Your report can't tell you why revenue is missing. The request your tag sends can, so start there.
- Open your site in a private window with ad blockers off, and place a test order (or reload a thank-you page that fires the purchase).
- Open DevTools › Network and filter for
collect. - Click the request that carries
en=purchase. Its parameters sit in the URL and, when several events go together, in the request body. - Read four things: the value,
cu,ep.transaction_idandpr1.
If there's no request with en=purchase at all, the event isn't firing. That's a different problem, covered further down.
How to decode a purchase hit
GA4 marks every custom parameter by type. epn. means a number and ep. means text. That one letter decides whether GA4 gets your order value as a number.
| On the request | What it is | Healthy example |
|---|---|---|
en | Event name | purchase |
epn.value | Order value, as a number | 59 |
ep.value | Order value, as text | should not appear |
cu | Currency (ISO 4217 code) | USD |
ep.transaction_id | Order ID | T1001 |
pr1, pr2… | One per item: id, nm (name), pr (price), qt (quantity), joined by ~ | idSKU-1~nmLinen shirt~pr29.5~qt2 |
Google's own help page for missing revenue says value must be "assigned a number rather than a string" with no currency symbol, and currency must be a three-letter ISO 4217 code. Its event reference adds that currency is required whenever you set value.
What we saw: 11 purchases through Google's real tag
On 30 October 2026 we loaded Google's tag (gtag.js) for a made-up GA4 property on a test page and fired one purchase in each of the shapes below. Every request to Google Analytics was recorded, then stopped before it left the browser, so this shows what the tag sent.
| What the site sent | Purchase request? | What went out |
|---|---|---|
value: 59, currency: 'USD' (correct) | yes | epn.value=59, cu=USD |
value: '59.00' (text) | yes | ep.value=59.00 |
value: '$59.00' | yes | ep.value=$59.00 |
value: '59,00' (decimal comma) | yes | ep.value=59,00 |
No currency | yes | epn.value=59, no cu |
No value, items with prices | yes | no value at all; items sent |
Value with a capital V | yes | epn.Value=59 |
A Tag Manager ecommerce: {…} object passed to gtag | yes | ep.ecommerce=[object Object] and nothing else |
Item price: '$29.50' | yes | pr$29.50 inside pr1 |
transaction_id: '' | yes | an empty ep.transaction_id |
dataLayer.push({event: 'purchase', ecommerce: …}) with only gtag.js on the page | no | nothing |
Ten of the 11 still sent a purchase. Each would reach GA4 as a purchase, so "the purchase is firing" tells you nothing about revenue.
gtag doesn't fill gaps. With no value, it didn't add up the items for you. With Value, it sent epn.Value, which isn't the value GA4 reads for revenue.
Tag Manager and gtag shapes don't mix. Pasting a Tag Manager ecommerce object into a gtag call sends the text [object Object]. A dataLayer push on its own sends nothing, since no tag was set up to read it.
Match what you see to the fix
| What you see on the request | Cause | Fix |
|---|---|---|
ep.value instead of epn.value | Value is text, often from a template that prints "59.00" or "$59.00" | Send a bare number: 59.00, no quotes, no symbol |
No cu | Currency missing | Add currency: 'USD' (your store's code) at the event level |
| No value parameter | Value never set | Set value to the sum of price × quantity, without tax or shipping, as Google's reference describes |
epn.Value or another odd spelling | Wrong parameter name | Use lowercase value and currency |
ep.ecommerce=[object Object] | A Tag Manager shape sent through gtag | Pass the fields directly to gtag, or send it through a Tag Manager GA4 event tag |
| Purchase request, but item revenue is empty | Item price has a currency symbol or isn't a number | Make each item's price a number |
| Some orders missing, others fine | Empty or repeated transaction_id | Send each order's real ID |
| No purchase request at all | Nothing reads the dataLayer push, or the tag doesn't fire on the thank-you page | See the next section |
On the transaction ID: Google deduplicates purchases that share an ID on web streams, and it treats every empty ID as the same one. So a blank transaction_id can collapse many orders into one without any warning.
Tag Manager: the data has to be in two places
If you use Google Tag Manager, Google's missing-revenue help page says the purchase has to be right in both your site's data layer and the GA4 event tag. The tag only reads the ecommerce object when you tick More settings › Ecommerce › Send Ecommerce data and set Data source to Data layer.
Google's examples push { ecommerce: null } before each ecommerce event to clear the previous ecommerce object, so old items can't carry over into a purchase.
When the request has no en=purchase at all, check the trigger first. Often the tag waits for an event name the site never pushes, or for a thank-you URL that changed. Our guide to tags that stop firing covers that hunt. If the tag waits for consent, our Tag Manager Consent Mode guide shows where the default belongs.
Before you change anything
Check DebugView after the fix, not the reports. Standard reports lag behind, and our Google Analytics not working guide covers how long is normal. If Meta is missing values too, the same order of checks applies, and we've written up Meta's purchase event on Shopify separately.
Where TagSentry fits
Event monitoring records which fields each event sent and their types (like value as a number), and where it was sent. So a purchase whose value turns up as text, or with no currency, shows as broken.
Purchases you've saved as key events are checked for value and currency, with GA4 and Meta each watched on their own. Once 20 purchases have come in, it emails you when they start arriving with a field missing, empty or of the wrong type, on every plan, Free included.
It's one line of code above Google Tag Manager. On WooCommerce and other checkouts that run your site's own code, it watches the purchase once the line is in your site-wide header, for visitors whose consent allows it.