Custom Tracking Domain for Cold Email: Setup Guide 2026

TL;DR

• A custom tracking domain is a subdomain you own (like inst.yourdomain.com) that your cold email tool uses for open pixels and click redirects.
• Without one, your links point to a tracking host shared by every customer of the tool. If other senders get that host flagged, your emails take the hit.
• Setup is one CNAME record: Instantly inst → prox.itrackly.com, Smartlead emailtracking → open.sleadtrack.com. lemlist generates the CNAME values and also needs a TXT record.
• Use one tracking subdomain per sending domain. On Cloudflare, set the record to DNS only.
• For most cold email, turn open tracking off. Apple Mail Privacy Protection inflates opens, and the pixel makes a plain email look like marketing. Measure replies instead.

What Is a Custom Tracking Domain?

A custom tracking domain is a subdomain on your own domain that your cold email tool uses to track opens and clicks. You point it at the tool's tracking servers with a single CNAME record.

Once it is live, every tracking pixel and rewritten link in your emails uses yoursubdomain.yourdomain.com. Without it, they use a hostname the vendor owns and shares with every other customer.

This guide is for SDRs, founders, and agencies running cold email on Instantly, Smartlead, or lemlist. It covers why shared tracking domains hurt deliverability, the exact DNS records each tool documents, how to verify them, and when the better answer is to switch tracking off.

Every DNS value below comes from each vendor's own help center, checked in October 2026. If your dashboard shows a different value, use the dashboard value.

How Open and Click Tracking Work

Email tracking works by routing small requests through the tool's server. The tracking domain is the hostname those requests go to.

Open tracking

The tool inserts a tiny invisible image, unique to each recipient, into the email. When the email client loads images, it requests that image from the tracking domain, and the tool logs an open.

That means open tracking only works in HTML email. A plain-text message cannot carry a pixel.

Click tracking

The tool rewrites every link in your email to a redirect URL on the tracking domain. When someone clicks, the request hits the tracking server first, gets logged, and then redirects to the real page.

Hover over a tracked link and you see the tracking domain, not your destination. That is the hostname spam filters and prospects judge.

Why Shared Tracking Domains Hurt Deliverability

Shared tracking domains hurt deliverability because spam filters score every domain inside your email, and you cannot control who else is sending through the same one.

Filters check the domains in your links

Domain blocklists look at links, not just the From address. The Spamhaus Domain Blocklist tells mail servers to check "domains appearing in the mail headers and body".

In SpamAssassin, one link on a DBL-listed domain adds 2.5 points by itself. Our SpamAssassin score guide breaks down that rule and the others that hit cold email.

You inherit your neighbors' reputation

A default tracking host carries traffic from every account on the platform. Smartlead's own docs warn that the same tracking domain used across thousands of campaigns from all users can cause deliverability drops.

If one heavy sender gets that host flagged, your perfectly authenticated email still carries a flagged link. A custom tracking domain cuts that tie.

Mismatched links look suspicious

An email from yourdomain.com whose links all redirect through an unrelated hostname is a pattern filters and humans both notice. Google's sender guidelines say links "should be visible and easy to understand."

A tracking subdomain on your own domain keeps the link consistent with the sender. It does not fix weak copy or a bad list, but it removes one avoidable red flag.

Before You Start

Check five things before touching DNS. Each one prevents a common failed verification.

1. DNS access for every sending domain. You need the panel that actually serves your DNS. If your nameservers point to Cloudflare, edits at the registrar do nothing. Our best domain registrar for cold email guide covers which panels make bulk DNS edits easy.
2. SPF, DKIM, and DMARC already passing. A tracking domain will not rescue broken authentication. See Gmail DKIM and how to avoid spam filters for the base setup.
3. One tracking subdomain per sending domain. Both Instantly and Smartlead let you reuse one tracking domain from an aged domain across all mailboxes. For cold email on secondary domains, isolate each one so a burned domain takes only its own tracking with it.
4. Cloudflare set to DNS only. A proxied (orange cloud) record makes lookups return Cloudflare anycast IPs instead of the vendor's hostname, so verification fails.
5. A different subdomain per tool. A hostname with a CNAME cannot hold any other record, so inst cannot point to two vendors at once.

Custom Tracking Domain CNAME Values by Tool

Here are the records each vendor documents. Replace yourdomain.com with your sending domain.

Set TTL to automatic or 3600 unless your provider forces another value. Comparing the platforms themselves? See Smartlead vs Instantly and lemlist vs Instantly.

Set Up a Custom Tracking Domain in Instantly

In Instantly, a custom tracking domain is a CNAME with host inst pointing to prox.itrackly.com, switched on per email account. These steps follow Instantly's help center.

1. Add the CNAME. In your DNS panel, create a CNAME record with Host inst and Value prox.itrackly.com. Use instexactly, since Instantly's guide warns that a different host breaks verification.
2. Open the account settings. In Instantly, go to Email Accounts, click the sending account, and open Settings.
3. Enable the setting. Scroll to Custom tracking domain, switch it on, and enter inst.yourdomain.com.
4. Check status.Click Check Status. "CNAME Verified" means you are done, while "Retrying" means the record has not propagated or has a typo.
5. Repeat per mailbox. Save, then repeat for every account on that domain.

Instantly's docs suggest one shared tracking domain only for older, warmed-up domains, and separate ones for new domains or risky campaigns. Done-For-You and pre-warmed accounts get the CNAME and tracking domain configured automatically.

More on the platform in our Instantly review.

Set Up a Custom Tracking Domain in Smartlead

In Smartlead, a custom tracking domain is a CNAME with host emailtracking pointing to open.sleadtrack.com, entered on each email account. These steps follow Smartlead's help center.

1. Add the CNAME. Create a CNAME record with Host emailtracking, Value open.sleadtrack.com, and TTL set to automatic.
2. Wait for propagation. Smartlead says 30 minutes to 24 hours.
3. Open the email account. In Smartlead, open the mailbox (or add a new one) and scroll to the Custom tracking domain field.
4. Enter the full URL. Smartlead's docs use the format http://emailtracking.yourdomain.com.
5. Verify. Click Verify CNAME, which opens an nslookup.io result. The Canonical name should read open.sleadtrack.com.

Smartlead also supports pointing all mailboxes at one tracking domain on an aged, well-reputed domain. That consolidates tracking, but per-domain records keep each sender isolated, which is the safer default for cold outreach.

See our Smartlead review for how the rest of the deliverability stack holds up.

Set Up a Custom Tracking Domain in lemlist

In lemlist, the custom tracking domain needs a CNAME plus a TXT record, and both values are generated for you. It is also mandatory: per lemlist's help center, sending is blocked when open or click tracking is on and no verified tracking domain exists.

1. Open the sending address settings. Go to Settings, then Sending settings, then Email, open the sending address, and find Custom tracking domain.
2. Copy the CNAME values. lemlist shows the host (examples in its docs include trail and route) and the target. Copy the value shown in your dashboard rather than typing it from memory.
3. Add the CNAME. Create it in your DNS panel. If your provider rejects a trailing dot on the target, remove it and retry.
4. Add the TXT record. Click Check setup. lemlist then shows a TXT value unique to your tracking domain, which goes on host @.
5. Check again and test. Click Check setup once more. Paste the tracking domain into a browser, and you should see a confirmation message.

A tracking domain set in team settings applies to all teammates, and a user-level one overrides it. Allow up to 72 hours for propagation.

Our lemlist review covers the rest of the product.

How to Verify and Troubleshoot

To verify a custom tracking domain, run a CNAME lookup on the full subdomain. The answer must be the vendor's target hostname.

dig +short CNAME inst.yourdomain.com
# expected: prox.itrackly.com.

nslookup -type=CNAME emailtracking.yourdomain.com
# expected canonical name: open.sleadtrack.com

If the lookup fails, it is almost always one of these five problems.

Record not found

Either the record has not propagated, it has a typo, or you edited the wrong DNS zone. Check which nameservers your domain uses before editing anything.

Doubled domain name

Many DNS panels append your domain to the host automatically. Typing inst.yourdomain.com as the host creates inst.yourdomain.com.yourdomain.com, so enter only inst.

Cloudflare proxy is on

A proxied record returns Cloudflare IPs instead of the vendor hostname. Switch the cloud icon to gray (DNS only) and recheck.

Conflicting record on the same host

A hostname with a CNAME cannot also hold an A, TXT, or second CNAME record under RFC 1034. Delete the old record on that host first.

Trailing dot rejected

Some providers want custom.lemlist.com. with a final dot, others reject it. If validation keeps failing, try the other form.

When to Turn Tracking Off Entirely

Turn open tracking off on most cold campaigns, and turn click tracking off whenever the goal is a reply. A custom tracking domain makes tracking safer, but no tracking removes the risk entirely.

Open rates no longer mean much

Apple's Mail Privacy Protection, launched in 2021, "stops senders from using invisible pixels to collect information about the user" and prevents senders "from knowing when they open an email." In practice, Apple Mail users can show as opens whether they read the email or not.

Corporate security scanners also fetch images and follow links before a human does. Open and click numbers from enterprise inboxes are inflated by bots.

The pixel changes how your email looks

A pixel turns a plain one-to-one note into an HTML email with a remote image. Rewritten links add a redirect hop through another hostname.

Both are traits of marketing mail, which is why tracking is on the list of fixes in our guide to avoiding the Gmail Promotions tab.

Tracking settings by scenario

Keep the CNAME in place even after switching tracking off. It costs nothing, and you are ready the day a campaign genuinely needs click data.

What to Measure Instead of Opens

With tracking off, judge campaigns on numbers no pixel can fake. These five tell you more than an open rate ever did.

• Reply rate and positive reply rate. Every sending tool records replies without a pixel.
• Bounce rate under 2%. Bounces hurt sender reputation faster than anything a tracking domain fixes. SyncGTM verifies each address through a multi-provider waterfall at 0.1 credits per email, and finding a work email costs 1 credit with misses not billed. See SyncGTM pricing.
• Spam complaint rate.Google's guidelines say to keep the spam rate in Postmaster Tools below 0.3%.
• Inbox placement. Seed tests show where emails land before you scale. Compare options in our email deliverability test tools roundup.
• Meetings booked. The only metric your pipeline actually cares about.

If you already push leads from SyncGTM into a sender, the SyncGTM + Instantly integration sends verified contacts straight into a campaign.

Setup Checklist

Run this for every new sending domain.

1. SPF, DKIM, and DMARC pass on the sending domain.
2. Decide whether this domain needs tracking at all. If not, switch tracking off and stop here.
3. Add the vendor's CNAME on a subdomain of the sending domain (host only, no doubled domain).
4. For lemlist, add the generated TXT record on @.
5. On Cloudflare, set the record to DNS only.
6. Verify in the tool and with a CNAME lookup.
7. Enable the tracking domain on every mailbox using that domain.
8. Warm the domain before launch. Our email domain warmup guide covers the schedule.
9. Run an inbox placement test on the full sequence before scaling.

Conclusion

A custom tracking domain takes one DNS record and five minutes of work per domain. If you track opens or clicks, it is the cheapest deliverability fix available, because it stops you from sharing a link domain with every other sender on the platform.

The bigger decision is whether to track at all. For most cold email, turn opens off, keep clicks for link-driven emails only, and judge campaigns on replies, bounces, and meetings.

Clean lists matter as much as clean DNS. Try SyncGTM free to find and verify every contact before your next campaign goes out.