Tracking domain rotation — the pre-burn playbook

Tracking domain rotation — the pre-burn playbook

Tracking domains get flagged. Rotate on a schedule, not in a panic. Build the rotation as a repeatable procedure.

— Maintain a warm pool. Keep at least three tracking domains registered, with DNS pointed at your tracker and SSL valid. A domain you register the day you need it is already too late.
— Stagger registrars and registration dates. Domains bought the same day from the same registrar get flagged as a cluster.
— Pre-validate each pool domain: SSL valid, not on a public blocklist, redirect resolving. Re-check monthly so a swap is instant.
— Define the swap trigger: a measurable drop in delivery or a confirmed flag, not a hunch. Document the metric.
— Execute the swap: update the tracking domain at the campaign level, confirm the new domain carries click-ids through, send a test conversion before resuming spend.
— Quarantine the burned domain. Do not reuse it for 90 days, and never on the same vertical.

Validation after swap:
— One test click and one test postback through the new domain before full traffic resumes.

Rotation as a scheduled asset means a flag costs you minutes. Rotation improvised under pressure costs you a day of spend.

Save this SOP. Keep your warm pool stocked before every launch.