Signal routing and destinations

Signal routing is only reliable when the event contract is clean. RocketCheckout expects canonical purchase events, consent-aware routing rules, and destination credentials to be validated before routing is expanded.

Routing checklist

• Canonical purchase event is mapped and tested
• Required order, customer, and value fields are present
• Consent handling is confirmed for each destination
• Deduplication strategy is defined when browser and server events coexist
• Destination credentials are current and verified

Current destination focus

• Meta Conversions API
• Google Enhanced Conversions
• TikTok Events API on supported plans
• Internal delivery reporting and signal quality monitoring