Refunds and settlement delay
A settlement delay of 0–60 minutes allows cancellations to arrive before dispatch. After delivery, ConversionOS records refund requests and schedules follow-up events for Meta CAPI, GA4 and Google Ads. Check each destination for processing results.
On this page
Not every completed order stays completed. Without handling, cancellations and refunds leave your ad platforms optimising toward revenue that no longer exists.
Settlement delay
Set a delay of 0 to 60 minutes before a conversion is dispatched. A supported cancellation received while the event is still waiting marks it so delayed workers skip it. A delivery already in progress needs the refund follow-up described below.
Choosing a delay
Choose a delay based on your actual cancellation patterns. A longer delay gives more time for supported cancellations to arrive, but also delays feedback to your destinations.
Refunds after the window
Later refund requests are stored before the order is marked cancelled. Queue outages and original deliveries that finish after cancellation are handled by automatic reconciliation. Each destination has its own processing rules and reporting limits.
- Meta CAPI
- AdProtektor currently sends a negative-value Purchase. Check Meta diagnostics and reports; this event is not proof that previously reported revenue was reversed.
- GA4
- A refund event with the original transaction ID. HTTP receipt alone does not confirm that GA4 processed it.
- Google Ads
- A full conversion retraction matched to the original event ID and conversion action. An accepted adjustment can remain pending while Google processes it.
Your own data stays intact
AdProtektor keeps the cancellation request and delivery audit. A cancelled conversion is removed from conversion totals, while failed or pending destination follow-up remains separate from the order's cancellation status.
Frequently asked questions
Does a settlement delay hurt ad optimisation?
A delay postpones feedback to the destination. Choose it using your cancellation patterns and compare delivery and campaign results; the effect is not guaranteed to be negligible.
What if a refund happens weeks later?
A supported refund request is recorded, but destination time limits, integration configuration and delivery outcomes still apply. Check the delivery audit and destination reports before treating an old purchase as corrected.