# Remove Refunds From Google Ads Conversions _Remove refunds from Google Ads conversions: restate vs retract, and the 7-day window that decides whether it retrains Smart Bidding or only fixes reporting._ Canonical: https://jamesdnichols.com/guides/remove-refunds-google-ads-conversions/ · by James Nichols · published 2026-07-18, updated 2026-07-19 To remove a refund from Google Ads conversions you adjust the original conversion, matched by its order ID: restate the value down for a partial refund, or retract it for a full return or cancellation. **But the honest headline is timing: an adjustment only retrains Smart Bidding if it lands within about 7 days of the original conversion.** After that, up to roughly 54 days, you are correcting your reports and your audiences, not the bidder. ## Does removing a refund actually change your bidding? Inside a short window, yes. Google reads a conversion adjustment for what it calls "autobidding readability" for **about 7 days** after the conversion is first recorded. Restate or retract in that window and value-based strategies (Target ROAS, Maximize Conversion Value) relearn on the corrected number. :::stat{figure="7 days" label="the autobidding-readability window"} Adjust within it and Smart Bidding relearns; adjust after it and the bidder keeps optimizing on the original value. Google Ads Help, read 2026-07-19. ::: Miss the window and the adjustment still does real work, just not where most people assume. It updates your reporting columns and your remarketing audiences, so you can measure campaign, ad group, asset, and keyword performance on values that are net of refunds. That lets *you* tune strategy. It does not change how Smart Bidding bids on its own. :::example{caption="Same adjustment, two different jobs"} | When you adjust | What Smart Bidding does | What your reports do | |---|---|---| | Within ~7 days | Relearns on the corrected value | Corrected | | After ~7 days (up to ~54) | Ignores it, keeps bidding on the original | Corrected | ::: One caution on the outer number: Google's own Help articles contradict each other, one saying 54 days and the other 55. The 7-day bidding window is the one that actually constrains you; do not build a job that fires on the exact outer deadline. ## Cancellations and returns are not the same problem The 7-day window turns a timing detail into the whole decision, because cancellations and returns arrive on different clocks. A **cancellation** usually happens fast, within hours or a few days, often before the 7-day window closes and sometimes before the order even ships. Retract it in time and the bidder sees it. A **return** runs on your return policy, 14 or 30 or 60 days. That is almost always past 7 days. Restating it does what operators ask for, to "automatically remove conversions that end up refunding" — but only in your reports; the bidder sees the change too late to act on it. For a store with a normal return rate, that is the real constraint, not whether the plumbing exists. ## The money is already gone either way Getting the conversion out of Google is damage control, and it is worth being clear about what it does not recover. A refund is never free. On the refund the processor keeps its gateway fees, and you pay the support and fulfillment labor to process it by hand. If the order was already picked, pulled, or shipped, add the cost of stopping or recalling it, plus restocking or return shipping. Removing the win from your ad account changes what Google learns, at best, for 7 days. It gives none of that money back. :::sources - Order ID | Your store's order record; the key Google matches adjustments on - Refund or return date | Your refund report — this is what tells you which side of the 7-day window you are on - Gateway fees kept | Your processor statement; refunds rarely return the original transaction fee - Handling and recall cost | Support time, pick-and-pack labor, and any return shipping or restock ::: ## Restate, retract, and the value floor The two moves are Google's own vocabulary. **Restate** changes a conversion's value and keeps it counted, for a partial refund or a true-cost correction. **Retract** removes the conversion and sets its value to 0.00, for a full return or a cancellation. A retracted conversion is locked; later adjustments to it are ignored. That 0.00 is the floor on paper. An operator whose order lost money often wants more than the win removed; they want to "send refunds back as negative conversion values," so the bidder learns the order was worse than nothing. Google's model does not offer that. :::stat{figure="−$20.83" label="a restated value the Ads API accepted"} One real order, restated below zero and uploaded in 2025. Accepted without an error — but acceptance is not effect, and past 7 days it moves no bid regardless. ::: So the paper floor and the accepted upload disagree, and the disagreement is worth stating plainly rather than resolving with a claim nobody can check. ## The fix is upstream of the refund Chasing refunds after the fact fights the 7-day clock and loses most of the time. The lever that beats it is sending the right number *before* the clock starts: predict the return rate at checkout and feed a net, margin-aware value with the conversion, so the bidder is already optimizing on what the order is really worth. That is the [break-even math](/guides/break-even-roas/) applied at fire time instead of clawed back later. Whether your account is leaking this way, and by how much, is the first thing I check: see how the scan works. ## Quick answers **Does removing a refund from Google Ads conversions change Smart Bidding?** Only if you do it within about 7 days of the original conversion. Google reads conversion adjustments for "autobidding readability" inside that window; after it, the adjustment still corrects your reporting columns (up to roughly 54 days), but Smart Bidding keeps optimizing on the original value. So a restatement at day 40 fixes your dashboard and does nothing to your bidding. **How do I remove a refund from a Google Ads conversion?** You adjust the original conversion, matched on its order ID. For a partial refund, restate the value down to what the order is really worth. For a full refund, return, or cancellation, retract the conversion, which sets its value to 0.00 and removes it from your count. Both upload the same way you uploaded the conversion — and both only reach the bidder inside the 7-day window. **Do cancellations and returns behave differently here?** Yes, because of timing. A cancellation usually happens within hours or days, often inside the 7-day window, so retracting it can still reach the bidder. A return runs on your return window — 14, 30, 60 days — so it almost always lands after 7 days, which means restating it cleans your ROAS reporting but teaches the bidder almost nothing. **What is the difference between restating and retracting a conversion?** A restatement changes the conversion value but keeps the conversion in your count; use it for partial refunds and true-cost corrections. A retraction removes the conversion entirely and sets its value to 0.00; use it for full returns and cancellations. A retracted conversion is locked, and further adjustments to it are ignored. **Can a Google Ads conversion value be negative?** Not in what Google documents. A retraction takes the value to 0.00, and Google states that once a conversion is retracted or restated to zero it "cannot be adjusted further" — so 0.00 reads as the floor. One real −$20.83 restatement was uploaded through the Ads API and accepted without an error, but acceptance is not effect, and outside the 7-day window it changes nothing in the bidder regardless. ## Where these numbers come from The 7-day window, from Google's own docs (Google Ads Help 7686280 and 7686447, read 2026-07-19): a conversion adjustment is read by automated bidding only within about 7 days of the original conversion ("autobidding readability"); after that it updates reporting only. The two Help articles then contradict each other on the outer reporting window — one says 54 days, the other 55 — so don't build a job that fires on the exact deadline. One real order's restated value came out to −$20.83 after the refund and its true costs, and Google accepted the upload through the Ads API in 2025. Stated as acceptance only: the value went in without an error. It is not a claim that Smart Bidding used it, and after the 7-day window it could not have. Acceptance and effect are different things. I ran a daily restatement on my own store in 2025 — daily precisely because of the 7-day cliff: catch the fast reversals in time to reach the bidder, and correct the reports on the rest. Operator experience, past tense. The refund cost is real even when the adjustment never reaches the bidder: on a refund the processor keeps its gateway fees, and you pay the support and fulfillment labor to process it. If the order was already picked, pulled, or shipped, add the cost of stopping or recalling it, plus restocking or return shipping. My own operation, stated as operator experience, not a measured figure. "does Smart Bidding learn from refunds" had zero indexed keyword volume and zero Reddit threads across four phrasings in twelve months, measured 2026-07 — this page targets that gap in the record, not search demand. Run it or hand it off. Everything above is the method, free. Prefer it done for you? The scan is read-only keys in, a dollar figure on every leak out, in a week: https://jamesdnichols.com/#offers. Or score your margin visibility first: https://jamesdnichols.com/assessment/.