Custom Tracking Domain vs Shared: Which Should You Use?

Should you use a custom tracking domain instead of your provider's shared one? For most senders the answer is yes, and the reason is reputation. When you send through an email service provider (ESP), the links in your message and the open-tracking pixel are usually rewritten to pass through a tracking domain. On a shared tracking domain, that hostname is the same one hundreds or thousands of other customers use.

A custom tracking domain — sometimes called a branded link domain — moves that hostname onto a subdomain of your own domain. Its reputation, and the trust of the visible URL, then belongs to you. A shared domain is zero-setup and included; for a low-volume, well-behaved sender it is usually fine. A custom domain is one CNAME record and a TLS certificate, and it isolates you from strangers' behaviour while keeping the link people see aligned with your From address. Below: the verdict, a side-by-side table, where each option genuinely wins, the setup steps, and an honest third option most guides skip.

The verdict, up front#

Use a custom tracking domain if you send marketing or bulk mail, run campaigns whose click and open data you rely on, or care that the link a recipient hovers matches your brand. The upside is real and the cost is a few minutes of DNS work, most of which the ESP automates.

Stay on the shared tracking domain if you send low volume, send mostly plain one-to-one mail, or have not set up your sending domain's authentication yet. A shared domain removes a step, and the reputation risk is small until your volume — or your ESP's other customers — makes it matter.

The one thing a tracking domain does not do is fix deliverability on its own. It affects link reputation and how consistent your URLs look. It does not replace SPF, DKIM and DMARC, and it will not rescue a list with a high complaint rate. Treat it as one lever among several, not the lever.

Custom vs shared tracking domain at a glance#

The dimensions below are the ones that change the outcome. Setup effort and cost favour the shared domain; reputation control and brand consistency favour the custom one.

Where a custom tracking domain wins#

The reputation is yours. On a shared domain, your links resolve through a hostname you share with every other customer of the provider. If one of them sends spam and a URL blocklist flags that host, filters can treat your links with the same suspicion, even though your own sending is clean. A custom tracking domain removes that dependency: the only sender who can damage the hostname's reputation is you.

The visible URL stays on-brand. A shared domain shows recipients a link that has nothing to do with you — a string on the provider's domain. A custom tracking domain shows a subdomain of your own domain, so the URL a careful recipient hovers matches the From address they already trust. That consistency is a small trust signal to readers and to some filters, and it keeps your brand out of a third party's hands.

You control the name and the certificate. Because the subdomain is yours, you choose what it reads as — links.yourbrand.com, email.yourbrand.com — and the TLS certificate covers a name you own. If you switch ESP later, you repoint the CNAME rather than change the domain people see, so the visible link your recipients have clicked for years stays stable.

Where a shared tracking domain is the right call#

Zero setup. A shared domain works the moment you send. There is no DNS record to add, no certificate to provision, and nothing to break. For someone sending their first campaign, that is one fewer thing between them and a working send.

Low volume, low risk. The shared-reputation risk is a function of volume and of who else is on the host. A reputable ESP polices its shared domains and removes abusive senders. If you send a few hundred low-complaint messages a month, the odds that a shared host's reputation hurts you are small — small enough that the setup may not earn its keep yet.

Plain one-to-one mail barely needs it. If your mail is genuine person-to-person correspondence rather than campaigns, you may not need click and open tracking at all, which makes the whole tracking-domain question moot. More on that below.

How to set up a custom tracking domain#

The mechanics are the same across most providers, even though the labels differ. You create a subdomain, point it at your ESP with a CNAME, and let the ESP provision TLS. Keep your ESP's setup page open — it gives you the exact target host to point at.

1. 1

   Pick a subdomain

   Choose a subdomain that reads as a link host, such as links.yourdomain.com, email.yourdomain.com or e.yourdomain.com. Avoid your bare root domain and avoid the exact subdomain you send from; the tracking host is its own name.

2. 2

   Get the CNAME target from your ESP

   In your ESP's sending or branding settings, turn on the custom (branded) tracking domain option. It gives you a target hostname — something like tracking.your-esp.com — that your subdomain will point to. Copy it exactly.

3. 3

   Add the CNAME record

   In your DNS host, add a CNAME record: name is your chosen subdomain, target is the ESP's hostname. If your DNS is on Cloudflare, set the record to DNS only (grey cloud), not proxied — a proxied CNAME answers with Cloudflare's own addresses and breaks the tracking link.

4. 4

   Let TLS provision, then verify

   Most ESPs issue a TLS certificate for the subdomain automatically once the CNAME resolves, so links are served over HTTPS. Save the setting, wait for the ESP to confirm the domain is verified, and send yourself a test — the links should now show your subdomain and load with no certificate warning.

Pricing model, not prices#

No numbers here — this category reprices often and any figure a blog prints ages within weeks. What is durable is the packaging shape. A custom tracking domain is a feature of your ESP, not a product you buy separately. Most established ESPs and marketing platforms include it, some only on higher tiers, and a handful bundle it into a dedicated sending setup. Check your provider's own pricing and branding docs before you assume it is available on your plan; that page is the source of truth, not a third-party writeup.

A shared tracking domain is included by definition — it is the default, so it costs nothing extra. The real cost of the custom option is not money; it is the few minutes of DNS work and the discipline to verify it after setup.

Who each option is genuinely for#

Volume, mail type, and how much you rely on the numbers decide this more than any feature list.

A third option: send without tracking at all#

The debate assumes you need click and open tracking. Increasingly, you may not — and turning it off is a legitimate third choice most comparison pages skip.

Open tracking has quietly stopped meaning much. Since Apple's Mail Privacy Protection and similar features in other clients, the open-tracking pixel is often pre-loaded or blocked before a human ever sees the message. Open rates read high and mean little, and the pixel you are relying on is exactly the thing privacy-minded clients now neutralise.

Click tracking is more reliable, but the rewritten link is what triggers the reputation problem this whole post is about. For plain one-to-one mail, transactional receipts, or any message where you do not actually act on the numbers, sending clean links with no tracking domain sidesteps the reputation question entirely and is friendlier to recipients. If you do need the data — and for real campaigns you usually do — a custom tracking domain is the version that costs you the least reputation risk while you collect it.

Where AI Emaily fits — and where it doesn't#

A note on us, because this is our site and we would rather be straight about it. We build AI Emaily, and it is not a tool for this job. AI Emaily is an AI email client — it sits on the receiving side of the exchange this whole post describes. It does not send bulk mail, it does not set up tracking domains, and it will not measure your campaigns. If you are choosing between a shared and a custom tracking domain, that decision lives in your ESP; use your ESP's docs, not us.

Where AI Emaily is relevant is the mirror image of this topic. That open-tracking pixel a sender embeds on a shared or custom domain — by default, AI Emaily blocks remote tracking pixels on the mail you receive, so a sender cannot quietly log when and where you opened their message. It also reads the SPF, DKIM and DMARC results on inbound mail to flag spoofed and phishing senders. Put simply, this post is about a sender tracking people; AI Emaily is on the side that decides how much of that tracking reaches you.

So it is the wrong tool for setting up a branded link domain, and the right tool if what you actually want is a private, well-triaged inbox on the receiving end. You can see the product on the AI Emaily homepage, and the plans — a 7-day free trial on the Pro and Autopilot plans, card required and $0 if you cancel before day 7 — are at aiemaily.com/pricing. It is not a permanent free tier, and we are not going to call it one.