Remove Refunds From Google Ads Conversions

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.

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.

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.

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.

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 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.