Custom Tracking Domain: How to Set One Up for Cold Email
Summarize with AI
A custom tracking domain gives retained open or click tracking a hostname you control instead of your sending tool's shared tracking URL. Set one up only if your team has decided the tracking data is worth collecting. LeadHaste does not recommend open tracking, so the cleanest configuration is often to turn it off. If you intentionally keep click tracking or another supported tracking feature, create the DNS record with values copied from your own provider, verify it, and test it before a campaign starts.
What a Custom Tracking Domain Does
When a sending tool tracks an open or click, it adds tracking code to the message. Open tracking usually loads a tiny remote image. Click tracking commonly rewrites a link so the recipient first visits a tracking URL and is then redirected to the destination.
Instantly defines a custom tracking domain as a dedicated domain used to track email opens and link clicks. Its guide says customers otherwise share an Instantly tracking URL. With a CTD, the tracking code uses a hostname under the customer's domain instead.
In practice, this is usually a subdomain such as track.example.com, not a new website and not a second inbox. The subdomain points to the sending provider's tracking service. The provider still records the event and handles the redirect or image request.
The change gives you control over the visible tracking hostname and removes reliance on the provider's shared hostname. It does not transfer the tracking service to your server, authenticate your email, repair a weak list, or guarantee inbox placement. A recipient filter can still inspect a tracked link or image.
Decide Whether You Need Tracking First
A DNS record should follow a measurement decision, not substitute for one. Start by listing the decisions the event will support. If nobody changes a campaign based on an open event, collecting that event adds code and reporting noise without helping the team act.
We turn open tracking off in LeadHaste programs. Opens depend on a tracking pixel, and privacy tools, image proxies, and automated scanners can load it without a person reading the message. We use replies, positive replies, bounce rate, pipeline generated, and cost per lead instead. Our guide to email open tracking explains the measurement trade-off in more detail.
Click tracking needs a separate decision. If links are rare and replies are the desired action, you may not need it either. If a campaign intentionally uses a resource link and the click event changes follow-up or reporting, a custom tracking domain is the better configuration than leaving the provider's shared tracking hostname in place.
How the CNAME Record Works
Most sending platforms connect a tracking subdomain with a CNAME record. Cloudflare's DNS documentation explains that a CNAME maps one domain name to another canonical domain name. Its documented fields include the name, the target hostname, and the TTL, which controls how long DNS resolvers cache a response before checking again.
For a CTD, those fields have distinct jobs:
| DNS field | What it means | Where to get the value |
|---|---|---|
| Type | The record type, normally CNAME | Your sending provider's CTD guide |
| Name or host | The subdomain label, such as `track` | Your sending provider |
| Target or value | The provider hostname that receives tracking requests | Your sending provider |
| TTL | How long resolvers cache the answer | Provider guidance or your DNS host's supported default |
| Proxy status | Whether a DNS host proxies the request | Follow the sending provider's instructions |
The name and target are not interchangeable. If the host is track on example.com, the resulting hostname is normally track.example.com. The target is the different hostname supplied by the sending tool.
Provider settings vary by tool and account. Instantly currently documents inst as its host, prox.itrackly.com as its target, and automatic or 3600 as the TTL. Those are Instantly-specific values. Do not paste them into Smartlead, Apollo, another sending platform, or even a different Instantly workflow without checking the current instructions shown in your account.
How to Set Up a Custom Tracking Domain
The setup has five parts: choose the hostname, copy the provider's values, publish the CNAME, connect it in the sending tool, and verify the result. Keep the provider guide open while you work.
1. Choose the Tracking Hostname
Pick a short subdomain that is not already used by a website, mail service, or another vendor. Names such as track, click, or a provider-specified label are easy to recognize. Check your DNS zone before choosing it because a CNAME generally cannot share the same name with unrelated records.
Write down the complete hostname you expect, such as track.example.com. Confirm that you are editing the correct domain, especially when several sending domains have similar names.
2. Copy the Values From Your Sending Provider
Open the custom tracking domain screen or current help guide for the sending tool connected to that domain. Copy the record type, host, target, TTL, and proxy instruction exactly. If the provider asks for an additional TXT record, copy that value too.
Do not infer a target from a screenshot or another account. Vendors can use different regions, tracking services, or account-specific verification values.
3. Add the CNAME in DNS
Open the authoritative DNS manager for the domain. Add a CNAME and enter the supplied host and target. Some DNS interfaces want only the host label, such as track; others accept the full hostname. Review the preview before saving so you do not accidentally create track.example.com.example.com.
If your DNS host has a proxy toggle, use the mode required by the sending provider. A CNAME can resolve correctly while an unsupported proxy setting still prevents the sending tool from verifying or serving the request as expected.
4. Enter the Full Hostname in the Sending Tool
Return to the sending platform and enable its custom tracking domain setting. Enter the full hostname, not only the host label, unless its interface explicitly requests otherwise. Save the setting for the correct workspace, domain, or mailbox scope.
Instantly's current process, for example, asks the user to add the CNAME, enter the full custom hostname in account settings, save it, and click Check Status. Its guide shows CNAME Verified when the record is accepted and Retrying when the record has not propagated or was entered incorrectly.
5. Verify DNS and Send a Test
Use the provider's verification button first. If verification fails, inspect the public CNAME answer and compare it character by character with the required target. Check for an extra domain suffix, a misspelled host, the wrong DNS zone, an unsupported proxy mode, or a conflicting record.
DNS changes may not appear everywhere at once because resolvers cache prior answers according to TTL. Do not repeatedly delete and recreate a correct record while caches are updating. Confirm the saved values, wait for the provider's stated window, and check again.
Once the platform verifies the hostname, send a test to an inbox you control. Inspect the message source or copy the rewritten URL without visiting it. Confirm that the tracking hostname is yours, the destination is correct, HTTPS works, and no certificate warning appears. Keep the test separate from a live prospect campaign.
How to Troubleshoot CTD Verification
A failed verification usually comes down to scope, spelling, or DNS behavior. Work through the evidence in this order:
- Confirm the zone. Make sure the record was added where the domain's authoritative nameservers are managed.
- Check the full name. Verify that the DNS host produced the intended subdomain exactly once.
- Compare the target. Remove accidental spaces and confirm every label against the provider's current value.
- Review proxy mode. Follow the sending tool's requirement rather than assuming proxied or DNS-only is always correct.
- Look for conflicts. Remove or rename another record only after confirming it occupies the same hostname and is safe to change.
- Complete extra verification. Add a provider-requested TXT record when the account screen requires it.
Instantly also recommends checking the public CNAME result and confirming that the canonical name matches its target. That check proves what DNS currently publishes. The sending tool's status remains the final test of whether that provider accepts the setup.
For a broader review of sending domains, authentication, and mailbox controls, use our cold email inbox placement guide.
Maintain the Domain After Setup
Keep the tracking hostname, provider target, proxy mode, and verification date in the domain record. Limit DNS access and review the CNAME with the rest of that sending domain. If you change sending tools, disable the old tracking feature, test the new provider's hostname, and remove the old CNAME only after no active campaign depends on it.
Revisit the original measurement decision too. If the team stops using click data, turn click tracking off rather than preserving it because the DNS record already exists. If open tracking was enabled during a test, disable it when the test ends. The leanest message is usually the one with no unnecessary tracking code.
Ready to Build Cleaner Cold Email Infrastructure?
We build client-owned outbound systems with documented DNS, provider settings, suppression, and reporting tied to decisions your team can act on. See how our outbound services fit together, then book your free discovery call →.
Frequently Asked Questions
A strong positive reply rate for B2B cold email is 1.5–3%. Top-performing campaigns with tight targeting and personalized copy can hit 4–5%. If you're below 1%, it usually signals a deliverability or messaging problem, not a volume problem.
The safe range is 30–50 emails per inbox per day for warmed inboxes. That's why outbound systems use multiple inboxes (we use 80) to reach 40,000+ monthly sends while keeping each inbox well within safe limits. Sending more than 50/day from a single inbox risks spam folder placement.
Yes. The CAN-SPAM Act permits unsolicited commercial email as long as you include a physical address, an unsubscribe mechanism, accurate headers, and non-deceptive subject lines. Unlike GDPR in Europe, the US does not require prior opt-in consent for B2B cold outreach.
Domain warm-up typically takes 2–3 weeks. During this period, sending volume gradually increases while the email warm-up tool generates positive engagement signals (opens, replies) to build sender reputation. Skipping or rushing warm-up is the most common cause of deliverability problems.
Cold email is targeted, relevant outreach to a specific person based on their role, industry, or company, with a clear business reason. Spam is untargeted mass messaging with no personalization or relevance. The distinction matters legally (CAN-SPAM compliance) and practically (deliverability depends on relevance signals).
Dimitar Petkov
Co-Founder of LeadHaste. Builds outbound systems that compound. 4x founder, Smartlead Certified Partner, Clay Solutions Partner.
