OneView’s global queue system ensures no events are lost due to temporary network issues or endpoint failures. No action required.
What are Retries?
Retries automatically resend failed conversion API requests when temporary network issues or endpoint failures occur. OneView’s stateful architecture guarantees that once an event is accepted, it will eventually reach its destination, even during extended outages.Understanding the problem:Traditional tracking solutions lose data permanently when:
- Server timeouts occur
- Temporary connectivity issues drop events
- Endpoint unavailability blocks conversion data
- No retry mechanism exists for failed transmissions
How Retries work
OneView operates a high-throughput global queue system that automatically retries failed requests with exponential backoff:| Scenario | Behavior | Result |
|---|---|---|
| Network timeout | Request queued, retried automatically | Event eventually delivered |
| Endpoint unavailable | Retries continue for up to 7 days | Event delivered when service recovers |
| Temporary rate limit | Backoff applied, retry scheduled | Event delivered after backoff period |
| Permanent failure | Marked as fatal error, retries stopped | Self-healed, unless configuration fix is needed |
Once an event is accepted by OneView, you’re guaranteed that it will eventually reach its destination, even if downstream services experience extended outages (up to 7 days).
Retry behavior
OneView classifies errors and applies appropriate retry strategies:| Error Type | Retryable | Behavior |
|---|---|---|
| Transient errors | Yes | Automatic retries with exponential backoff |
| Rate limit errors | Yes | Retries with backoff to respect rate limits |
| Fatal errors | No | Retries stopped, requires configuration fix |
| Skipped events | No | Intentionally skipped (e.g., consent not granted) |
Retry window:OneView retries failed requests for up to 7 days. This covers most temporary outages while preventing indefinite retry loops for permanent failures.
Benefits
No data loss Unlike stateless proxy solutions (such as GTM Server-Side), OneView’s stateful architecture ensures events are never lost due to temporary network issues or endpoint failures. Consistent reporting By guaranteeing delivery, OneView ensures your marketing platforms receive all conversions, preventing discrepancies between your dashboards and platform reports. Automatic recovery No manual intervention required. OneView automatically handles retries, backoff, and error classification without any configuration.Common questions
How long does OneView retry failed requests?
How long does OneView retry failed requests?
OneView retries failed requests for up to 7 days. After this period, permanent failures are marked as fatal errors and require configuration fixes.
What happens if an endpoint is down for more than 7 days?
What happens if an endpoint is down for more than 7 days?
After 7 days, OneView stops retrying and drops the event. Some Conversion APIs (such as Meta), do not accept data past 7 days prior.
How does this differ from browser-based retries?
How does this differ from browser-based retries?
Browser-based tracking cannot guarantee retries because:
- Users may close the browser before retry completes
- Network conditions may prevent retry attempts
- No persistent queue exists to ensure eventual delivery
Can I see retry attempts in logs?
Can I see retry attempts in logs?
Yes, while the attempts are ongoing. When the event is delivered, you will see the final result in your reports.