Google Ads Multi-Source Conversions (September 2026): What Small Ecommerce Teams Must Check Before the Upload Overwrites Their Conversion Values

On September 16, 2026, Google published a new help document for multi-source conversions (beta), which attaches a backend data source — a CRM or an order database — to an existing website conversion action through Data Manager or the Data Manager API. Search Engine Roundtable flagged it the same morning, noting Google had renamed the feature from “conversions with multiple data sources” back in August.

Google’s pitch leads with recovery: win back the conversions your tag lost to ad blockers and browser restrictions. For a store running $4,000 a month, that is the least interesting thing in the document. The part that moves your money sits four bullets down, and it is permanent.

What are Google Ads multi-source conversions?

One Google Ads website conversion action receives data from two places at once: your Google tag, and an upload from your own backend. Google matches the streams using transaction_id — your order ID — and reconciles them inside that one conversion action.

The eligibility fence is narrow. Per Google’s documentation this works only on website conversion actions set up manually with code through the Google tag or Google Tag Manager; imported Google Analytics conversions and URL-based actions are excluded. If your store has run on a GA4 import since day one — which describes a lot of small accounts — you have a prerequisite project, not a feature.

How does the transaction ID matching actually work?

Three outcomes, and knowing them lets you predict what your own data will do:

• The transaction ID matches a tag event. Your upload’s value and currency overwrite the tag’s permanently. Missing user-provided data gets filled in. Every other field — including GCLID — is ignored; the tag’s version wins.
• The transaction ID matches nothing. Google creates a new conversion event from your row and attributes it using whatever identifier you supplied — GCLID, GBRAID, WBRAID, or hashed email, phone, or IP.
• Deduplication is scoped to one conversion action. Google states explicitly that it does not deduplicate against other conversion actions in your account.

Run those rules against a case Google does not cover. Your Shopify export writes order IDs as #1041; your tag fires 1041. Nothing matches. Every upload row becomes a new conversion event attributed by hashed email, reported conversions roughly double, CPA appears to halve, and once the trial closes Smart Bidding pays twice as much for the same order. That failure throws no error. It looks like a good month.

Does recovering lost conversions actually matter at a small budget?

Mostly no. Signal recovery is a volume argument, and volume arguments pay off at volume.

Take a store spending $4,000 a month at a $95 average order value, roughly 120 orders. If your tag misses 8% of purchases to blockers and browser restrictions, recovery hands Smart Bidding about 10 extra conversions a month — ten data points spread across several campaigns, inside the noise band of ordinary weekly variance. You will not separate that lift from a good week, and neither will the bidding model.

This is where The Job to Be Done earns its keep. A conversion signal is hired for two jobs: count the sale and price the sale. Google bundles them and leads with counting, because counting scales with account size. For a three-person team, counting is nearly fine already. Pricing has been broken since you turned on Target ROAS — and this is the first time fixing it needs no enterprise data stack.

Why is the conversion value override the part that matters?

Because your tag reports what the checkout page saw; your backend knows what the order was worth. Those numbers diverge constantly — refunds, partial returns, cancelled lines, late discount codes, support-rep upsells. Google says it plainly: the additional data source “becomes the source of truth for conversion value,” and 0 is a valid value for a full refund.

Put numbers on it. That same store returns 18% of units, and Target ROAS has optimized against gross checkout value the whole time — so it has bid hardest for the categories with the highest return rates: apparel sizing, anything a customer buys two of to keep one. Feed net revenue back through transaction_id and the model stops treating a returned $180 order as a $180 win. On a 120-order month that is roughly a $2,000 correction to what the algorithm believes it bought. The case that margin, not revenue, is the number to feed Google finally has plumbing behind it.

The same override is the risk. Google warns that uploading values in the wrong unit causes “severe conversion value inflation,” because the system does not convert. Send 9500 where your tag sends 95.00 and Google reads $9,500. A 400% Target ROAS appears met at a hundred times reality, and Smart Bidding spends into it — the one error here that can empty a small budget in a weekend.

What happens during the 14-day trial period?

Connect an additional data source to a biddable conversion action and it enters a 14-day trial. Value updates are disabled during it — the tag’s value stays in reporting — and newly created conversions show in reporting but are not used for bidding. After 14 days both switch on automatically. Nobody sends a second confirmation.

Treat it as a free audit window, because it is the only one you get. It is also the headcount trap: a bad mapping does not surface on day one, when you are paying attention. It surfaces on day 15, when you have moved on.

How should a small team set this up without breaking Smart Bidding?

1. Confirm eligibility. Open Conversions > Summary and check the source. If it says Google Analytics, stop — you need a Google tag or GTM purchase conversion first.
2. Attach the source to your existing purchase action, not a new one. Google’s own best practice. Create a second action, leave both in one Goal Set, and a single sale counts twice — deduplication never crosses actions.
3. Match the order ID format character for character. Export twenty recent orders, pull the same twenty transaction IDs your tag sent, compare them in a spreadsheet. Prefixes, leading zeros, and casing all break the join.
4. Fix your units in writing. Decide dollars-with-decimals and confirm the tag agrees. This is the one step where an error costs real money.
5. Send net value, and use NULL deliberately. Post-refund revenue in the value field; 0 for a full refund; NULL for records you do not want touched. Any number overwrites permanently.
6. Map GCLID and hashed email. Google recommends both. One identifier is the minimum; two is what makes unmatched rows attributable instead of orphaned.
7. Schedule daily uploads, inside 24 hours. That is Google’s guidance for Enhanced Conversions matching and bidding. A weekly batch works for reporting and badly for bidding.
8. Set a reminder for day 13. Compare Google Ads conversion count and value against your backend’s totals for the window. Off by more than a few percent, disconnect and fix the mapping — an automated alert summary is a symptom list, not a diagnosis.

For a freelancer running eight client accounts, every step above multiplies by eight, and step three cannot be templated — each backend names its orders differently. Budget setup time per account, not once.

Which dates should be on the calendar before you connect?

• September 22 – October 6, 2026 — connect this week and the trial closes in early October, seven weeks clear of peak season.
• October 1, 2026 — Google Local Services Ads begins charging for missed calls, as reported in August. Test both changes at once and you will not know which moved cost per lead.
• October 1, 2026 — Microsoft Advertising’s removal of Max CPC takes effect, per its reported timeline. If you mirror campaigns across engines, keep the measurement change and the bidding change in separate weeks.
• November 12, 2026 — Pinterest’s synthetic media ad policy is reported to take effect; unrelated, but competing for the same two hours.
• November 27 and November 30, 2026 — Black Friday and Cyber Monday. Connect after roughly November 13 and the trial flips to biddable during your highest-CPM fortnight of the year. Do not.

Frequently asked questions

Do I need the Data Manager API to use multi-source conversions?

No. Google’s recommended path is a direct connection through Data Manager, configured by editing your conversion action and choosing “Connect another data source.” The Data Manager API is a separate route requiring allow-list access, and only pays off if you manage many accounts or your backend has no supported connector.

Will this double-count my sales?

Only if you set it up in a way that invites it. Google deduplicates between the tag and your upload inside a single conversion action, using the transaction ID, and does not deduplicate across two actions. The two ways to double-count: running a new supplemented action alongside the original in the same campaign goals, or sending transaction IDs in a format that never matches the tag’s.

Can I use this if my conversions come from Google Analytics?

Not as-is. Google’s documentation restricts the feature to website conversion actions implemented manually via the Google tag or Google Tag Manager, and specifically excludes imported Google Analytics conversions and URL-based actions. Migrating from a GA4 import to a native tag conversion is a real project with its own reporting discontinuity — plan it as one, not as a checkbox.

What should I send if a customer has not paid yet?

Send NULL in the value field. Google treats NULL as “do not update,” leaving the tag’s original value intact until you have a final number. Sending 0 is different: 0 is a legitimate value meaning a fully refunded order, and it permanently overwrites whatever the tag recorded. NULL versus 0 is the most consequential mapping choice in this setup.

The short version

Multi-source conversions is sold as a recovery tool and should be bought as a pricing tool: under a few hundred conversions a month the recovered volume is noise, but your order database knows what a sale was worth and your tag never will. Get the order ID format and the currency units right, or you will teach Smart Bidding a lie it spends your budget defending.