Maximize Conversion Value

Maximize Conversion Value works the same way mechanically as Maximize Conversions - fully automated CPC bidding based on real-time auction signals - but the objective it solves for is total value across conversions rather than raw count. For that to mean anything, it needs conversion values that actually differ from one conversion to the next: ecommerce accounts typically pass this dynamically as the real order total at purchase, while lead-gen accounts assign it through lead scoring or a value passed via offline conversion import once a lead is qualified or closed.

An optional target ROAS field constrains efficiency the same way a target CPA constrains Maximize Conversions - without it, the strategy spends the full budget chasing the highest total value it can find. Conversion value rules are the other setting worth knowing here: they let you adjust the value Google sees for a conversion based on the user's device, location, or audience membership, without touching the raw revenue number in your own reporting system, so bidding can lean toward segments you know convert at higher value even when the checkout or lead form itself does not capture that distinction.

This strategy earns its complexity in accounts where order size or lead value genuinely varies - an ecommerce store selling a $20 item and a $400 item in the same campaign, or a lead-gen business that scores leads by likely deal size. If every conversion in an account is worth roughly the same amount, Maximize Conversion Value has nothing to differentiate and functions identically to Maximize Conversions while adding setup overhead for no benefit. It is worth checking this before switching to it, since setting it up correctly means wiring dynamic values through the ecommerce tag or a value field on the lead conversion action, and that work is wasted if the resulting values end up clustered near the same number anyway.

The classic failure here is a hard-coded value on the conversion action - every lead or every purchase logged at a flat number regardless of what actually happened. The bidding algorithm has no way to tell a $400 basket from a $20 one if both are recorded identically, so it optimizes for conversion count exactly like Maximize Conversions would, while the account's reports keep displaying a ROAS figure calculated from a number that was never real. Because the math still resolves to a plausible-looking percentage, this mistake tends to go unnoticed for a long time - the report does not look broken, it just is not measuring anything.

Read the Conv. value and Conv. value / cost columns as the primary signals, but check them periodically against actual revenue in your order system or CRM rather than trusting Google Ads in isolation - that is the fastest way to catch a currency mismatch, such as cents passed as dollars, or a stale hard-coded value before it skews months of bidding decisions. It is also worth spot-checking the distribution of individual conversion values in the conversion action's own diagnostics; if every single value is identical, that is the hard-coded-value problem showing up directly in the data.