A custom tracking domain gives your cold email campaigns a branded tracking hostname instead of relying on the default shared tracking domain provided by your sending platform. If you use Instantly or Smartlead, you can configure one through a DNS CNAME record and verify it inside your account.
However, setting up a custom tracking domain is not simply about changing a URL. You also need to understand how click tracking and open tracking work, when tracking is worth enabling, how Cloudflare proxy settings affect verification, and why a custom tracking domain does not replace SPF, DKIM, or DMARC.
This guide explains how custom tracking domains work, walks through the setup process for Instantly and Smartlead, and shows you how to troubleshoot common DNS verification problems.
What Is a Custom Tracking Domain?
A custom tracking domain is a subdomain you control that your email outreach platform uses for tracking links, open-tracking pixels, and, depending on the platform, unsubscribe links.
For example:
Default tracking URL:
tracking.provider.comCustom tracking URL:
track.yourdomain.com
When click tracking is enabled, your sending platform replaces the original destination URL with a tracking URL. The recipient visits that URL first, and the platform records the click before redirecting them to the intended destination.
A custom tracking domain changes the hostname used for this tracking activity.
Instead of relying on a platform's default shared tracking hostname, your campaign uses a subdomain associated with your domain.
Important: A custom tracking domain does not mean you host the tracking service yourself. Your sending platform still processes tracking requests and records engagement events.
Why Use a Custom Tracking Domain for Cold Email?
There are several reasons cold email teams configure custom tracking domains.
1. Reduce Dependence on Shared Tracking Domains
Sending platforms may use shared tracking infrastructure for multiple customers. A custom tracking domain gives your campaigns a separate tracking hostname rather than relying on the platform's default shared hostname.
This gives you greater control over the tracking domain's configuration and reputation.
It does not guarantee inbox placement or eliminate every reputation risk.
2. Maintain Consistent Domain Branding
Consider this example:
Your sending address:
john@trycompany.com
Your tracking URL:
track.trycompany.com
The tracking hostname is associated with the same domain used for sending.
This can make tracked links more recognizable and consistent with your business identity.
3. Manage Tracking Infrastructure More Independently
A custom tracking domain gives you control over the DNS record connecting your subdomain to the tracking provider.
If you change email outreach platforms, you can review and update the tracking configuration without changing your mailbox address.
You should always check the new provider's requirements before replacing an existing CNAME record.
4. Support Agency-Level Domain Management
Agencies managing multiple clients may need separate tracking configurations.
For example:
Client | Sending domain | Tracking domain |
|---|---|---|
Client A | tryclienta.com | track.tryclienta.com |
Client B | getclientb.com | track.getclientb.com |
Client C | clientc-mail.com | track.clientc-mail.com |
This arrangement makes ownership and troubleshooting easier.
However, the ideal structure depends on the platform, account configuration, and reputation-isolation requirements. Some platforms also support one tracking domain across multiple mailboxes.
Custom Tracking Domain vs. Sending Domain
These two terms are often confused, but they serve different purposes.
Feature | Sending domain | Tracking domain |
|---|---|---|
Main purpose | Identifies the email sender | Processes tracking requests |
Example | trycompany.com | track.trycompany.com |
DNS configuration | SPF, DKIM, DMARC and other required records | Usually CNAME |
Used for | Sending and receiving email | Tracking clicks, opens and supported unsubscribe links |
Managed through | Email hosting and DNS provider | DNS provider and sending platform |
A custom tracking domain does not replace your email authentication records.
SPF, DKIM, and DMARC authenticate your sending identity. A tracking CNAME connects your tracking subdomain to your sending platform.
Both configurations serve different purposes.
How to Set Up a Custom Tracking Domain
The general process is similar across most cold email platforms:
Choose a tracking subdomain.
Open your domain's DNS manager.
Copy the CNAME information from your sending platform.
Add the CNAME record.
Enter your full tracking hostname in the platform.
Verify the configuration and test a message.
For this example, we will use:
track.yourdomain.com
Replace this example with your actual domain and the hostname required by your provider.
How to Set Up a Custom Tracking Domain in Instantly
Instantly provides a dedicated custom tracking domain configuration.
Follow these steps.
Step 1: Open Your DNS Manager
Log in to the DNS provider managing your sending domain.
This could be Cloudflare, Namecheap, GoDaddy, or another DNS hosting provider.
Select the domain you want to configure.
Step 2: Add the CNAME Record
According to Instantly's current help documentation, its standard custom tracking domain configuration uses:
DNS field | Value |
|---|---|
Type | CNAME |
Host / Name |
|
Target / Value |
|
TTL | Automatic or 3600 |
Your resulting hostname will look like:
inst.yourdomain.com
These values are specific to Instantly. Do not reuse them for Smartlead or another sending platform.
Step 3: Enable Custom Tracking Domain
After publishing the DNS record:
Open your Instantly account.
Navigate to Email Accounts.
Select the mailbox you want to configure.
Open its Settings.
Find Custom Tracking Domain.
Enable the setting.
Enter
inst.yourdomain.com.Save the configuration.
Step 4: Verify the CNAME
Click Check Status.
Instantly should display CNAME Verified when the record is accepted.
If you see Retrying, check the DNS record, hostname spelling, and propagation status.
Instantly also recommends using a CNAME lookup to confirm that your hostname resolves to prox.itrackly.com.
For the latest instructions, see the official Instantly Custom Tracking Domain Guide.
How to Set Up a Custom Tracking Domain in Smartlead
Smartlead also supports custom tracking domains through CNAME configuration.
Its current setup includes an important distinction: the CNAME target depends on whether you select HTTP or HTTPS tracking.
Step 1: Open Your Smartlead Mailbox Settings
Log in to Smartlead.
Open Sender Accounts.
Select the mailbox.
Navigate to the General tab.
Find Custom Tracking Domain.
Enable Use a Custom Tracking Domain.
Step 2: Choose HTTP or HTTPS
Smartlead provides two tracking configurations, depending on your account plan.
Option A: Without HTTPS
DNS field | Value |
|---|---|
Type | CNAME |
Host |
|
Target |
|
TTL | Automatic |
Option B: With HTTPS
DNS field | Value |
|---|---|
Type | CNAME |
Host |
|
Target |
|
TTL | Automatic |
The HTTPS option is only displayed when supported by your plan.
Always copy the values shown inside your own Smartlead account rather than relying on an old screenshot or another user's configuration.
Step 3: Publish the DNS Record
Open your DNS manager and create the CNAME record.
For example:
emailtracking.yourdomain.com
Make sure the hostname and target match the configuration displayed by Smartlead.
Step 4: Enter Your Tracking Domain
Return to Smartlead.
Enter your full tracking hostname in the Custom Tracking Domain field.
Smartlead automatically displays the HTTP or HTTPS prefix according to your selected option.
Click Check Status and then Save.
Step 5: Verify the Configuration
Smartlead displays the verification status for the CNAME and SSL configuration.
If verification fails, check the DNS target, hostname, SSL selection, and propagation status.
Important: Smartlead configures this setting at the mailbox level. You can reuse one tracking domain across multiple mailboxes, but all mailboxes using that tracking domain share its tracking-domain exposure. If it is blacklisted, all those mailboxes can be affected.
Read the official Smartlead Custom Tracking Domain Setup Guide.
How to Configure a Custom Tracking Domain in Cloudflare
Cloudflare users need to pay attention to the proxy setting.
For Instantly's documented Cloudflare configuration, the CNAME record should use DNS-only mode.
Follow these steps:
Log in to Cloudflare.
Select your domain.
Open DNS.
Click Add Record.
Select CNAME.
Enter the host and target supplied by your sending platform.
Set the proxy status to DNS Only when required by the provider.
Save the record.
Return to your sending platform and verify it.
For Instantly, the documented configuration is:
Type: CNAME
Name:
instTarget:
prox.itrackly.comProxy status: DNS Only
TTL: Auto
Do not assume that every tracking provider uses identical Cloudflare settings. Follow the specific instructions from your sending platform.
You can also consult Cloudflare's official proxy status documentation.
How to Check Whether Your Custom Tracking Domain Is Working
Publishing a CNAME record does not automatically mean your tracking configuration is working correctly.
Complete these checks before launching your campaign.
1. Check the CNAME Record
Use a DNS lookup tool to check your tracking hostname.
For example:
track.yourdomain.com
The returned canonical name should match the target supplied by your sending platform.
You can also run:
Or:
Replace the example hostname with your actual tracking domain.
2. Check Platform Verification
Open your Instantly or Smartlead account.
Confirm that the platform reports the tracking domain as verified.
3. Send a Test Email
Send a test email to an inbox you control.
Inspect the message source or hover over a tracked link without opening an unknown destination.
Check:
Does the tracking URL use your custom hostname?
Does the link redirect to the correct destination?
Does HTTPS work if enabled?
Does the platform report successful verification?
4. Check Again After DNS Changes
If you migrate DNS providers, change tracking platforms, or modify the CNAME target, repeat the verification process.
Keep a record of the hostname, provider, CNAME target, proxy mode, and verification date.
Common Custom Tracking Domain Problems and Fixes
Problem | Possible reason | Recommended fix |
|---|---|---|
CNAME not found | Record missing or incorrect | Check the authoritative DNS zone |
Verification stuck on Retrying | DNS not propagated | Wait and check again |
Wrong canonical name | Incorrect CNAME target | Copy the provider's exact target |
Cloudflare verification failure | Unsupported proxy configuration | Follow provider-specific proxy instructions |
SSL not verified | HTTPS not configured or provisioned | Check plan eligibility and provider SSL status |
Tracking URL still uses platform domain | Custom tracking setting not enabled or saved | Review mailbox settings |
Tracking stopped after migration | Old DNS record removed | Publish the new provider's required CNAME |
Avoid deleting and recreating records repeatedly when the configuration is already correct. First identify whether the issue is a DNS error, propagation delay, account setting, or SSL problem.
Should You Enable Open Tracking in Cold Email?
Open tracking and click tracking are different.
Open tracking uses a tracking pixel, usually a tiny invisible image embedded in an email. When the image loads, the tracking system records an open event.
Click tracking rewrites a link so that the recipient visits a tracking URL before reaching the intended destination.
Both can use a custom tracking domain, but their usefulness differs.
Open tracking is increasingly unreliable because privacy features and automated image loading can generate open events without a person reading the email.
For this reason, many cold email teams disable open tracking on initial outreach and focus on more meaningful indicators.
Recommended metrics include:
Positive reply rate
Total reply rate
Bounce rate
Meetings booked
Qualified opportunities
Click-through rate when links are genuinely needed
A custom tracking domain does not make tracking pixels invisible to filters or guarantee that tracked emails reach the inbox.
For sensitive campaigns, consider disabling unnecessary tracking altogether.
Custom Tracking Domain Checklist Before Launch
Use this checklist before activating a new campaign.
A dedicated tracking subdomain has been selected.
The correct CNAME target has been copied from the provider.
The CNAME record has been published in the authoritative DNS zone.
Cloudflare proxy settings follow the provider's requirements.
The tracking domain is verified inside Instantly or Smartlead.
HTTPS has been verified when enabled.
A test email has been sent successfully.
The tracking URL uses the expected hostname.
The final destination redirects correctly.
Unnecessary open tracking has been disabled.
SPF, DKIM, and DMARC have been checked separately.
for properly authenticated inboxes, clean prospect data, and responsible sending practices.
How LiteMail Fits Into Your Cold Email Infrastructure
A custom tracking domain is one part of a larger cold email setup.
You also need properly configured mailboxes, domain authentication, appropriate sending practices, and a reliable outreach platform.
LiteMail supports Google Workspace and Microsoft 365 mailbox provisioning, domain management, automated DNS configuration, and custom tracking domain setup. It also supports connecting mailboxes with cold email outreach tools.
If you are building an outbound infrastructure with Instantly or Smartlead, make sure your mailbox and tracking configurations are documented and verified separately.
Explore LiteMail's cold email infrastructure to learn how mailbox provisioning and domain management fit into your outreach setup.
Frequently Asked Questions
1. What is a custom tracking domain in cold email?
A custom tracking domain is a subdomain you own that your sending platform uses for tracking links, open pixels, and supported unsubscribe URLs. For example, track.yourdomain.com can replace a platform's default tracking hostname.
2. Does a custom tracking domain improve email deliverability?
It can reduce dependence on a shared tracking hostname and give you more control over your tracking-domain configuration. However, it does not guarantee better inbox placement or solve problems involving poor lists, authentication failures, sending practices, or domain reputation.
3. Does Instantly support custom tracking domains?
Yes. Instantly supports custom tracking domains through CNAME configuration. Its current documented setup uses the hostname inst and target prox.itrackly.com. Always check the latest instructions inside your account.
4. Does Smartlead support custom tracking domains?
Yes. Smartlead supports custom tracking domains through mailbox settings and CNAME records. Its documented target differs depending on whether you select HTTP or HTTPS tracking.
5. What DNS record is required for a custom tracking domain?
Most setups use a CNAME record that connects your tracking subdomain to the tracking service operated by your email platform. The exact hostname and target depend on the provider.
6. Should I use Cloudflare proxy for my tracking domain?
Follow your sending platform's instructions. For Instantly's documented Cloudflare setup, the CNAME should be set to DNS Only rather than Proxied. Other providers may have different requirements.
7. Does a custom tracking domain replace SPF, DKIM, or DMARC?
No. A tracking CNAME connects your tracking hostname to a tracking service. SPF, DKIM, and DMARC are separate email authentication mechanisms. You need to configure and verify them independently.
8. Should I disable open tracking for cold emails?
Consider disabling it on initial outreach if open data does not support a meaningful decision. Open tracking is affected by privacy features and automated image loading. Replies and qualified conversions are generally more useful campaign indicators.
9. Can I use one custom tracking domain for multiple inboxes?
Yes, depending on your sending platform. Smartlead explicitly supports using one tracking domain across multiple mailboxes. However, all mailboxes using that hostname share its tracking-domain exposure.
10. How long does custom tracking domain setup take?
The DNS configuration itself can take only a few minutes. Verification depends on DNS propagation, provider processing, and SSL configuration. Smartlead documents propagation of up to 48 hours, while Instantly documents a window of 24–72 hours.
Final Thoughts
Custom tracking domains are a useful part of cold email infrastructure, particularly for teams using tracking links across multiple inboxes and campaigns.
The key is to configure the correct CNAME record, follow your platform's DNS and SSL requirements, verify the hostname, and avoid collecting engagement data that does not help your campaign decisions.
Whether you use Instantly or Smartlead, a verified custom tracking domain gives you more control over your tracking configuration. Just remember that it is one part of deliverability, not a substitute
