Conversion measurement · Digital marketing

Zero value and zero conversions are different outcomes

A Data Manager API restatement can lower the value of a canceled order to zero. Google's migration guide says its conversion count remains one.

  1. Value correctionA matching transaction ID lets Data Manager API replace the recorded value without adding a conversion.
  2. Count removalThe API does not support the separate retraction operation that sets both count and value to zero.
  3. Migration testUse a canceled-order case before switching uploads. A partial refund alone cannot prove the cancellation path.

Suppose a lead is recorded as one offline conversion worth $100 and the order is later canceled. A value correction and a retraction may both end at $0, but they answer different questions. Google's current Data Manager API migration guide says its IngestEvents adjustment can restate value while the conversion count stays the same. It also says the Data Manager API does not support retractions. If your team reports cost per conversion or optimizes on a conversion count, changing value alone does not implement the intended cancellation.

This distinction matters now because Google has restricted new offline-conversion uploads through the Google Ads API since June 15, 2026 for developer tokens without qualifying earlier use. The Data Manager API is the primary new upload path. That shift does not make its operations identical to the older API's adjustment types.

The canceled order has two counters

Keep this example explicitly hypothetical. Initially, one order contributes 1 conversion and $100 value. A Data Manager API adjustment with the same transaction ID and a new $0 value produces 1 conversion and $0 value under Google's API contract. A separate Google Ads API RETRACTION, where available, negates both count and value: 0 conversions and $0 value. These are possible semantics of two different operations, not measurements from a live account.

Hypothetical $100 conversion: Data Manager API restatement to $0 leaves one conversion; Google Ads API RETRACTION removes the count, leaving zero conversions and zero value.
The two counters are separate: a value restatement changes the amount, while a retraction changes whether the conversion counts. Hypothetical example based on Google's Data Manager API migration and adjustment guides, checked 27 September 2026.

A Google Ads API retraction explicitly sets count and value to zero. Google Ads Help's spreadsheet instructions also offer a RETRACT adjustment and describe a zero restatement as withdrawn from reports. Those instructions refer to the file-based Google Ads adjustment workflow. The Data Manager API developer guide explicitly says its zero-value restatement retains the count. Do not transfer the spreadsheet or Google Ads API rule to IngestEvents merely because the word “adjustment” appears in all three places.

For a partial refund, the business event usually still exists and its remaining value changes; our partial-refund example explains why the new value is the order's remaining total, not just the refunded amount. A fully canceled order raises a second requirement: should the conversion count disappear? Decide that with the owner of the KPI before treating a $0 value as completion.

A matching transaction ID adjusts; an unmatched one creates

Google's Data Manager API adjustment reference says a request with the same transactionId, destination and conversion action is treated as an adjustment. For a matched conversion, the new value replaces the previous value without incrementing the count. The endpoint does not need a separate adjustment-type field. This is useful for correcting values, but it does not introduce a hidden retraction option.

A mistyped or changed transactionId is more serious than a failed adjustment. Google says an unmatched event is handled as a new conversion upload, with attribution attempted from its identifiers. In the hypothetical ledger, the intended state “one order corrected to $0” could therefore become two separate records. A request returning successfully is not proof that it matched the original. Preserve the original action and transaction ID, log the intended correction, then reconcile the count and value after processing. This is a route-specific warning, not a claim that any particular account double-counted.

The identifier must survive earlier data handling, too. Our order-ID precision test shows how a numeric JSON ID can lose identity before an analytics tag fires. That article does not test Data Manager API; it illustrates why an exact transaction key needs a lossless path from order system to adjustment job.

Test the cancellation path before switching uploads

Start from the business rule

Write down which cases should change value only and which should change both value and count. A discounted or partly refunded order often belongs in the first group. A canceled reservation or invalid lead may belong in the second, depending on your conversion definition. A vague instruction to “send zero” hides the choice.

Check the actual route and account owner

Inventory the upload method used by each conversion action: Data Manager API, a qualifying legacy Google Ads API integration, a scheduled file import, or a manual Ads upload. Do not assume the feature set crosses routes. Google's migration guide also changes the destination-account contract: the Data Manager API operating_account must be the Google Ads conversion customer that owns the conversion action, whereas the older API allowed some parent or descendant account IDs. An incorrect destination can make a seemingly sound adjustment design fail earlier.

Rehearse one of each outcome in a controlled action

  • Original. Record a distinct test transaction ID, action owner, upload route, one conversion and a nonzero value. Keep this isolated from production bidding if your account policy allows a test action.
  • Value change. Send a same-ID correction and verify value changes while count remains as documented for Data Manager API. Check the response, processing and account report; do not use HTTP success alone as the outcome.
  • Cancellation. State whether count must become zero. If the Data Manager API route cannot perform that operation, stop the migration decision there and confirm a supported, eligible adjustment route with your Google Ads implementation owner or support. Do not fabricate a second event or assume $0 is a retraction.
  • Mismatch guard. Run a deliberately different test ID only in a safe, isolated environment if allowed, and confirm that the job does not send an unmatched correction as a real new conversion. In production, reject unknown IDs before upload.

The June 2026 restriction is not a universal shutdown of the Google Ads API. Google's access notice says inactive developer tokens are restricted for offline uploads; its developer announcement says prior adopters can continue while integrating with Data Manager. Eligibility and the supported retraction route need to be verified for the specific account and action. Google's spreadsheet adjustment path is another documented surface, but using it as part of a programmatic migration requires its own operational design and test.

Keep a count/value reconciliation for a complete processing window. Compare the source order ledger, accepted adjustments, Google Ads conversion count and conversion value for the same conversion action and dates. A zero-value canceled order remaining in count changes CPA-type interpretation even if ROAS value looks corrected. Conversely, a failed or unmatched correction can change the value ledger in a different way. Our custom-goals analysis explains why the action's role in bidding should also be checked rather than inferred from a label.

This article interprets Google's documentation as checked 27 September 2026; it is not a live API or Ads-account experiment. The narrow, reliable rule is that Data Manager API value restatement cannot be counted on to retract an offline conversion. If cancellation must erase the count, make that missing operation an explicit migration requirement rather than a silent spreadsheet assumption.

Questions about Data Manager conversion adjustments

Does a $0 Data Manager API adjustment remove the conversion count?

No. Google's Data Manager API migration guide states that it can restate the value while the conversion count remains unchanged; retractions are not supported by that API.

What if the transaction ID is wrong?

The adjustment reference says an unmatched transactionId is treated as a new conversion upload. Validate the original ID, destination and conversion action before sending a correction.

Is the Google Ads API completely unavailable after June 2026?

No. The restriction applies to developer tokens without qualifying prior offline-upload use. Eligibility and the exact supported route must be checked for the integration.

Why does Google Ads Help say a zero adjustment removes a conversion?

That Help page describes the file-based Google Ads adjustment workflow. The Data Manager API developer guide explicitly states a different count outcome for its value restatement. Check which surface your job actually calls.

Official Google sources

Primary documentation checked 27 September 2026