Your shop shows a refunded order, but Google Ads still reports the original sale. Before you use that revenue to judge a campaign, check whether the refund has reached the conversion action behind the report.
Google Ads has conversion adjustments for correcting recorded sales. The right route depends on how the purchase was measured, whether the original transaction can be matched and whether you need to change its value or remove its count.
Start with a few confirmed orders. Establish what happened to the money, identify the measurement route, then verify a correction before automating the rest.
Start with the order and payment records
Choose a completed sale that was later refunded, a partial return and an unaffected order for comparison. Record the original order reference, payment outcome, refund amount and dates. Ask whoever manages measurement to identify the conversion action that received each original purchase.
A cancelled status alone is a poor basis for an advertising correction. Your review should establish whether payment was taken, whether money was returned and whether any part of the sale remains valid. Keep the customer-service decision separate from the reporting task.
Agree what your conversion value represents. If the original measurement excludes VAT and delivery, calculate the revised value on the same basis. Subtracting a refund that includes components absent from the original value can introduce another error.
For the wider reporting framework, see our guide to connecting conversion reporting with business outcomes.
Identify where the Google Ads purchase came from
Open the relevant conversion action and inspect its source and implementation with your tracking specialist. A name such as Purchase does not tell you whether the record came from a Google Ads website tag, Google Analytics or a backend upload.
Google’s current API workflow table lists website and uploaded click conversion actions for retraction and restatement, alongside the deprecated Salesforce type. GA4 purchase actions are listed separately. The practical implication is that you must establish support for your particular source before choosing an adjustment method.
If the purchase comes from GA4
Google documents GA4 refund measurement through a refund event tied to the relevant transaction_id, with item information recommended for item-level refund metrics.
That is evidence for the Analytics refund implementation. It does not establish that a native Google Ads adjustment has happened. Ask your specialist to demonstrate the result in the actual Google Ads conversion action used by the campaign. If the proposed route cannot adjust that source, document the reporting limitation before considering a measurement change.
Choose between restating value and retracting a sale
For the supported adjustment route, Google distinguishes two operations: restatement changes the recorded value while retaining the conversion count; retraction removes the conversion and its value.
| Outcome | Operation to consider | Expected result |
|---|---|---|
| Part of a purchase is returned | Restate | Keep the sale count and replace its value with the remaining value. |
| A purchase is fully returned and should no longer count | Retract | Remove the sale count and its value. |
| An order is delayed or awaiting a decision | Review first | Wait for an agreed business outcome before making a permanent correction. |
Google warns that retraction, or restatement to zero, prevents further adjustments to that conversion in this route. Treat those operations as final. Do not use them as temporary placeholders.
A partial refund needs the remaining value
As a worked example, suppose the original conversion value was £180 and a confirmed return reduces that same measured value by £60. The replacement value is £120. A further £30 return would leave £90.
Have a second person check the calculation before submitting a batch. Include discounts and any retained items in that review, using the value definition agreed at the start.
Match the original transaction exactly
Google’s transaction ID guidance requires a unique ID for each transaction and says it must not contain information identifying the customer. For website conversions, verify that the original tag actually sent the ID.
Ask your developer to show how the shop’s visible order reference maps to the value sent to Google Ads. A prefixed reference, an internal database number and the number printed in a customer email may look related without being identical.
Preserve the original matching value throughout the correction process. Avoid spreadsheet formatting that removes leading zeroes or changes long identifiers. If IDs were missing from historical website purchases, adding them now is a repair for future measurement; it does not prove that those earlier conversions can be matched.
Prepare a small file adjustment before scaling up
For the file route, follow Google’s current adjustment upload instructions. Download the conversion-adjustment template from Goals, Conversions, Uploads. Keep new conversions in a separate file. If a manager account owns conversion tracking, upload adjustments there.
Use the original order ID, exact conversion-action name, adjustment time and operation. A restatement supplies the replacement value and appropriate currency, such as GBP. Keep customer names, email addresses and phone numbers out of the file.
The same guide recommends uploading at least 24 hours after the original conversion. It states seven days after first recording for automated bidding to read the adjustment, and 54 days overall for adjustments. These are the published limits for this documented route; confirm the rules for your actual integration. Do not assume a late reporting correction will influence bidding.
Before applying the small batch, write down the expected outcome for each row and inspect any available validation results. Keep a copy of the approved input and the processing result. Resolve unmatched or rejected rows individually before expanding the upload.
Check the API route before automating refunds
Ask an integration supplier which adjustment mechanism it uses. File uploads and API connections can have different behaviour, even when both are described as refund tracking.
Google’s Data Manager API adjustment guide, updated on 21 October 2026, describes value restatement through a matching transaction ID and conversion action. The replacement value updates the existing conversion without incrementing its count. An unmatched ID is instead treated as a new conversion upload.
That matching behaviour makes an altered ID particularly risky. The API also requires a valid event with the required identifiers; the order reference alone is insufficient. Value updates for multi-source conversions are disabled during their initial 14-day trial.
Do not assume a value update reproduces the file route’s retraction behaviour. Require your supplier to demonstrate both the final value and final count for a full refund using your actual connection.
Give the process a clear owner
Once a small correction works, agree who approves refund outcomes, who maintains the connection and who investigates failed submissions. Give exceptions a visible queue rather than allowing them to disappear inside a monthly total.
Include repeated refunds against one order in the acceptance check. The process should carry the latest approved outcome through to reporting, with enough history to explain what was sent and when. Keep corrections outside an integration’s supported window in your business reporting and explain that remaining difference.
Verify the change in reports
An upload confirmation is one piece of evidence. Check the reported result too. Google’s conversion-adjustment reporting guide describes the Conversion adjustment segment, which separates original counts and values from subsequent changes.
Compare the chosen conversion action before and after processing. For the supported file route, a partial return should reduce value while retaining the sale count; a retraction should remove both. Confirm that the unaffected comparison order remains correct.
For a settled review, Google recommends ending the reporting period at least 30 days ago, or longer where the conversion window is longer. Use that mature comparison alongside checks on newly processed adjustments.
Annotate the date the correction process began in your own reporting. If recorded return on ad spend falls after refunds are included, investigate the underlying retained revenue before interpreting that change as deteriorating advertising. Keep budget and bidding decisions separate from the initial implementation check so you can assess each change clearly.
Make advertising decisions from sales you keep
A dependable setup needs an agreed value definition, matching transaction records, a supported correction route and evidence of the result. Start with those foundations before committing to a larger automation project.
If your shop, Analytics and Google Ads tell different stories after refunds, talk to BuzzBoost about checking your conversion measurement. We can help identify where the records diverge and define a practical repair.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
