Separate refunds from missing conversion events

A campaign report shows fewer dollars of conversion value on Friday than it did on Thursday, even though the order count looks right. Before investigating the conversion tag, check whether the two exports describe the same orders at different points in their lives. A refund can lower the value of an order that was tracked correctly. A missing event leaves a different trail and calls for a different fix.

Compare the same order before comparing totals

Keep the original order identifier, its event time, currency, captured value and reporting action in a reconciliation table. Join the refund records to that order identifier through your billing system. Separately retain the platform receipt for the original conversion if the platform provides one. A row is easier to explain when you can see the order, the event sent to the ad platform and the later adjustment in one place.

Pick a simple example. A shopper pays $120 for an order, returns one item and receives a $35 refund. Under a reporting policy that deducts successful refunds from captured value, the revised value of that order is $85. The order can still count as one accepted purchase. A missing purchase event would instead leave an accepted order without a matching original conversion receipt. The missing-event case warrants checking event delivery and eligibility before attempting to adjust any reported value.

Keep refund state and reporting state in separate fields

A refund request can exist before the refund has completed. The Stripe refund documentation describes pending and failed refunds as well as full and partial refunds. If your report uses completed refunds, keep pending items visible with their current state. Add the amount to the calculation once the event has succeeded. Keep the currency with the amount throughout the join and use a stable refund identifier to prevent an event delivery retry from being counted twice.

The amount used for conversion reporting may also differ from the amount on a payment receipt. A merchant might report a subtotal that excludes tax and shipping. Keep the original definition when calculating a refund adjustment. If a partial refund includes a delivery charge that the original conversion value excluded, separate that portion with the same rules used for the first report. Otherwise two correct systems will disagree for a reason unrelated to tracking.

Check what the ad platform accepted

For eligible Google Ads conversions, the Google Ads API documentation on conversion adjustments distinguishes restating an existing value from retracting a recorded conversion. Use the identifier required for the original conversion action. In the $120 example, a restatement after the $35 refund carries the new value of $85 under the stated reporting policy. A retraction fits a case where the recorded conversion no longer meets the rule for a counted outcome.

Record the response for the specific adjustment row. A job that completed its upload can still contain a row that the platform rejected. If the original conversion is missing, verify the order identifier, action and original acceptance before trying another adjustment. Put an unresolved event into the investigation queue with the original receipt and the exact error. That gives the next reviewer a place to start without sending a new purchase event for an order that may already be counted.

Rebuild a small comparison with both versions

Export the same mature date range from both systems and save the time of each export. Preserve an original value column and a current value column for each accepted order. Record the first conversion timestamp and the refund or cancellation timestamp separately. Check several partial refunds and one full cancellation against the platform responses. Include a normal order with no adjustment so the comparison shows whether a change also affected untouched records.

When those rows reconcile, summarize the remaining exceptions using the categories that drive different actions. The FroggyAds conversion-tracking guide describes the event records, duplicate checks and accepted backend outcomes that support a reconciliation. Hand off a small table with the order identifier, prior value, revised value, currency, reason and platform status. The campaign manager can then see whether a lower reported value came from a later refund, a missing event or a request still waiting for a platform decision.