Tracking

Custom Tracking Domains for Cold Email: Why You Need One (and Setup)

By Toukir AhmedPublished June 18, 2026Read 3 min

Here's a risk most senders don't know they're carrying: every open pixel and rewritten link in your emails points at your tool's shared tracking domain — a domain simultaneously used by every spammer on that platform. When their reputation tanks, yours goes with it. You didn't do anything wrong; you were just standing next to them.

How shared tracking burns clean senders

Spam filters evaluate every domain that appears in a message — sender, reply-to, and every link in the body. With default settings, your beautifully authenticated email contains links to track.sendingtool.com, and that domain's reputation is a group project with thousands of strangers. Shared tracking domains regularly end up on URI blacklists like SURBL — at which point every email containing them takes a placement hit, regardless of the sender's own flawless authentication.

what filters see in your email body
Sharedhttps://track.sendingtool.com/c/xy12…FAIL
Customhttps://track.getacme.com/c/xy12…PASS
Fromalex@getacme.comPASS
Alignmentbody links match from-domain familyPASS
one CNAME record moves you from the top row to the second

Setup: five minutes per domain

01

Pick the subdomain

Convention: track.yourdomain.com (or link., go., t.) on each sending domain.

02

Add the CNAME

Point it at your tool's tracking target (each platform documents its hostname).

03

Verify in the tool

Add the custom domain in your sending platform and confirm SSL provisions.

04

Assign per inbox

Map each inbox to the tracking domain that matches its sending domain.

Fleet scale: 200 sending domains means 200 CNAMEs and 200 tool assignments. This is exactly the kind of work I automate through Cloudflare's API and the sending platform's API — the whole fleet configures identically in one pass.

The bigger principle: control every domain in the message

Tracking domains are one instance of a rule that governs all of cold email infrastructure: never let a domain you don't control appear in your messages. Your from-domain, your links, your tracking, your unsubscribe URL — all should live on infrastructure whose reputation you own and monitor. It's the same logic as using secondary sending domains: isolate what you can't afford to lose from what you're putting at risk.

1CNAME per sending domain
5 minsetup per domain
0third-party domains in body
SURBLthe list shared tracking hits

Frequently asked questions

What is a custom tracking domain?

When your sending tool tracks opens and clicks, it rewrites links through a tracking host. By default that host is shared by every customer of the tool; a custom tracking domain replaces it with a subdomain of your own sending domain, so your links carry your reputation instead of a stranger's.

Do tracking domains need to match the sending domain?

Best practice is one tracking subdomain per sending domain (track.getacme.com for getacme.com). Matching keeps the domains in your email body aligned with your from-domain, which reads as coherent to filters and avoids cross-domain reputation bleed.

Should I turn off open tracking entirely for cold email?

Many high-deliverability senders now disable open tracking — the pixel adds a filterable fingerprint and open data is unreliable anyway. If you keep any tracking (especially click tracking), a custom domain is non-negotiable; if you disable all tracking, you sidestep the issue.

Keep reading

Back to top