Signal routing and destinations

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

Routing checklist

• Canonical purchase event is mapped and tested
• Required order, customer, value, and currency 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
• Click IDs and identity fields are captured where available

Current destination focus

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

Signal quality layer

RocketCheckout should not only deliver events. It should evaluate whether each destination received a strong signal: email hash, phone hash, external ID, IP, user agent, fbc, fbp, gclid, ttclid, msclkid, event ID, value, and currency where supported.

Why delivery is not enough

An event can be delivered but still weak. If Meta, Google, or TikTok cannot match the event to a user or click, ad optimization suffers. Signal quality is the difference between sending data and sending useful data.