Inventory the baseline message
Extract every visible and hidden URL: branded links, click tracker, image/CDN, unsubscribe, preference center, survey, social link, and redirect hop. Record domain owner, TLS, redirect behavior, recipient identifiers, and purpose. Remove stale or unknown domains before using placement as the first diagnostic.
Check domain-specific reputation sources under their documented licensing and meaning. “Not listed” is not a provider trust guarantee. Verify registrar, DNS, and provider accounts are secured.
Define one change
Examples include tracking on versus off, branded tracking domain versus provider default, one redirect removed, or a rewritten unsubscribe implementation. Keep From/return-path/DKIM, provider account/pool, audience, timing, MIME, subject, and content otherwise stable.
Ensure both variants remain compliant and functional. Turning off unsubscribe tracking must not remove unsubscribe. Do not send a broken/privacy-hostile variant merely to test whether filters prefer it.
Inspect received messages
Providers can rewrite links or route variants differently. Compare originals after receipt: headers, authentication, size, MIME, URL domains/hops, and provider outbound IP. Confirm only the intended link behavior changed.
Use a safe redirect inspector: HTTPS/HTTP allowlist as approved, no credentials, private/reserved address blocking, DNS revalidation, hop/time/byte caps, and no browser script execution. Do not fetch customer-specific links through public tools.
Compare observations
Record SMTP outcome, inbox/spam/other/missing/unknown, monitor health, and provider/account per variant. Repeat the paired test. Add provider complaints/delivery errors over an appropriate window if a bounded real-audience rollout follows.
If placement differs, the evidence supports a hypothesis about that tested configuration and sample—not a claim that “tracking links go to spam.” Investigate domain ownership, redirect failures, compromised destinations, and recipient expectation.
Deploy with rollback
Roll out the safer supported variant to a limited authorized cohort, monitor links and mail outcomes, and retain a rollback. The test is useful when it produces a reproducible, technically explainable change while preserving security, privacy, and recipient controls.