Fix Missing Revenue in GA4 Purchase Events

The Required Fields GA4 Uses for Revenue

For event-level revenue metrics, Google says the purchase event must include event-level value,currency, transaction_id, anditems. If any of those are missing, malformed, or placed at the wrong level, revenue reporting becomes unreliable.

The Common Implementation Mistakes

• value is sent as a string or includes a currency symbol
• currency is missing or not sent in ISO 4217 format
• values are pushed at the wrong level in the payload
• the purchase event fires, but the items array is incomplete or malformed
• GTM data layer values differ from what the event tag actually sends

The Fastest Debug Order

1. inspect the network payload for the live purchase event
2. confirm value is numeric and currencyis present at the event level
3. confirm transaction_id and items are included on every purchase
4. compare DebugView, GTM preview, and the live request payload rather than trusting just one of them
5. wait for reporting latency before assuming the fix failed

Why This Matters

Missing revenue is one of the most commercially dangerous GA4 defects because the purchase event may still appear to be working. Teams see conversion counts and assume the implementation is fine, while revenue-based bidding, channel ROI, and product reporting are quietly wrong.

Official Sources

• Fix missing revenue data
• Measure ecommerce
• Monitor events in DebugView