Google Ads Multi-Source Conversions: How to Recover Lost Sales Data Without Double-Counting

6 Oct

Every ecommerce business has two versions of the truth about sales: what your website tag sends to Google Ads, and what your order system actually records. They rarely match, because browser settings, ad blockers and tagging errors stop some purchases from ever reaching Google Ads.

Google Ads has started documenting a beta called multi-source conversions, which lets your order database or CRM fill some of those gaps. For Smart Bidding on purchase data, that is valuable. It also gives your backend data the power to overwrite the conversion values your bidding learns from. In this blog, we’ll explain what the feature does, why it matters for the P&L, and the checks to make before anyone switches it on.

What Google has launched

Google’s multi-source conversions help page describes a way to connect an additional data source, such as a CRM or order database, to an existing Google tag website conversion. Data is sent through Google Ads Data Manager or the Data Manager API.

Recover missed conversions: orders in your backend that the tag never recorded can be added.
Fill in missing customer data: if the tag recorded a purchase but not the customer’s email or phone number, the upload can supply it, which helps Google match the sale to an ad click.
Correct conversion values: your order system can send updated values, such as restatements, upsells or finalised basket totals, which override the value the tag recorded.

The glue is the transaction ID: the unique order number sent with each purchase. Google uses it to match backend records to tag events and to avoid counting the same sale twice. The feature is in beta, so it may not be available in your account yet. Search Engine Watch reported on the documentation on 28 September 2026.

Why it matters for the P&L

Smart Bidding can only optimise towards the sales it can see. If a meaningful share of paid-search orders never reaches Google Ads, campaigns look less profitable than they are, and automated bidding is learning from an incomplete picture.

Better signal: recovered conversions and fuller customer data give bidding more to work with.
More honest ROAS: backend values reflect the final order, not just the value when the tag fired.

The flip side is just as commercial. Google says the uploaded value becomes the source of truth and permanently overwrites the tag’s value for matched transactions. Send values in pence when your tag reports pounds and conversion value inflates a hundredfold, straight into value-based bidding.

A worked example

Imagine a UK homewares retailer whose order system regularly shows more paid-search orders than Google Ads reports, and some recorded purchases arrive with no customer email attached. (An illustrative scenario, not a benchmark.)

With multi-source conversions, the retailer connects its order data to its existing purchase conversion action. Orders whose transaction IDs match a tag event are enriched; orders the tag missed are added as new conversions where Google can attribute them to an ad interaction. The danger sits in the detail: if the website sends #1042 but the order export sends 1042, nothing matches, and Google’s diagnostics can flag that conversions may be overcounted.

Who can use it today

Google is specific about eligibility:

It works for Google Ads website conversion actions set up manually with code through the Google tag or Google Tag Manager.
It is not available for conversions imported from Google Analytics or for URL-based conversion actions.
Each upload needs a transaction ID, the conversion date and time, and at least one way to link the sale to an ad, such as a click ID or hashed customer details.

If your bidding runs on GA4-imported purchases, the beta does not apply to that conversion action, so adopting it is a measurement design decision, not a quick switch.

Director checklist before you switch it on

Confirm eligibility. Which conversion action do your campaigns bid on, and is it a coded tag or a GA4 import?
Check transaction IDs on the tag. Every purchase should carry a real, unique order number. Google notes that IDs starting with GG_ mean your own ID is not being sent.
Match the format exactly. Prefixes, letter case, decimals and leading zeros must be identical in the tag and in the upload.
Match values and units. Same currency, same units, and agree whether values include VAT and shipping before anything is uploaded.
Use the authoritative source. Google says the data should come from your ecommerce backend or CRM, not an export from another tag-based analytics tool.
Add it to your existing conversion action. Google recommends this, and warns that deduplication only happens within one conversion action. Two actions counting the same sale in one campaign goal can double-count it.
Confirm consent fields. Only consented events are used, so privacy and legal should sign off how consent is mapped per order.
Use the 14-day trial properly. From the first upload, the extra data is reporting-only for 14 days, then becomes biddable automatically, regardless of any diagnostic alerts. Diary a review before day 14.

Caveats before you rely on it

Beta means change. Recheck the help page before rolling it out across accounts.
Value overrides are permanent. Google advises sending NULL when you do not want to change a value, because any number you send updates reporting and bidding.
Speed matters. Google recommends uploading within 24 hours, ideally on a daily schedule.
Not a fix for broken plumbing. If transaction IDs are missing or inconsistent, fix the tag first.

Final thoughts

#6/100 — Your order data can rescue lost conversions, but only if the IDs match.

Multi-source conversions could give Google Ads a far more complete view of the sales your campaigns drive. Treat it as a finance-grade data connection: one transaction ID format, one value definition, one owner. Use the 14-day trial to clear every alert, then let it steer bidding.

Want help checking whether your purchase tracking is ready? Email info@taggurus.co.uk or book a meeting today to discuss.

FAQ

Q: Is multi-source conversions available in every Google Ads account?
A: No. It is in beta and may not be available to you yet. Check the Data source section of your conversion action.

Q: We import GA4 purchases into Google Ads. Can we use it?
A: Not on that conversion action. Google says imported Google Analytics conversions are not eligible.

Q: Will it double-count our sales?
A: Within one conversion action, Google uses matching transaction IDs to deduplicate. It does not deduplicate across different conversion actions, so never include two actions counting the same purchase in the same campaign goals.