A brand sourcing products in China may commission its advertising, storefront and order-data work from different partners. When a data provider adds backend purchases to Google Ads, a successful upload answers only a transport question. It does not yet establish whether two records represent one purchase, or whether distinct purchases have accidentally been merged.
Before increasing the video budget on the strength of those signals, buy an explanation of purchase identity. ONCE proposes a one-purchase, two-path acceptance method: demonstrate that the same purchase remains one event while separate purchases retain their identities.
A current capability has a specific scope
Google's October 13, 2026 Demand Gen announcement provides the research context: stronger first-party data connections are becoming part of campaign operations. It does not establish when multi-source conversions first launched, nor does its average performance claim predict a result for your brand.
The current multi-source conversions FAQ is labeled beta. It supports coded Google Ads website conversion actions, not imported Google Analytics conversions through the same setup. Its matching operates within one conversion action using consistent transaction IDs. Do not assume an account-wide deduplication service across unrelated actions.
The FAQ also describes an initial 14-day trial for the added source, followed by automatic bidding eligibility. For procurement, schedule verification and an owner review at implementation rather than leaving acceptance until the monthly report. This timing belongs to the documented beta mechanism, not every Google Ads integration.
Separate event identity from bidding use
Google's transaction-ID guidance calls for a unique dynamic identifier per purchase, consistent between tag and backend submissions. Prefixes or spaces can disrupt matching; a fixed identifier shared by different purchases can instead cause undercounting. The identifier must not contain personally identifying customer information.
Have the business owner and provider agree when a purchase exists, where its identifier originates, which account and action receive it, and how currency, tax and shipping are represented. A developer should implement an agreed commercial definition rather than invent one while configuring a connection.
Bidding use needs a separate check. Google's primary/secondary guidance says secondary actions are normally observational, but a secondary action in a custom goal can be used for bidding. A label saying “secondary” is therefore insufficient evidence of isolation. Review the goals actually used by the campaign.
The ONCE one-purchase, two-path acceptance method
This is a proposed purchasing framework, not an official product name or an ONCE client test. An authorized data team should perform appropriate controlled verification without introducing invented purchases into live optimization.
| Scenario | Evidence to request |
|---|---|
| One purchase arrives through the tag and backend | A sanitized business reference, both transmitted IDs, target action and handling status can be reconciled. Two successful uploads alone are insufficient. |
| The same purchase triggers again or is retried | The record retains its original identity, with handling or diagnostic evidence explaining why it is not another purchase. |
| Two different purchases occur | Different identifiers are captured. A fixed placeholder has not collapsed real purchases into one. |
| An identifier is missing or inconsistent | The discrepancy, owner and resolution are recorded. Unknown handling remains unresolved rather than being hidden under “connected.” |
For an illustrative example, suppose the store uses SHOP-A-104, the tag sends that reference and the backend sends only 104. The shared digits do not prove a successful platform match. Inspect the actual mapping and applicable mechanism. A separate purchase, SHOP-A-105, must keep its own identity. These are invented references, not customer records.
The acceptance pack can contain sanitized samples, sending records, configuration, diagnostic findings and unresolved exceptions. A frontend request establishes what was sent; diagnostics help explain processing. Neither is a complete financial ledger. Store totals and advertising conversions cover different populations, so forcing their aggregates to equal one another is not a valid universal test.
Counting one per click is a different decision
Google distinguishes counting every conversion from counting one per ad click. The latter is not the same operation as identifying a repeated order. If one click leads to two independent purchases, a one-per-click rule can suppress genuine purchasing activity. Choose the business counting objective first; do not use “One” as a universal duplicate fix.
Commission acceptance and maintenance as explicit work
Break the proposal into identity and field mapping, implementation, controlled verification, and ongoing exception handling. A quote covering only the first two needs an explicit owner for the rest. A green connection indicator does not specify a maintenance service.
Request a final acceptance statement identifying the actions and sources covered, the remaining gaps, who owns unmatched records, and what triggers revalidation. Adding a storefront, changing order prefixes or replacing a plugin can require another check. Record when the additional source enters bidding and who will review its readiness before then. Absence of a warning is not a guarantee about every future purchase.
A small brand may reasonably begin with mapping and a limited implementation if it cannot yet support a broader verification exercise. A multi-store operation needs agreement about identifier ownership and changes before expanding its connections. Scale the service to the actual chain of responsibility rather than the number of tools connected.
Give the creative team usable conclusions, not customer records
Correct event handling reduces one source of error in the feedback used to commission content. It does not prove incremental sales from a video or guarantee better bidding. Creative decisions still need a suitable comparison and a clear statement of what changed in the product demonstration, opening or claim.
A production partner usually needs version-level summaries, measurement scope and known gaps. It does not need buyer identities or an entire order database. Purchase identity resolves transaction records; creative identity locates a film. An authorized team can connect those tasks without making the production asset library a copy of the customer database.
For the separate question of whether partner benefits justify another production order, see ONCE's content monetization and production-budget analysis. In this case, the prerequisite is narrower: establish what the purchase signals mean before turning them into a new content brief.
For ONCE's long-term workflow design, the useful asset is a record of the conditions under which creative feedback was produced. That is a proposed operating direction, not a claim that ONCE provides a live data integration or has measured a client performance gain.
Sources and scope
Checked October 30, 2026: Google's October Demand Gen announcement (October 13); Google Ads Help's multi-source conversions beta FAQ, transaction-ID guidance, primary and secondary action guidance, and conversion counting options (help pages do not display publication dates).
The acceptance framework and example are ONCE analysis. No client account was accessed or integration implemented for this article. The original AI cover illustrates a business process; it is not client project photography.
