OneView automatically resolves Conversion API errors and configuration conflicts for each integration. No action required.
What is Contextual Error Handling?
Contextual Error Handling automatically classifies and resolves Conversion API errors based on each platform’s specific requirements and API behaviors. OneView intelligently recovers from platform errors and configuration conflicts so conversions always flow correctly—accurate, compliant, and attributed where they should be.Understanding the problem:Each advertising platform has unique:
- API error codes and meanings
- Configuration requirements
- Attribution model compatibility rules
- Consent handling specifications
How Error Handling works
OneView classifies errors and applies platform-specific resolution strategies:| Error Type | Classification | Action |
|---|---|---|
| Transient errors | Network issues, temporary outages | Automatic retries with backoff |
| Rate limit errors | API rate limits exceeded | Retries with exponential backoff |
| Fatal errors | Configuration issues, incompatible settings | Retries stopped, requires fix |
| Skipped events | Intentional skips (consent, lookback windows) | No retry, recorded for observability |
OneView automatically handles incompatible conversion models, misaligned consent configurations, attribution-breaking setup conflicts, and API-specific quirks without manual intervention.
Error classification
OneView classifies integration responses into normalized outcomes:Transient errors
Temporary failures that OneView automatically retries:| Cause | Example | Resolution |
|---|---|---|
| Network issues | Connection timeout | Automatic retry with backoff |
| API outages | Platform temporarily unavailable | Retries until service recovers |
| Rate limits | Too many requests | Retries with exponential backoff |
No action is typically required. If transient errors persist for prolonged periods, review rate limits and batch sizes for the specific integration.
Fatal errors
Non-retryable problems that require configuration changes:| Cause | Example | Resolution |
|---|---|---|
| Misconfiguration | Webhook misconfigured | Fix configuration, reprocess |
| Incompatible settings | Attribution model conflict | Align settings, reprocess |
| Validation errors | Invalid data format | Fix data format, reprocess |
Skipped events
Intentional skips to prevent errors or policy violations:| Reason | Example | Behavior |
|---|---|---|
| Consent not granted | ad_storage denied | Event skipped, no retry |
| Lookback window exceeded | Conversion outside click-through window | Event skipped, no retry |
Skipped events are acknowledged by the pipeline (no retry). They are recorded for observability and do not count as failures.
Platform-specific handling
Each Conversion API integration is context-aware and handles platform-specific requirements:| Platform | Automatic Handling |
|---|---|
| Google Ads | Attribution model compatibility, Enhanced Conversions requirements |
| Meta | Consent mode enforcement, event matching rules |
| Microsoft Ads | Conversion goal configuration, lookback window validation |
| TikTok | Event schema validation, attribution settings |
OneView automatically adapts error handling to each platform’s API specifications and requirements, ensuring conversions flow correctly regardless of platform-specific quirks.
Benefits
Automatic recovery OneView automatically retries transient errors and resolves configuration conflicts without manual intervention. Platform-specific intelligence Each integration understands its platform’s error codes, requirements, and behaviors, applying appropriate resolution strategies. Consistent delivery By handling errors contextually, OneView ensures conversions reach their destinations accurately and compliantly, even when platform requirements change.Common questions
What happens when OneView encounters a fatal error?
What happens when OneView encounters a fatal error?
OneView stops retrying and marks the event as a fatal error. The pipeline may pause the affected webhook to prevent repeated failures. Once you fix the configuration and resume the webhook, you can reprocess affected conversions.
How does OneView handle rate limit errors?
How does OneView handle rate limit errors?
OneView automatically retries rate limit errors with exponential backoff, respecting the platform’s rate limits while ensuring eventual delivery.
Can I see error details in logs?
Can I see error details in logs?
Yes. OneView logs show error classifications, reasons, and resolution actions for each integration, allowing you to monitor and troubleshoot issues.
What if an error persists after automatic retries?
What if an error persists after automatic retries?
If transient errors persist for prolonged periods, review:
- Rate limits and batch sizes for the integration
- Network connectivity and endpoint availability
- Platform-specific requirements and recent API changes