Quick Summary
A custom tracking domain is a subdomain you own, such as track.yourdomain.com, that replaces the generic tracking domain your email platform uses by default. You set it up by adding a CNAME record at your DNS host that points your chosen subdomain at the target value your platform gives you, then verifying it once DNS propagates.
- Choose a short hostname such as track, links, or click, and avoid the bare root domain.
- Enter the platform's target value as the CNAME target, and check that your DNS host did not add your root domain to the name twice.
- DNS propagation takes minutes to an hour or two and occasionally up to 24 hours, so a failed check early on does not mean the record is wrong.
- A certificate warning usually means HTTPS is not yet issued for the subdomain, not that the CNAME is broken.
- Keep the tracking record in place permanently, because removing it breaks every link you already sent.
What a Custom Tracking Domain Does and Why It Matters
A custom tracking domain is a subdomain you own, such as track.yourdomain.com, that replaces the generic tracking domain your email platform uses by default. When a recipient clicks a link, the click passes through this subdomain before it reaches the final page. Setting one up takes about 15 minutes of DNS work plus propagation time.
Why bother? Links that point to your own domain show recipients your brand in the link rather than a shared third-party domain.
A tracking domain does not guarantee inbox placement. It is one part of your sending setup, and it works best when the rest of that setup is sound.
Before You Start: What You Need and Choosing a Tracking Subdomain
You need three things: access to your DNS manager (at your domain registrar or DNS host), admin access to your sending platform, and a subdomain name.
Choose a short, descriptive hostname. Common choices include track, links, or click. Avoid names that imply a different company or product. Do not use the bare root domain: a name that holds a CNAME can hold no other record, and the root must keep its SOA and NS records (and usually your website).
Keep a note of the exact hostname you choose. You will type it into the DNS record and the platform, and a single typo will stop verification. For the other records a sending domain needs, read email deliverability: the four DNS records every sender needs.
Adding the CNAME Record at Your DNS Host
Your sending platform will show you a target value. Your job is to point your chosen subdomain at that target.
- Log in to your DNS host and open the DNS management page for your domain.
- Create a new record with type CNAME.
- In the name or host field, enter your subdomain (for example,
track). - In the value or target field, paste the target value from your platform.
- Save the record.
A CNAME record maps one name to another name. It does not hold an IP address, which is why the target must be a hostname.
Provider-Specific Notes for Common DNS Hosts
Some DNS hosts append your root domain automatically, so entering track may create track.yourdomain.com correctly. Others require the full name. If your record shows track.yourdomain.com.yourdomain.com, remove the duplicate suffix. Check your host's help pages for the exact field format.
On Cloudflare, set the record to DNS only (the grey cloud). A proxied record answers with Cloudflare's own addresses instead of your CNAME, so both the platform's verification and its certificate fail.
The tracking record sits beside your authentication records, not in place of them. For DKIM, see how to configure DKIM for custom domains.
Custom Tracking Domain Examples for Common Setups
Here are three typical setups:
| Setup | Hostname | Target type | Notes |
|---|---|---|---|
| Single sending brand | track.company.com | Provider CNAME | Simplest case |
| Multiple brands, one domain each | track.brandone.com, track.brandtwo.com | Provider CNAME per domain | Only where your platform allows one tracking domain per sending domain |
| Subdomain for marketing only | links.marketing.company.com | Provider CNAME | Keeps tracking away from the main site |
How Long Propagation Takes and How to Verify the Domain
A brand-new hostname has no old answer for resolvers to hold, so most see it within minutes of saving. The exception is a resolver that looked the name up before it existed, such as your platform's verify check or your own dig: it remembers that the name does not exist for the negative-cache time set in your zone's SOA record. So save the record before you click verify. If you are replacing an older record on the same name, that old record's TTL sets the wait instead. Allow up to 24 hours before treating a failure as a wrong record.
To verify, return to your platform and click the verify or check button. If it fails, wait and try again. You can also query the record yourself with a command-line tool such as dig or nslookup. Querying the authoritative nameserver directly shows whether your record is live at the source.
Watch out: do not assume a failed check means the record is wrong. Often it is just not propagated yet.
Troubleshooting Common Symptoms and HTTPS Behavior
Most failed custom tracking domain setups fall into a small number of patterns. Work through the checks below in order, because each one rules out a cause before you move to the next.
Verification fails immediately after saving
- Likely cause: Record not yet published, or hostname mistyped.
- Check first: Query the record with
dig CNAME track.yourdomain.com +short, using your own hostname. - Fix: Correct the hostname, or wait for the record to appear.
Verification fails after several hours
- Likely cause: Your DNS host appended the root domain twice.
- Check first: Run
dig CNAME track.yourdomain.com.yourdomain.com +shortwith your tracking hostname followed by your root domain again. Any answer means the suffix was doubled. - Fix: Remove the duplicate suffix and re-save.
The CNAME query returns nothing, but a plain query returns only IP addresses
The plain query is dig track.yourdomain.com +short, using your own hostname. An unproxied CNAME prints the target first, then the addresses.
- Likely cause: The record is proxied (Cloudflare orange cloud).
- Check first: Look at the proxy status on the record in your DNS panel.
- Fix: Switch the record to DNS only.
Verification passes but links open a certificate warning
- Likely cause: The HTTPS certificate is not yet issued for the subdomain.
- Check first: Open the link in a private window and inspect the certificate issuer.
- Fix: Wait for the provider to issue the certificate, then retest. If it never issues, check for a CAA record on your root domain that leaves out your platform's certificate authority.
Links resolve to the old tracking domain
- Likely cause: Old messages still carry old links, or the platform setting was not switched.
- Check first: Send a fresh test message to yourself and read the link in the source.
- Fix: Confirm the custom domain is selected in the platform, then resend.
The DNS host will not save the CNAME, or verification is blocked
- Likely cause: Another record (CNAME, TXT or anything else) already exists on that hostname.
- Check first: List all records for that name in your DNS panel.
- Fix: A name with a CNAME can hold no other record. Delete the other record if nothing uses it, or pick a different hostname.
How HTTPS fits in
HTTPS behaves differently from the DNS record itself. The CNAME only tells resolvers where the subdomain points. The certificate must then be issued for that exact hostname before a browser will accept a link without warning. Certificate issuance timing depends on the platform. A redirect chain adds another failure point: if the tracking host redirects to a different domain that has no valid certificate, the browser shows an error even though your CNAME is correct.
To separate a DNS problem from a certificate problem, check the record from several resolvers. If dig returns the provider target but the browser still fails, the issue is on the certificate or redirect side, not in your DNS records. If dig returns nothing, return to the DNS panel and check the record, and whether it is proxied, before touching anything else.
Watch out: do not disable HTTPS on the tracking domain to make a link work. Recipients may see an insecure link warning.
Custom Tracking Domain Best Practices and Your Next Step
Put the tracking subdomain under the same root domain you send from. Keep the record in place permanently, because removing it breaks every link you already sent, unsubscribe links included. Send a test campaign and click each link type before you start a real send. Review your DMARC and DKIM setup at the same time as your tracking domain.
Once the record verifies and your test links resolve through your own domain, the tracking setup is complete. Recheck the record after any DNS host migration, and keep your target value on file so a future change does not break tracking.
FAQ
What is a custom tracking domain?
It is a subdomain you own, such as track.yourdomain.com, that replaces the generic tracking domain your email platform uses by default. Clicks pass through this subdomain before reaching the final page, so recipients see your brand in the link rather than a shared third-party domain.
How long does a custom tracking domain take to verify?
The DNS work takes about 15 minutes. A brand-new hostname usually shows up within minutes to an hour or two, occasionally up to 24 hours. Save the record before you click verify: a resolver that asked for the name before it existed remembers that it does not exist for a while. If verification fails early, wait and try again before changing the record.
Why do my tracking links show a certificate warning?
The CNAME only tells resolvers where the subdomain points; an HTTPS certificate still has to be issued for that exact hostname before a browser accepts the link without warning. Wait for the provider to issue it, then retest. Do not disable HTTPS to make a link work, because recipients may see an insecure link warning.
Can I delete the tracking CNAME later?
No. Keep the record in place permanently, because removing it breaks every link in the messages you already sent, unsubscribe links included. Recheck the record after any DNS host migration and keep the target value on file.