Implementation: CRM Stage to Ads Values
Turn a CRM stage change into a real Ads value.
Google Ads optimizes toward whatever value it's fed. If every lead reports the same flat conversion, Ads has no way to tell a serious buyer from a dead end. This workflow reports a different value for each pipeline stage instead of one flat number.
- $0 setup, month to month
- 30-day guarantee, pay only if satisfied
- Free proposal within 1 business day
What this workflow covers
The field map, the click ID, and the reversal problem.
The field map
Each CRM pipeline stage, such as New, Qualified, Booked, or Won, maps to a specific conversion value agreed with your sales team ahead of time. A stage change fires that mapped value instead of the same flat lead event repeating every time.
The identity match: the click ID
The lead record needs to carry the click ID captured at first submission for any of this to work. Without that field stored on the record from day one, usually built as part of a UTM-to-CRM mapping workflow, there is nothing later for the import to attach the value to.
Where the data enters
A workflow automation inside the CRM watches for a stage field to change, packages the click ID, the timestamp, and the mapped value, and sends it to Google Ads through the offline conversion import feature. Depending on the CRM's connector, that send happens as a scheduled batch or closer to real time.
How failures surface
Google Ads enforces a conversion matching window on offline imports, tied to the original click, so a deal that closes well after that window can be rejected on import; we confirm the exact window on each account rather than assume one figure applies everywhere. A stage that flips back and forth, Won reopened to Lost, can also produce a contradicting import if the automation isn't built to handle a reversal.
Where a value rule quietly stops reflecting reality.
One value per stage, agreed in writing first
This only works if the stage-to-value mapping is agreed with sales before it ships. The entire point is differentiating real value between leads, and a mapping built without sales input tends to just repeat whatever a CRM admin guessed months ago.
The click ID has to survive the whole pipeline
If any step between lead capture and the eventual stage change lets that field go blank or get overwritten, the value rule has nothing to attach the import to. It fails silently, one lead at a time, rather than producing an error anyone would notice right away.
Google decides what to do with the value, not us
Once a value is imported, Google's own bidding systems decide how heavily to weight it. We build the pipe and confirm the value lands correctly on the right click; what the algorithm does with that signal afterward is a platform decision we don't control or promise an outcome from.
Rebuilt after either platform changes
Both CRM automation builders and Google's offline conversion import have changed supported formats and connectors before. We re-test this setup after either platform pushes an update that touches automations or conversion import, rather than treating a working setup as permanent.
How we set it up.
01
Confirm the click ID is captured
We verify the lead record already carries a click ID from first submission, building that capture first if your CRM doesn't have it yet.
02
Agree the value mapping
We work with your sales team to assign a real, defensible value to each pipeline stage, from a new lead through to a closed deal.
03
Build and test the import
We set up the automation, run a test lead through every stage, and confirm each mapped value appears correctly against the right click inside Google Ads.
CRM stage to Google Ads value rules FAQ.
Organic, direct, and referral leads that never carried a paid click have nothing to import a value against in Google Ads. This workflow only applies to leads that started with a paid search click; other channels need a separate reporting approach.
Yes, if your CRM stores an actual deal amount by the time it's won. That figure can replace a fixed stage value, though it means the Won-stage import happens later, once the real number is actually known.
We build the automation to send an updated value when a stage reverses, rather than leaving the earlier import standing uncorrected. The exact behaviour depends on what your specific CRM's automation tools allow.
Not directly through this workflow. Meta has its own conversions API for a similar purpose, which is a separate setup. This page is scoped specifically to Google Ads value rules.
Yes. Point us to your CRM, your pipeline stages, and whether a click ID is already stored, then request a proposal. Expect a scoped plan back within one business day.
Give Google Ads a real signal about which leads matter.
We'll confirm your click ID is captured, build the stage-to-value mapping with your sales team, and test the import before it ever touches your live bidding.