Conversion value
Conversion value is the monetary worth attached to a conversion or key event. In GA4 it comes from the value parameter (with currency) sent on events such as purchase or generate_lead, and it feeds revenue, ROAS, and page-value calculations. Because it is whatever you assign — a real order total or an estimated lead worth — its reliability depends entirely on consistent, correctly scoped tagging.
What this means
Conversion value is the amount you assign to a converting event. GA4 reads it from the event's value parameter alongside a currency parameter. For a purchase the value is usually the order total; for a lead or sign-up it is an estimated worth you supply. That estimate is a modeling choice, not an observed sale, so its accuracy depends on the assumptions behind it.
Why scope and currency matter
Value-based metrics — revenue, ROAS, page value, event value — all inherit conversion value's quality. If currency is missing GA4 may not convert correctly; if the value is sent on the wrong event or duplicated, totals inflate. Decide once what each conversion is worth, send a currency every time, and validate against the order or CRM system before trusting any value-weighted report.
For non-purchase conversions, document that the value is an estimate so consumers of the report do not read it as booked revenue.
- GA4 value parameter + currency parameter
- Real for purchases; estimated for leads/sign-ups
- Feeds revenue, ROAS, page value, event value
How it appears in analytics and logs
A conversion value reflects whatever the tagging assigns. Missing or zero values, wrong currency, or double-counted events silently distort every downstream revenue and ROAS figure, so value-quality checks come before value-based analysis.
Diagnostic use case
Attach money to conversions so marketing performance can be judged on value rather than raw counts, enabling ROAS, value-based bidding, and page value.
What WebmasterID can help detect
WebmasterID records event values first-party, so the amounts behind ROAS and page value are captured without third-party cookies and can be reconciled against the source of truth.
Common mistakes
- Sending value without a currency parameter.
- Treating estimated lead values as booked revenue.
- Double-counting value via duplicated events.
Privacy and accuracy notes
Conversion value is a monetary number on an event, not personal data. Never place order IDs tied to identity or PII into value-related parameters.
Related pages
- Page value
Page value estimates the average monetary value of a page by crediting it with revenue from transactions (and goal values) that occurred in sessions where the page was viewed before the conversion. It is a way to surface which content contributes to revenue, not just which page closes the sale. Page value is an attribution-style estimate, so it shares the assumptions and limits of crediting upstream pages.
- Event value
Event value is a numeric value attached to an event via a value parameter, letting analytics sum the worth of actions that are not direct purchases — a lead, a sign-up, a key interaction. It turns counted events into an aggregable monetary or proxy figure. The catch is that event values are assigned by the implementer, so inconsistent or arbitrary values quietly distort every total and comparison built on them.
- Conversion events (key events)
A conversion event is an ordinary event you have marked as important — a purchase, a signup, a qualified lead. GA4 now calls these 'key events'. Nothing about the event changes; marking it tells the platform to count it as a conversion and build conversion reports around it. The decisions that matter are which events to mark, and whether to count once per session or every time.
- Event tracking docs
Assign value and currency to conversions consistently.
Sources and verification notes
- Google — GA4 measure ecommerce and the value parameter
- Google — GA4 currency reporting and conversion value
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.