Features How it works Pricing Guides
Console
← Back to playbooks
Deliverability Published on June 28, 2026

How the Zero-Loss Retry Queue Protects Your Ad Data

Learn how PostbackFlow uses an automated queue with exponential backoff to guarantee 100% conversion delivery to Meta CAPI and Google Ads.

The Headache: Unstable Ad Network APIs

When you run massive campaigns on Meta (Facebook), Google, or TikTok, accurate pixel feedback is critical. If your ad platform does not know when a conversion occurs, its optimization algorithms will stall, leading to higher Cost Per Acquisition (CPA) and wasted budget.

However, ad network APIs are not 100% reliable. They frequently experience:



Most standard trackers use a single-fire postback mechanism: when a conversion occurs, they call the ad network API. If the ad network responds with an error (e.g., HTTP 500 or 503), the conversion is lost forever. Your pixel misses the data, and your campaign optimization degrades.

PostbackFlow solves this with the Zero-Loss Retry Queue.

---

How the Retry Queue Works

When a conversion postback arrives from your affiliate network, PostbackFlow processes it immediately and triggers the Ad Platform API forwarder.

If the forwarding attempt fails (any HTTP status code other than 200/201, or a timeout):
1. Fallback Capture: The system captures the conversion payload and registers it in our database retry queue.
2. Cron Scheduler: A background cron worker (retry_worker.php) runs automatically every 60 seconds.
3. Exponential Backoff: The worker scans for pending retries and attempts to resend the conversions. It uses an exponential backoff schedule:
* Retry 1: 1 minute after failure.
* Retry 2: 5 minutes after failure.
* Retry 3: 15 minutes after failure.
* Retry 4: 60 minutes after failure.
* Retry 5: 240 minutes (4 hours) after failure.
4. Permanent Log: If all 5 attempts fail, the conversion status is set to failed and logged on your dashboard so you can review credentials.

---

Technical Setup: Fully Automated

You do not need to configure anything. The retry queue is built into the core PostbackFlow architecture and operates silently in the background.

To verify forwarding statuses:
1. Open your Dashboard or Reports page.
2. View the Conversions table.
3. Check the status indicator:
* received / sent: Conversion recorded and forwarded successfully.
* pending / retrying: Forwarder failed on first try and is scheduled for the next retry interval.
* failed: Delivery aborted after 5 retries (check API credentials under Settings).

---

Expected Results & ROI Impact