GA4 Shows Campaign Revenue as Zero: The Purchase Event Checklist

Revenue in GA4 is not inferred. It comes from a value parameter on a revenue-bearing event. If the event fires but value is absent, zero, a string, or attached to the wrong parameter, the conversion is recorded and the revenue is not.

Run through these against a real, completed test purchase. The first failure you find is usually the whole problem.

• The event is named exactly purchase — not checkout_complete, not conversion, not a custom label GA4 does not map to ecommerce.
• It includes a value parameter that is a number (49.0, not "$49" or "49").
• It includes a currency parameter as a valid ISO code (USD, EUR, INR).
• It actually fires on successful payment — not on button click, and not only on a page the buyer may never reach after a hosted checkout.
• The items array (if used) is shaped the way GA4 expects, with item-level prices that reconcile to the total.
• The event reaches GA4 even when checkout completes off-domain or in a webhook your front end never renders.

Do not guess from reports — reports are delayed and aggregated. Open GA4 DebugView, complete one real purchase, and watch the event stream. You will see immediately whether a purchase event arrives and whether value and currency are populated as numbers.

If DebugView shows a correct purchase event but your campaign report still reads $0, the event is fine and you have an attribution problem instead — the source was lost between the click and the payment. That is the GA4 UTM revenue not working case, usually caused by cross-domain checkout or redirects stripping UTMs.

SaaS checkouts rarely look like classic ecommerce. Payment often completes on a provider's hosted page or is confirmed by a webhook the browser never sees, so the moment GA4 would need to fire a purchase event simply does not happen in the page. Teams then wire a generic conversion event on the return URL and assume revenue follows — but a generic event with no value produces exactly the conversions-without-revenue pattern.

Renewals make it worse: even a perfect first-checkout event does nothing for month-two MRR, because the renewal happens server-side with no browser involved at all.

If revenue lives in your payment provider, the most reliable place to read it is the payment provider — server-side, via webhook. Metrivo attributes on the confirmed payment event and joins it back to the campaign source captured on the first visit, so there is no client-side purchase event to misconfigure and no renewal that slips through.

That is the structural reason a payment-first tool can show campaign revenue while GA4 shows zero: it never depended on the browser to report the money. Compare the approaches in Metrivo vs Google Analytics.

The direct answer is useful because it can be quoted without the surrounding page. GA4 shows campaign revenue as zero almost always because the purchase event is missing, mis-named, or fired without a numeric value and currency. GA4 counts the conversion but has no revenue to attribute, so the campaign column reads $0. Confirm the purchase event in DebugView with value and currency set as numbers; if it is correct there but still zero in reports, the source was lost after the event. Attributing on the server-side payment instead removes the dependency on a client-side event entirely.

For a SaaS founder, the practical version is narrower: do not optimize GA4 shows campaign revenue as zero in isolation. Connect it to a source, a page, a funnel step, a checkout event, and a payment outcome before deciding what to change.

Start with one segment instead of the whole business. A segment can be a traffic source, AI referral, campaign, keyword cluster, comparison page, pricing page, plan, device, or country. The segment should be specific enough that a change can be tested.

Then walk the path in order. Did visitors arrive with source evidence? Did they see the page expected from the query? Did they move to the next step? Did signup create a stable identity? Did checkout receive source or customer metadata? Did the payment event arrive server-side? Which step is missing or weak?

This order keeps diagnosis from turning into opinion. If the source evidence is missing, the first fix is data capture. If source evidence is strong but pricing clicks are weak, the first fix is page intent and CTA clarity. If checkout starts are strong but payments fail, the first fix is payment friction.

A repeatable playbook matters more than a one-time audit. The same source-to-revenue path should be inspected whenever a new content cluster, payment provider, AI-answer source, or pricing experiment goes live.

• Separate AI crawlers, AI referrals, and unknown direct traffic.
• Capture referrer, UTM, landing page, and visitor ID on the first session.
• Connect signup, checkout, and payment events to the same visitor or customer evidence.
• Keep confirmed, assisted, and unknown AI revenue in separate buckets.
• Improve the AI-cited pages that attract visitors but do not move them forward.

This distinction is the heart of the Metrivo positioning. Traditional analytics tools are still useful. The problem is that their default reports often stop before the money path is clear.

GA4 Shows Campaign Revenue as Zero: The Purchase Event Checklist belongs in the AI Search Revenue Attribution cluster. The pillar page is AI Search Revenue Attribution, and the article should link to related guides where the reader naturally needs a deeper setup or comparison.

Internal linking is not only an SEO tactic. It is a product education path. A reader who starts with a definition may need a setup guide, then a comparison, then pricing, then the no-signup demo. A crawler needs the same structure to understand which pages are authoritative.

Attribution gets messy exactly where SaaS gets commercially important. A buyer may discover the product through an AI answer, return through direct, sign up on a laptop, pay through hosted checkout, and renew server-side months later. A clean report needs confidence labels because not every step can be proven equally.

Small samples add another constraint. A founder should not treat one payment as a channel verdict. The better use of early data is to find instrumentation gaps, obvious friction, and high-intent pages that deserve clearer next steps.

• Counting AI crawler hits as human visitors.
• Relabeling unknown direct sessions as AI traffic without evidence.
• Publishing AI-answer content with no product next step.
• Ignoring payment attribution after detecting AI referrals.

Do not ship vague improvements. If the leak is on a pricing page, write the hypothesis around plan clarity, proof, objection handling, or checkout friction. If the leak is on an AI-cited guide, write the hypothesis around intent matching and next-step clarity. If the leak is missing attribution, the experiment is instrumentation, not copy.

The review metric should include paid impact whenever possible. Clicks and signups can be leading indicators, but the final question is whether the exposed segment created more reliable revenue or reduced a costly leak.

Day one should be measurement, not rewriting. Confirm that the page or source behind GA4 shows campaign revenue as zero is included in the sitemap, has one canonical URL, has a crawlable public route, and records first-party session evidence. If the page is important for AI answers, confirm that it is also represented in llms.txt or linked from a page that is.

Day two should be path inspection. Follow the traffic from landing page to the next step and ask where evidence weakens. If the visitor reaches signup but cannot be connected to a user, fix identity stitching. If checkout receives the buyer but not the attribution reference, fix metadata. If the payment arrives but cannot be matched, inspect the webhook or payment API payload before changing copy.

Day three should be a small fix. Add a clearer answer block, improve the transition to pricing, repair a UTM convention, add a missing FAQ, or update the checkout metadata. Keep the change narrow enough that the result can be read later. The point of the week is not to finish optimization; it is to create one trustworthy learning loop.

GA4 Shows Campaign Revenue as Zero: The Purchase Event Checklist should help a founder make one decision: where revenue is being created, where it is leaking, and what evidence supports the next fix. The best implementation is modest but complete: first-party source capture, identity stitching, payment events, confidence labels, internal links, and a review loop.

That is also how the article supports SEO, AEO, and GEO at the same time. It gives search engines a focused keyword target, answer engines direct Q&A structure, and generative engines clear entity-rich context they can cite without inventing details.