What a $40 return does to a $120 Google Ads conversion
Three orders show how a partial return, cancellation, and wrong zero adjustment change Google Ads purchase reports.
The return portal says $40 refunded. Google Ads still has a $120 purchase. Both can be faithful records of the same order at different moments. The mistake is to treat the return as a second, negative purchase—or to erase the first purchase when the customer kept the rest.
The useful question is not “Was there a return?” It is what is true of this purchase now? If the customer kept $80 of merchandise, the purchase is still one conversion with a different value. If the whole order was canceled, the purchase may no longer belong in the conversion count. And if the adjustment itself was wrong, the next move depends on whether the conversion still exists to adjust.
Here is a small ledger for those three situations. The orders, dates, and dollar amounts are invented examples, not account results. Assume a website Purchase conversion action, one recorded and attributed conversion per order, and merchandise-only value excluding tax and shipping. The commerce order and refund records are the authority for what the customer retained. The timestamps use Google Ads’ accepted spreadsheet format, yyyy-MM-dd HH:mm:ss-0400 (Eastern daylight time). In a real account, use the original action’s value policy and actual transaction records.
The ledger: three orders, three different endings
1. One item comes back; the purchase stays
Order R-104 · original purchase: $120
| When | The record that knows | What to send or expect |
|---|---|---|
2026-08-04 10:15:00-0400 |
Completed order R-104: a $30 mug, $50 sweater, and $40 wrapped item; merchandise total $120. | Website tag records Purchase, order ID R-104, value $120. Expected starting position for an attributed order: 1 conversion / $120. |
2026-08-07 14:20:00-0400 |
Return and refund record for the $40 wrapped item, linked to R-104. The mug and sweater remain: $80 retained. | Submit RESTATE, order ID R-104, conversion action Purchase, adjustment time 2026-08-07 14:20:00-0400, adjusted value 80, currency USD. This is the new total value, not a −$40 adjustment. |
| After processing | Order ledger still says one completed purchase, net merchandise $80. | The attributed conversion remains 1; its value becomes $80. Reconcile the accepted adjustment with the affected report period after reporting has caught up. |
If a later $20 partial refund applies to one of the retained items, the next restatement is $60, with a later adjustment time. It is not $20, and it is not a second purchase. Google processes multiple adjustments by adjustment time. The row should describe the order’s current value. Google’s adjustment guidance and description of restatements make those rules explicit.
2. The whole order is canceled; the purchase leaves the count
Order R-105 · original purchase: $90
| When | The record that knows | What to send or expect |
|---|---|---|
2026-08-05 09:30:00-0400 |
Completed order R-105: $90 of merchandise. | Website tag records Purchase, order ID R-105, value $90. Starting position, if attributed: 1 / $90. |
2026-08-08 11:05:00-0400 |
Cancellation and full refund records close R-105 with no retained merchandise. | Submit RETRACT, order ID R-105, action Purchase, adjustment time 2026-08-08 11:05:00-0400. No adjusted-value field is needed for the retraction. |
| After processing | The order ledger says canceled and fully refunded. | The attributed conversion becomes 0 / $0. Check the adjustment result and the affected reporting period. |
The distinction is count, not just dollars. A restatement above zero changes value while preserving one purchase; a retraction removes both count and value. Entering a zero-value restatement also removes the conversion and blocks later adjustments. “We can always put a dollar back in later” is an expensive assumption to make with a website conversion. Google’s rules say a removed website conversion cannot be added back to reports by another adjustment.
This says something about the reported order event. It does not say that the original click had no influence on the person, or that a retained purchase was incremental. The adjustment makes a specific measurement more faithful to the business record; it does not answer a causal question the ledger cannot answer.
3. The adjustment was wrong; first ask whether the conversion survived
Order R-106 · original purchase: $100; actual refund: $30
| When | The record that knows | What to send or expect |
|---|---|---|
2026-08-06 13:40:00-0400 |
Completed order R-106: $100 of merchandise. | Website tag records Purchase, order ID R-106, value $100. Starting position, if attributed: 1 / $100. |
2026-08-09 16:10:00-0400 |
Refund record: $30 returned, $70 retained. | The correct instruction would be RESTATE to $70. Instead, an operator mistakenly submits RESTATE to $0, using R-106 and this adjustment time. |
| After the mistaken adjustment | The source order is still a $70 purchase. | Google’s zero-value rule removes the conversion: 0 / $0 in the attributed report, once processed. The business and ad ledgers now disagree. |
2026-08-10 10:00:00-0400 |
The refund record still proves $70 retained. | A later RESTATE to $70 for the same website conversion does not restore it. Do not mark the case reconciled because a second file uploaded quietly. |
If the mistake had been a positive value—say $7 instead of $70—a later restatement with a genuinely later adjustment time could correct the surviving conversion. Zero is different. Google says subsequent spreadsheet adjustments after retraction or a zero-value restatement can be ignored without an error. Its API also defines an already-retracted error, so the exact diagnostic depends on the upload route; neither a completed file transfer nor the absence of a visible complaint proves that the report is right. Google Ads Help and the API adjustment errors describe those edges.
Google describes a narrow re-upload route for some offline imported conversions under “every conversion” counting, treated as a new event with a changed timestamp and, when an order ID was used, a new unique ID. That is not a way to reopen R-106’s website conversion, and it carries duplicate-counting risk if treated as a casual repair. For this website case, record the discrepancy, identify the affected report and bidding history, and take the recovery question to the owner of conversion measurement rather than manufacturing a replacement purchase. Google’s retraction guidance separates the new offline event from the retracted one.
The four checks before you call an adjustment finished
Match the event. Keep the original order ID and exact conversion action name. For website conversions, the transaction ID must have been captured with the purchase. Use the adjustment time when the value changed or when the team learned of it, after conversion time and before upload, with a time zone. An adjustment cannot repair a conversion that Google Ads never recorded or attributed. Google recommends order IDs and says an unmatched conversion can produce a “not found” error. Adjustment preparation · About adjustments
Decide what survives. Positive retained value? Restate to the whole retained value, keeping one conversion. No purchase left to count? Retract, knowing that zero is a terminal state for that event. The order record decides this before the upload format does.
Check the submission, then the report. First inspect row-level import results or API partial failures. For the Google Ads spreadsheet adjustment route used in this ledger, Google advises waiting at least 24 hours after the original conversion before uploading. An adjustment submitted up to 7 days after the conversion is first recorded is within Google's window for automated bidding to read it; a later report correction should not be assumed to have reached bidding. Google's overall 54-day adjustment window limits how late an adjustment can be submitted for the original conversion. Check that limit before working an old return.
Then check the affected report period after ordinary conversion reporting has caught up. A completed upload is not that later report observation. In Google Ads, the Conversion adjustment segment can separate original count and value from later changes; Days to conversion or adjustment shows their timing. Those are aggregate report views, not a receipt that proves each order’s row has matched. Preparation and timing · Report segments · API partial failures
Reconcile on the right dates. Preserve the commerce order/refund record, the exact adjustment submitted, its row result, and the later report observation. Standard Google Ads conversion columns attribute conversions to the ad interaction date, while by conversion time columns can help when comparing with a commerce ledger. A refund posted on August 9 need not appear as a new August 9 purchase or a new negative order. Compare the same conversion action, attribution basis and mature period before declaring the books equal. Google’s reporting-date explanation
R-104 finishes at 1 conversion / $80. R-105 finishes at 0 / $0. R-106 is the open exception: the store still has a $70 purchase, while the mistaken zero adjustment left 0 / $0 in the ad report. A refund record, an upload receipt and a conversion report each tell part of the story; the order ID makes them answer to the same purchase.