Documentation
Event Delivery
Monitor and troubleshoot your conversion event delivery across all connected ad networks in real-time.
What is Event Delivery?
Event Delivery shows you the real-time status of every conversion event sent through ChannelStack. You can see which events were successfully delivered to each ad network, identify any failures, and troubleshoot issues quickly.
Delivery Status Types
Successfully Delivered
Event was accepted by all connected ad networks. Your conversion data is being tracked properly.
Partial Delivery
Event delivered to some networks but failed on others. Check individual network statuses for details.
Delivery Failed
Event could not be delivered to any network. This might be due to network errors or configuration issues.
Validation Failed
Event was rejected due to invalid data format or missing required fields. Review your event payload.
Unmapped Event
Event type is not mapped to any conversion action in the ad networks. Configure event mappings in Campaigns.
Consent Blocked
Event was not sent due to consent=false flag. This respects user privacy preferences (GDPR/CCPA compliance).
Pending
Event is queued for processing. Delivery status will update once processing is complete.
Event Flow
Each event goes through multiple stages before reaching the ad networks:
- Event Received - Your server sends an event to ChannelStack's API
- Validation - Event is validated for required fields and proper format
- PII Hashing - Personal data (email, phone, name) is hashed with SHA-256
- Network Routing - Event is routed to each connected ad network
- Delivery - Event is sent to each network's conversion API
Network-Specific Delivery
Meta (Facebook & Instagram)
Events are sent to Meta's Conversions API using your selected pixel. Each event includes hashed user data, event parameters, and attribution information.
Google Ads
Events are sent directly to Google's Enhanced Conversions API. Events are mapped to conversion actions in your Google Ads account automatically.
TikTok
Events are sent to TikTok's Events API using your selected pixel. Includes support for web events and custom parameters.
Troubleshooting
Events not appearing?
- Verify your API key is correct and active
- Check that events include required fields (api_key, event)
- Ensure your server can reach our API endpoint
- Events may take up to 30 seconds to appear
Validation failures?
- Review the event payload for missing required fields
- Ensure email addresses are valid format
- Phone numbers should include country code
- Currency codes must be 3-letter ISO format (USD, EUR)
Delivery failures?
- Check that your ad accounts are still connected
- Verify pixels/conversion actions are properly configured
- Ensure ad account permissions haven't changed
- Some networks may temporarily reject events during outages
Unmapped events?
- Configure event mappings in your campaign settings
- Each event type needs to be mapped to network conversion actions
- Standard events (purchase, add_to_cart) are usually pre-mapped
- Custom events require manual mapping configuration
Best Practices
- Monitor delivery status regularly, especially after launching new campaigns
- Include as much user data as possible (email, phone) to improve match rates
- Use consistent event names across your application for easier tracking
- Test event delivery with sample data before going live
- Set up alerts for delivery failures if running critical campaigns
- Review unmapped events weekly to ensure all conversions are tracked