Conversion value adjustments let you restate what a B2B SaaS conversion is worth after Google has already logged it — so a form-fill that starts life worth a $50 proxy becomes worth $500 when it turns into an SQL and the full deal value when it closes. Per Google’s conversion-adjustment definitions, a restatement changes a conversion’s value without changing the count, while a retraction removes the conversion and zeroes its value. Used well, restatements are how you make Smart Bidding chase pipeline value instead of raw lead volume — the single highest-leverage fix for a SaaS account whose cost-per-lead looks fine while pipeline does not.
This post explains the mechanic, how it differs from importing offline conversions, the one prerequisite that trips most accounts up (you must be on value-based bidding for restatements to do anything), the proxy-value ladder to encode, and the data-strength bar you need to clear. It assumes the strategic case for optimising to revenue is already made; here we cover the specific adjustment workflow that implements it.
Restatements vs retractions: two different tools
A conversion adjustment corrects a conversion Google has already recorded, and the two types do different jobs. A restatement keeps the conversion but changes its value — this is the workhorse for lead-quality bidding, because it lets you log a lead early and sharpen its worth as the sales process reveals it. A retraction permanently removes the conversion and sets its value to zero, which is the right tool for a spam lead, a duplicate, or a disqualified form-fill you want the algorithm to stop chasing.
The distinction matters because they affect bidding differently. Restatements influence value-based strategies — Maximize Conversion Value and Target ROAS — because those bid on value. Retractions can affect both conversion-based strategies (Maximize Conversions, Target CPA) and value-based strategies, because zeroing a conversion removes it from the count as well as the value. For a B2B SaaS account, the typical pattern is restatements to grade lead quality upward through the funnel and retractions to purge the junk that would otherwise teach bidding to find more junk.
Why this is not the same as an offline conversion import
Offline conversion imports and value adjustments are often conflated, but they operate on different objects. An offline conversion import logs a new event tied back to the original click — for example, uploading a closed-won deal as its own conversion. A value adjustment does not create anything new; it restates the value of a conversion Google already recorded, keeping one conversion per lead and correcting its worth as the deal matures.
For long sales cycles, that difference is practical, not academic. Import-based stacks tend to accumulate a chain of stage conversions per lead (lead, MQL, SQL, closed) that you must manage with primary/secondary settings to avoid double-counting and to point bidding at the right event. Restating the single original form-fill keeps the picture clean: one conversion whose value climbs from proxy to real as it moves through the CRM. Many accounts run both — importing offline events for stages that were never a web conversion, and restating the web conversion’s value as its quality becomes known. The goal either way is the one covered in optimising for SQLs, not leads: give Smart Bidding a signal that reflects revenue, not form submissions.
The prerequisite: you must be on value-based bidding
Here is the step most accounts skip. Restatements only influence value-based bidding strategies — Maximize Conversion Value and Target ROAS. If your campaigns run on Target CPA or Maximize Conversions, restating a conversion’s value changes the number in your reports but does not change a single bid, because those strategies optimise toward conversion count and cost-per-conversion, not value. You can build a perfect proxy-value ladder and watch it do nothing because the bidding strategy is not listening to value.
So the sequence is: move the campaigns you want to grade by lead quality onto value-based bidding first, then implement value adjustments. That decision is its own trade-off, covered in Maximize Conversions vs Maximize Conversion Value and in the comparison of Maximize Conversion Value vs tCPA. Only once value is the thing being optimised do restatements become a lever rather than a reporting cosmetic — and retractions remain useful on count-based strategies because zeroing a conversion removes it from the count too.
Building the proxy-value ladder from your CRM
With value-based bidding in place, encode a value ladder that mirrors the relative pipeline worth of each stage. A widely used starting structure is MQL around $50, SQL around $500, opportunity created around $2,500, and closed-won at the actual deal value, with only the pipeline-quality events set as primary conversions. The headline numbers matter less than the ratios between them: if an SQL is realistically worth roughly ten times a raw MQL in your funnel, that ratio is what bidding needs to see, because the algorithm will pursue whatever hierarchy you encode.
Derive those ratios from your own data, not a template. Pull stage-to-stage conversion rates and average deal size from your CRM, and set each stage’s proxy value to its expected contribution to pipeline. This is the same logic behind a conversion value ladder, applied through the adjustment workflow: log the form-fill at the entry proxy, then restate it upward as the lead is qualified and again when it closes. Google supports adjusting the same conversion multiple times and processes adjustments in time order, so a single lead’s value can track the deal from first touch to signature.
The data-strength bar you have to clear
Value adjustments sharpen an account that already has signal; they cannot manufacture signal where there is none. Smart Bidding needs a steady flow of conversions to optimise well — a commonly cited rough floor is around 30+ conversions per month, which comes from agency guidance rather than an official Google figure — and value-based strategies with graded values ask more of that volume than simple count-based bidding does. An account logging a handful of conversions a month does not give the algorithm enough to learn a value hierarchy from.
Google’s own data-strength signals are the read on whether your first-party and conversion data are rich enough to carry this. If you are below the volume the account needs, widen the conversion base first — add a reliable mid-funnel action, fix tracking gaps, extend the conversion window to match the sales cycle — and layer value adjustments on once there is a stable stream to grade. Applied to a thin account, value adjustments mostly add noise; applied to an account with real conversion volume, they are the mechanism that finally points bidding at revenue instead of lead count.
Putting value adjustments to work
The workflow, in order: confirm the campaign is on value-based bidding, build a proxy-value ladder from your CRM’s stage conversion rates and deal sizes, log each lead at its entry value, restate upward as it becomes an SQL and closes, retract the junk, and confirm you have the conversion volume for Smart Bidding to learn from. Done right, cost-per-lead stops being the metric the account chases and pipeline value takes its place — which is the only version of “more conversions” a B2B SaaS board actually cares about.
If you want this implemented without the double-counting and bidding-strategy mismatches that break most attempts, a Google Ads audit checks whether your conversion setup and bidding strategy can even support value adjustments, and our Google Ads management service builds the full CRM-to-bidding value loop around your sales cycle. To check whether your current tracking is clean enough to restate values at all, start with the free 10-point audit checklist.