Delivery health and retries
The delivery-health dashboard shows the last seven days of deliveries per destination, with the reason for any failure — auth error, rate limit and so on. Failed deliveries retry automatically with exponential backoff, and any conversion can be re-fired by hand.
Conversion tracking fails quietly by nature. A destination stops accepting your events and nothing announces it — you simply see fewer conversions and assume demand dropped. The delivery-health view exists so that never happens silently.
What it shows
- Per-destination delivery status over the last seven days.
- Counts of delivered and failed events.
- The reason for each failure — authentication error, rate limit, rejected payload and so on.
Automatic retries
Failed deliveries retry automatically with exponential backoff, which clears transient problems — a rate limit or a brief outage — without any action from you.
When to step in
- Authentication errors
- Will not fix themselves. A credential has expired or been revoked at the destination — reconnect it.
- Persistent rate limits
- Suggest volume beyond the destination's allowance. Check your account limits at that platform.
- Rejected payloads
- Usually mean a configuration mismatch at the destination, such as a pixel or measurement ID pointing somewhere unexpected.
The underlying data is never lost
Raw conversion records are stored in AdProtektor whatever happens downstream, so a destination outage costs you delivery — not the record. Once fixed, affected conversions can be re-fired.
Manual re-fire
Any conversion can be re-fired by hand once the underlying problem is resolved, so a period of failed delivery can be repaired rather than written off.
Frequently asked questions
How will I know if delivery is failing?
The delivery-health dashboard surfaces it directly. Checking it after any change to a destination — a new pixel, a rotated credential — is a good habit.
Do retries risk duplicate conversions?
No. Events carry a stable event ID, so a destination that has already seen one de-duplicates the retry.
Related articles
ConversionOS destinations
Connect Meta Pixel and Conversions API, Google Analytics 4, and Google Enhanced Conversions for Web.
Setting up ConversionOS
Enable the add-on, connect a destination, and confirm conversions are arriving.
Refunds and settlement delay
Hold conversions briefly before firing so cancellations do not reach your ad platforms, and fire compensating events for refunds.
