TL;DR
- Google published a new help document for multi-source conversions in Google Ads, a beta that connects a website conversion action to a backend source like a CRM or order database via Data Manager, reported by Search Engine Roundtable on 16 September 2026.
- It lists five benefits: recovering conversions lost to ad blockers, better bidding, simpler setup, real-time value adjustment, and supplementing the tag with email or phone.
- The real-time value adjustment is the key capability: your CRM can send restatements, upsells or finalized totals to override the value the tag recorded.
- It differs from enhanced conversions, which harden the tag's own event; multi-source adds a separate backend system that can confirm and correct it.
- It is a beta with no stated general-availability date, no regions, and no published match rates, so validate against your own records before it drives Smart Bidding.
Google has published a new help document for multi-source conversions in Google Ads, a beta that lets you connect an existing website conversion action to an additional backend data source such as a CRM or an order database, through Data Manager or the Data Manager API. Search Engine Roundtable reported the new documentation on 16 September 2026. The pitch is a more complete count of conversions and the ability to correct the value of a conversion after the fact, using data your website tag never sees.
Google renamed this feature last month, from conversions with multiple data sources to multi-source conversions, and has now added a dedicated help page called Multi-source conversions in Google Ads (beta), plus supporting docs for diagnostics, FAQs, tag troubleshooting, and supported data sources. It is still a beta, so treat the capability as available to test rather than finished.
What multi-source conversions do
The core idea is that your Google tag on the website is one source of conversion data, and your backend systems are another, and this feature joins them onto the same conversion action. Instead of the tag being the only thing reporting a conversion, you can add a backend source that confirms, completes, or corrects it. Google lists five benefits in the documentation.
| Benefit | What the documentation says it does |
|---|---|
| Resilient, accurate measurement | Recovers conversions the Google tag can miss because of browser restrictions and ad blockers, by adding a backend source. |
| Better bidding | More comprehensive conversion data leads to better bidding outcomes. |
| Simpler setup | Uses the new Google Ads Data Manager for a more integrated experience. |
| Real-time value adjustment | Sends financial updates such as restatements, upsells, or finalized cart totals from your CRM to override the value the tag recorded. |
| Better measurement accuracy | Supplements the tag with user-provided data such as email or phone to recover conversions and improve bidding. |
The value-override is the part worth understanding
Most conversion tooling adds conversions or recovers ones that were lost. The real-time value adjustment is different, and it is the capability that changes what advertisers can do. It lets your backend send an accurate financial value that overrides the value your tag recorded at the moment of conversion.
That matters because the value captured at checkout is often not the final value. An order gets partially refunded. A cart total is finalized after tax and shipping. An upsell happens after the initial purchase. A lead that the tag recorded at a placeholder value turns into a deal of a known size in the CRM. When Smart Bidding optimizes toward conversion value, feeding it the corrected value rather than the checkout-moment value changes what it bids on. An account that passes real revenue back, including restatements and refunds, is optimizing toward money it actually keeps, not toward gross checkout totals.
How this differs from enhanced conversions
It is easy to confuse this with enhanced conversions, and the difference is worth being precise about. Enhanced conversions supplement your tag with hashed first-party data, such as an email address collected on the page, to recover attribution that browser restrictions would otherwise lose. It is still fundamentally the tag's event, made more durable.
Multi-source conversions go further: they connect a separate backend system, a CRM or order database, as an additional source on the conversion action. That backend can carry information the page never had, most importantly the final financial value and events that happen after the visit. Enhanced conversions make the tag's own event survive; multi-source conversions add a second system that can confirm and correct it. The documentation notes that supplementing the tag with user-provided data such as email or phone is one of the benefits, so there is overlap, but the backend-source connection and the value override are what is new.
What to check before you rely on it
The feature is only as good as the backend data you connect, and connecting a messy source produces confident wrong numbers rather than better ones. A few things to settle first.
- Confirm your backend has a reliable join key. The whole thing depends on matching a backend record to the tag's conversion, so an order ID or a hashed identifier has to line up on both sides.
- Decide what value you are sending, and when. A restatement that arrives after a refund is useful; a value sent before the order is final can make bidding worse, not better.
- Check the supported data sources list before planning an integration, because the documentation ships a specific list and your system may or may not be on it.
- Watch the diagnostics. Google shipped a Fix diagnostic alerts page and Tag Diagnostics troubleshooting alongside this, which is a sign that misconfiguration is common enough to need its own tooling.
- Treat it as a beta. Validate the numbers against your own records before you let the corrected values drive Smart Bidding, and expand only once they reconcile.
What Google did not say
The documentation describes the capability but leaves the operational questions open. It did not give a general-availability date or say which regions the beta covers. It did not quantify how many conversions a typical account recovers, so the "resilient measurement" benefit is stated without a size. It did not detail the matching method or match rates you should expect, which is what determines whether the recovered conversions are real. And it did not say how the override interacts with attribution windows, or what happens when a backend value arrives long after the conversion. Those are the details an advertiser needs before trusting the corrected numbers, and they are not in the announcement.
What this means for Thai advertisers
The value-correction and backend-source model fits the Thai market unusually well, because so much of the real transaction happens off the website. A large share of Thai e-commerce and lead generation closes in chat, on LINE, or over the phone, and the final value is confirmed in an order system or a CRM rather than at a web checkout. An advertiser whose website tag only ever saw a form fill or an add-to-cart has, until now, been optimizing toward a weak proxy. Connecting the order database or CRM as a second source is how the real outcome gets back to Google Ads.
The refund and restatement handling matters here too. Thai retail carries meaningful return rates and cash-on-delivery cancellations, and an account optimizing toward gross checkout value is bidding on revenue it never collects. Passing the corrected value back is how bidding aligns to money actually received. The prerequisite is the same as anywhere: the backend data has to be clean and joinable, and the measurement has to reconcile before it drives spend. Teams should scope this alongside their analytics and measurement setup, since the join keys and data hygiene sit there, and keep the bidding changes inside the Google Ads plan rather than flipping them on the moment the beta appears.
Frequently asked questions
What are multi-source conversions in Google Ads?
They are a beta that connects an existing website conversion action to an additional backend data source, such as a CRM or order database, through Data Manager or the Data Manager API. Google published a dedicated help document for the feature, reported by Search Engine Roundtable on 16 September 2026.
How is this different from enhanced conversions?
Enhanced conversions supplement your tag's own event with hashed first-party data to recover attribution. Multi-source conversions add a separate backend system as another source on the conversion action, which can carry the final financial value and post-visit events, and can override the value the tag recorded.
Can it fix my conversion values after the sale?
Yes, that is the real-time value adjustment benefit. The documentation says you can send financial updates such as restatements, upsells, or finalized cart totals from your CRM to override the value the tag recorded, which lets Smart Bidding optimize toward corrected revenue rather than the checkout-moment value.
Does it recover conversions lost to ad blockers?
Google says the resilient measurement benefit recovers conversions the tag can miss because of browser restrictions and ad blockers, by adding a backend source. The documentation does not quantify how many conversions a typical account recovers.
Is it available now?
It is a beta with new documentation as of 16 September 2026. Google did not give a general-availability date or specify which regions the beta covers, so check the supported data sources list and confirm availability on your own account before planning an integration.
The bottom line
Multi-source conversions let a backend system confirm, complete, and correct what your website tag reports, and the value override is the capability that changes real behaviour: an account can finally bid on revenue it actually keeps rather than gross checkout totals. It is a beta, its usefulness depends entirely on clean, joinable backend data, and Google has not published the match rates or availability that would let you judge it from the outside. Test it against your own records first, and for Thai advertisers whose real sales close off the website, it is worth testing sooner rather than later.
