Setup and operations
Campaign Routing Testing Checklist
A launch checklist is strongest when every case declares its expected destination and evidence before the request is sent.
Prepare deterministic fixtures
Create intended, conservative, allowlisted, unknown-source, excluded-market, unusual-network, repeated-click, and incomplete-context cases relevant to the campaign. Record which fields each fixture can reliably control.
Check one routing layer at a time
Verify DNS and TLS, host or path match, captured request context, rule precedence, risk result, selected destination, and delivery response. This sequence makes the first failure visible before later behavior adds noise.
Exercise both destination experiences
Load assets, navigation, forms, mobile layouts, and parameter handling on White and Target pages. Include the chosen redirect, proxy, or iframe behavior rather than checking only the upstream URLs.
Test failure and recovery
Use a bad path, unavailable test upstream, malformed parameter, and reversible rule mistake. Confirm the visitor receives the intended safe behavior and an operator can locate the error without exposing secrets.
Capture launch signoff
Store URL versions, observed events, unresolved deviations, approver, rollback action, and test time. Re-run affected cases after any domain, tracker, destination, filter, or delivery-mode change.