SOP: Tracking domain — shared tracker domain vs custom first-party

SOP: Tracking domain — shared tracker domain vs custom first-party

Step 1 — Check blocklist exposure. A shared SaaS tracker domain gets burned by other users' bad traffic; your clean campaign inherits the block.
Step 2 — Move money campaigns to custom domains. One domain per traffic source minimum, so a block on Facebook traffic doesn't kill native.
Step 3 — Warm new domains. Don't launch peak volume on a day-old domain; ramp over 3-5 days or filters flag the spike.
Step 4 — Match the redirect domain to the lander domain (same root) where the source rewards first-party — cuts ITP cookie loss.
Step 5 — Keep 2-3 spare warmed domains parked. When one burns, swap config, not campaigns.

Tradeoff: shared domains are zero-setup but fragile; custom domains cost upkeep but isolate risk.

Check domain reputation weekly; rotate burned domains immediately.