CDPGuidesSupport
Event And Identity

Error Handling

Learn how Ours Privacy manages errors, retries failed destination requests, and ensures data reliability with multi-region ingestion.

Ours Privacy is designed to ensure high reliability and robust error management for your data. Event ingestion uses multi-region redundancy, and forwarding retries when an external destination fails.

Multi-Region Redundancy for Ingestion

Ours Privacy uses a multi-region setup to provide fault-tolerant ingestion of your events. This ensures that your data is reliably captured, even if a regional data center experiences downtime.

Retry Mechanism for External Destination Failures

When forwarding events to external destinations (e.g., Google Ads, Facebook Ads), Ours Privacy employs a robust retry mechanism to ensure data delivery, even if the destination is temporarily unavailable.

Retry Logic:

  1. Automatic Retries:
    • If a request to an external destination fails, Ours Privacy automatically retries the request.
  2. Exponential Backoff:
    • Retries are spaced out using exponential backoff to avoid overwhelming the destination.
  3. 48-Hour Retry Window:
    • Ours Privacy will continue retrying failed requests for up to 48 hours.
  4. Error Logging:

Common Failure Scenarios and Resolutions

ScenarioHow Ours Privacy Handles It
Temporary Destination DowntimeRetries the request until the destination becomes available.
Rate-Limiting by DestinationAdapts retry intervals to avoid hitting rate limits.
Invalid ConfigurationLogs the error and provides debugging details for quick resolution.
Network ErrorsRetries with exponential backoff to handle transient issues.

Monitoring Retry Status:

  • Use the Recent Events Dashboard to:
    • Identify failed dispatches to destinations.
    • View detailed error messages and retry status.
    • Confirm successful retries after issues are resolved.
The Recent Events dashboard showing a fictional appointment request with a temporary destination delivery failure, scheduled retry, and successful comparison dispatch

Best Practices for Error Handling

  1. Configure Destinations Correctly:
    • Ensure API keys, credentials, and mappings are set up correctly for each destination.
  2. Validate Events Before Sending:
    • Use the allowlist and data mapping tools to ensure events are properly formatted and configured.

Debugging Errors

When errors occur, follow these steps to troubleshoot:

  1. Check the Recent Events Dashboard:
    • Identify the affected events and view error details.
  2. Inspect Configuration:
    • Verify destination settings and ensure required fields are included in the event.
  3. Reach Out for Support:

Next Steps

How is this guide?

Test Mode

Previous Page

Event Replay

Next Page

On this page

Multi-Region Redundancy for IngestionRetry Mechanism for External Destination FailuresRetry Logic:Common Failure Scenarios and ResolutionsMonitoring Retry Status:Best Practices for Error HandlingDebugging ErrorsNext Steps