Order queue open · Verified lists delivered within 24–48 hours
How to set up custom tracking domains in Instantly 2026: what tracking domains do to open and click tracking, how to add the CNAME DNS record, how to verify in Instantly, and the deliverability impact of shared vs. custom tracking domains.
Marcus Chen
Outbound sales trainer, 150k+ emails sent · Updated June 24, 2026
Last updated: June 2026 · Marcus Chen, Outbound sales trainer, 150k+ emails sent
TL;DR — 5 things to know before reading
track.yourdomain.com) that only your Instantly account uses, isolating your tracking domain reputation from other senders on the platformCustom tracking domains are one of those setup steps that get skipped because the default shared tracking domain works fine on day one. The problem emerges at scale: shared tracking domains are used by hundreds or thousands of senders, and if other senders on the same shared domain engage in poor practices that trigger spam filter blacklisting, your click tracking and open tracking reliability degrades even though you did nothing wrong.
Setting up a custom tracking domain takes 15–30 minutes and provides permanent isolation of your tracking infrastructure. It is a one-time task, not an ongoing maintenance burden. After 150,000+ emails sent, this is one of the setup steps I do before launching any high-volume campaign. Instantly makes the configuration straightforward; Inframail handles the email sending infrastructure; Quarvio provides the verified contacts whose opens and clicks the tracking domain records; Aimfox covers the LinkedIn channel tracking separately.
This guide covers the full end-to-end process: what tracking domains actually do, how shared vs. custom domains affect deliverability, every step of the DNS configuration with sub-steps and failure modes, the configuration reference table, advanced tracking domain setup tactics, and troubleshooting for every common failure mode.
When Instantly sends an email with open tracking enabled, it embeds a small invisible pixel image in the HTML email body. The image is hosted on the tracking domain. When the recipient's email client downloads the image to render the email (or when Apple Mail Privacy Protection prefetches the email), Instantly's tracking server receives the request and records an open for that contact.
The pixel URL looks something like: track.yourdomain.com/pixel/abc123xyz
If the tracking domain is unavailable, blacklisted, or filtered by a corporate email security gateway, the pixel does not load and the open is not recorded — producing artificially low open rates.
When Instantly inserts a link into an email, it replaces your destination URL with a redirect URL hosted on the tracking domain. When a recipient clicks the link, their browser first visits the tracking domain (recording the click), then immediately redirects to your intended destination URL.
The redirect URL looks something like: track.yourdomain.com/click/abc123xyz
If the tracking domain is blacklisted or flagged by an email security gateway, the redirect URL may:
When Instantly's default shared tracking domain is used by thousands of senders simultaneously, any single sender's poor practices can affect the shared domain's reputation. If one sender on the network runs a high-volume spam campaign that gets the tracking domain blacklisted, every other sender's open and click tracking reliability degrades immediately — without any action on their part.
A custom tracking domain creates a 1:1 relationship between your Instantly account and the tracking domain. Only your emails use this domain for tracking, so only your sending behavior determines the domain's reputation.
They do not improve inbox placement directly. Tracking domain setup is an isolation measure, not a deliverability improvement in itself. Inbox placement depends on sending domain warmup, DNS authentication records (SPF, DKIM, DMARC), and contact list quality.
They do not remove the need for open tracking to be enabled. Open tracking requires HTML email. If recipients have image loading disabled or use text-only email clients, open tracking will not record opens regardless of which tracking domain is configured.
They do not affect deliverability of the sending domain. The sending domain (the domain in the From: address) and the tracking domain are separate. A well-configured tracking domain does not compensate for a poorly warmed or blacklisted sending domain.
They do not track LinkedIn clicks. LinkedIn outreach tracking is managed by Aimfox's separate analytics. The custom tracking domain in Instantly only applies to email campaigns.
Before configuring the custom tracking domain in Instantly, confirm you have the following:
An Instantly account with at least one active campaign: The tracking domain setting is accessible in Instantly's settings, but it is most useful once you have active campaigns to apply it to.
Access to a domain you control: The tracking domain must be a subdomain of a domain whose DNS records you can edit. You need login access to the DNS management panel for this domain — typically your domain registrar (Namecheap, GoDaddy, Cloudflare, Google Domains, or similar).
The domain must be at least 3–6 months old: A newly registered domain used for tracking raises trust signals with email security systems. If you are registering a new domain specifically for tracking, allow 3+ months before using it as a tracking domain, or use an existing domain you already control.
A clear understanding of which subdomain prefix to use: track, trk, click, open, and em are all common prefixes. The subdomain prefix does not affect functionality — choose one and use it consistently. track.yourdomain.com is the most common and most readable choice.
Sub-step 1.1: Decide whether to use a new domain or a domain you already own.
The recommended approach is a dedicated domain for outreach tracking infrastructure: a domain separate from your primary brand domain and separate from your sending domains. This creates clean separation between your primary brand identity and your cold outreach infrastructure.
Example: If your company is CompanyName and your primary domain is companyname.com, your sending domains might be outreach-companyname.com and hello-companyname.com (via Inframail), and your tracking domain might be cn-metrics.com or companyname-track.com.
Sub-step 1.2: If using an existing domain, confirm you have DNS edit access.
Log in to your domain registrar or DNS management panel (Cloudflare, Namecheap, GoDaddy, or wherever your DNS is managed). Confirm you can see the DNS records for the domain and have the ability to add new CNAME records.
Sub-step 1.3: Choose your subdomain prefix.
The subdomain is the part before the root domain: track in track.cn-metrics.com. Common prefixes:
track — clear and professionaltrk — shorter, equally commonem — common for email marketing platformsclick — specific to click trackingChoose one prefix. The same prefix will be used throughout your Instantly configuration.
Sub-step 1.4: Confirm the subdomain does not conflict with an existing record.
In your DNS management panel, check whether the subdomain prefix you want (e.g., track) already has an A, CNAME, or MX record on this domain. If it does, either use a different prefix or remove the conflicting record first.
Benchmark: The right domain choice has three characteristics: it is a domain you control with DNS edit access, it is not your primary brand domain, and the subdomain prefix you want is not already in use.
Failure mode: Trying to use track.companyname.com when your primary brand domain is companyname.com. If your brand domain gets associated with cold outreach infrastructure, it can affect brand reputation. Use a separate dedicated domain.
Sub-step 2.1: Navigate to your DNS management panel for the tracking domain.
Every registrar has a slightly different interface, but all provide a section to manage DNS records. The most common path is: Domain Management → DNS → DNS Records or Zone Editor.
Sub-step 2.2: In Instantly, retrieve the exact CNAME target value for your account.
Navigate to Settings → Tracking Domains → Add Tracking Domain in Instantly. Instantly will display the exact CNAME value to add to your DNS. This value is specific to Instantly's tracking infrastructure and changes occasionally as Instantly updates its servers — always copy the value from your Instantly account settings, not from a guide or memory.
Sub-step 2.3: Add the CNAME record in your DNS panel.
In your DNS management panel, add a new record with these values:
| Field | Value |
|---|---|
| Type | CNAME |
| Name / Host | track (or your chosen subdomain prefix) |
| Value / Target | [Copy exact value from Instantly Settings → Tracking Domains] |
| TTL | 3600 (1 hour) |
The exact value for the target/value field is provided in your Instantly account. Do not use a value from memory or a third-party guide — copy it directly from your Instantly account's tracking domain setup screen.
Sub-step 2.4: Save the DNS record and note the timestamp.
After saving, note the exact time. CNAME records typically propagate within 15–60 minutes for most DNS providers, but propagation time varies. A 30-minute wait is usually sufficient before attempting verification.
Benchmark: The CNAME record is correctly configured when the Type is CNAME, the Name matches your chosen subdomain prefix exactly, the Value matches the Instantly-provided target exactly, and the TTL is 3600 or similar.
Failure mode: Entering the root domain (e.g., yourdomain.com) as the Name instead of just the subdomain prefix (e.g., track). This creates a record for yourdomain.com.yourdomain.com rather than track.yourdomain.com and will fail verification. Enter only the subdomain prefix in the Name field, not the full domain.
Sub-step 3.1: Wait a minimum of 30 minutes after adding the CNAME record before attempting verification.
DNS propagation is the process by which the new CNAME record spreads across DNS resolvers globally. Most modern DNS providers (Cloudflare, Namecheap) propagate changes within 5–15 minutes. Legacy DNS providers may take up to 24 hours in rare cases.
Sub-step 3.2: If you want to confirm propagation before attempting verification in Instantly, use an external DNS lookup tool.
Navigate to MXToolbox DNS Lookup and search for your full tracking subdomain (e.g., track.yourdomain.com). If the CNAME record has propagated, the lookup will show the target value you entered. If it shows no record or an error, propagation is not yet complete — wait another 15 minutes and check again.
Sub-step 3.3: For Cloudflare users specifically: confirm proxy status.
If your domain is managed through Cloudflare and you have Cloudflare's proxy (orange cloud) enabled for the tracking subdomain record, disable it. The tracking subdomain CNAME should have the grey cloud (DNS only) status in Cloudflare, not the orange cloud (proxied). A proxied CNAME will not work correctly for tracking domain verification because Cloudflare's proxy changes how the CNAME resolves.
Benchmark: DNS propagation for a CNAME record takes 15–60 minutes for most providers. If verification is still failing after 60 minutes, investigate the record configuration rather than waiting longer.
Failure mode: Attempting verification in Instantly 2 minutes after adding the DNS record and concluding it does not work when propagation simply has not completed. Allow at least 30 minutes and use MXToolbox to confirm propagation before troubleshooting.
Sub-step 4.1: Navigate to Settings → Tracking Domains in Instantly.
Sub-step 4.2: Click Add Tracking Domain and enter your full tracking subdomain.
Enter the full subdomain: track.yourdomain.com (not just track or yourdomain.com). Instantly needs the complete subdomain to verify the CNAME record.
Sub-step 4.3: Click Verify or Check DNS.
Instantly will attempt to resolve the CNAME record and confirm that it points to Instantly's tracking server. If verification succeeds, the tracking domain is marked as active in Instantly and ready to assign to campaigns.
Sub-step 4.4: If verification fails, troubleshoot in this order:
track.yourdomain.com), not the root domain (e.g., yourdomain.com)Benchmark: Verification succeeds within 30–60 minutes of adding a correctly configured CNAME record. If verification has been failing for 2+ hours with no changes to the DNS record, the issue is almost certainly the CNAME value not matching Instantly's expected target.
Failure mode: Re-adding the tracking domain with a typo in the subdomain (e.g., tack.yourdomain.com instead of track.yourdomain.com). Always copy-paste the full subdomain from a trusted source rather than typing it manually.
Sub-step 5.1: Once verified, navigate to each active campaign's settings.
Sub-step 5.2: In the campaign settings, locate the tracking domain section.
In Instantly, this is typically under Campaign Settings or within the campaign creation flow. Look for a dropdown that shows "Default tracking domain" or "Shared tracking domain" — change it to your custom tracking domain.
Sub-step 5.3: Save the campaign settings after updating the tracking domain selection.
Sub-step 5.4: For new campaigns being created from this point forward, select the custom tracking domain during the campaign creation flow rather than leaving it as the default.
Note: Emails already sent before this configuration change are not retroactively affected. Only future sends from the campaign will use the new tracking domain. If a campaign has already sent to many contacts, the historical analytics data (from before the switch) used the old tracking domain; future sends will use the new one.
Benchmark: After completing this step, all new sends from the campaign will route open tracking pixels and click tracking redirects through your custom domain rather than the Instantly shared domain.
Failure mode: Updating the tracking domain setting in Instantly but failing to save the campaign settings before navigating away. The change reverts to the default. Always confirm the tracking domain selection persists after saving by reopening campaign settings to verify.
Sub-step 6.1: Send a test email from the campaign to yourself.
Use the campaign's test send feature in Instantly to send one email to your personal email address. This test email will use the custom tracking domain for both the open pixel and any tracked links.
Sub-step 6.2: Open the test email on a device where image loading is enabled.
On a desktop email client (Gmail in Chrome, Outlook in Windows), open the email and allow images to load. Do not use Apple Mail for this test because Apple MPP will fire the open tracking pixel automatically before you open the email, making it harder to confirm the test worked correctly.
Sub-step 6.3: Return to Instantly and check campaign analytics.
After opening the test email, refresh the campaign analytics view. If the custom tracking domain is working correctly, the test open will appear in the analytics. If it does not appear within 5 minutes of opening the email, the tracking domain may not be correctly connected.
Sub-step 6.4: Click any tracked link in the test email.
If the campaign includes tracked links (Calendly, case study, content resource), click one in the test email and confirm: (1) the browser is redirected through your custom tracking domain URL briefly before landing on the destination, and (2) the click appears in Instantly's analytics within a few minutes.
Benchmark: A successful test shows the test open appearing in Instantly analytics within 5 minutes of opening the email on a desktop client with images enabled.
Failure mode: The test open does not appear even after 10 minutes. This indicates either image loading is disabled in the test email client (try Gmail in Chrome with image loading enabled), or the tracking domain configuration has a problem not caught during the verification step — proceed to the troubleshooting section.
Once the custom tracking domain is set up and verified, make it the default for all new campaigns. There is no advantage to using the shared tracking domain for some campaigns and the custom tracking domain for others — the custom domain provides isolation that benefits every campaign, and there is no cost to using it universally.
In Instantly, check whether there is a global default tracking domain setting (under Settings → Tracking Domains) that can be set as the account-wide default, so new campaigns automatically use it without manual selection per campaign.
| Configuration | Type | Name/Host | Value/Target | TTL | Notes |
|---|---|---|---|---|---|
| Tracking subdomain CNAME | CNAME | track (or your prefix) | [Copied from Instantly Settings] | 3600 | Copy value exactly; do not type from memory |
| Alternative prefix | CNAME | trk (or click, em) | [Same Instantly value] | 3600 | Use any prefix that does not conflict |
| Cloudflare proxy status | N/A | N/A | N/A | N/A | Must be grey cloud (DNS only), not orange (proxied) |
| MXToolbox verification | N/A | track.yourdomain.com | N/A | N/A | Use to confirm propagation before Instantly verification |
| Multiple subdomains | CNAME x N | track1, track2, etc. | Same Instantly value | 3600 | Optional: one per campaign type |
| Domain age requirement | N/A | N/A | N/A | N/A | Use a domain at least 3–6 months old |
| Root domain | Do not use | N/A | N/A | N/A | Never use the root domain as a tracking domain |
| Sending domain | Do not use | N/A | N/A | N/A | Tracking domain must be separate from sending domain |
A single tracking domain can serve all your campaigns. But at high volume (500+ emails per day), separating tracking domains by campaign type provides an additional layer of isolation:
cold.yourdomain.com — for cold outreach campaignsnurture.yourdomain.com — for warm follow-up or re-engagement campaignsevent.yourdomain.com — for event-triggered campaignsThis separation means a reputation problem in one campaign type does not affect tracking for other campaign types. Each subdomain requires its own CNAME record in DNS pointing to Instantly's tracking server.
Your custom tracking domain has its own reputation with email security systems, separate from your sending domain. A tracking domain that appears in spam emails (even from previous uses of the domain) can get flagged by email security gateways, causing tracked links to trigger security warnings.
Check your tracking domain on MXToolbox Blacklist Check monthly. If the tracking domain appears on any blacklist, pursue delisting immediately. Most blacklist operators provide a self-service delisting process for domains that can demonstrate they are no longer used for spam.
Also check whether your tracking domain is being flagged by Virustotal or major email security vendors. A clean tracking domain should return no flags on these tools.
If your tracking domain gets blacklisted and delisting proves difficult, or if you want to start fresh with a new reputation, you can rotate to a new tracking domain. The process:
Rotating tracking domains is typically necessary at most once every 12–24 months, and only when the tracking domain's reputation has been meaningfully damaged.
If your campaigns target contacts in multiple regions and you send significant volume into markets with different email security standards (US, EU, APAC), consider separate tracking domains per region. Some regional email security gateways flag domains more aggressively than others; isolation prevents one region's security environment from affecting another's tracking accuracy.
This is an advanced configuration that most practitioners do not need until they are running very high volume across multiple distinct geographic markets.
Changes in click tracking accuracy (sudden drops in click rate on campaigns where links were previously being clicked) are often the first visible sign of tracking domain reputation problems — before those problems affect inbox placement or open rates. Monitor click rate trends across campaigns as a leading indicator of tracking domain health.
If click rates drop across multiple campaigns simultaneously with no change in the emails themselves, investigate the tracking domain reputation before investigating the campaigns.
They do not improve inbox placement directly. Tracking domain setup is an isolation measure, not a deliverability improvement in itself. If your sending inboxes have poor warmup scores or your contact list has high bounce rates, changing the tracking domain will not improve those metrics.
They do not remove the need for open tracking to be enabled. Open tracking relies on HTML email. If recipients have image loading disabled or use text-only email clients, open tracking will not record opens regardless of which tracking domain is configured.
They do not track LinkedIn clicks. LinkedIn outreach tracking is managed by Aimfox's separate analytics. The custom tracking domain in Instantly only applies to email campaigns.
If your cold email sequences deliberately exclude links in the first 2–3 steps (a common deliverability practice for cold outreach), click tracking is not relevant for those steps. Open tracking still uses the domain, so a custom tracking domain remains useful for open rate accuracy even in link-free sequences.
If you are testing a new campaign with fewer than 200 contacts, the shared default tracking domain is adequate. The shared domain risk is a scale concern — at low volumes, the impact of a shared domain issue is minimal.
Symptom: The CNAME record is added and MXToolbox confirms it is visible, but Instantly's verification step continues to fail.
Cause: The most common cause is a mismatch between the CNAME value in the DNS record and the CNAME value Instantly expects. Even a single character difference (a missing dot, a typo) will cause verification failure. A second common cause for Cloudflare users is the proxied status (orange cloud) being active on the CNAME record.
Fix: Export or screenshot the exact CNAME value from Instantly's settings screen. Go to your DNS panel and view the current CNAME record. Compare character by character. If using Cloudflare, confirm the record is set to DNS-only (grey cloud). If the values match and Cloudflare is not the issue, contact Instantly support with a screenshot of the DNS record and the error message from the verification attempt.
Symptom: Open rate was showing data before the switch to the custom tracking domain. After the switch, open rate shows 0% for new sends.
Cause: The custom tracking domain was set to active in Instantly but not correctly applied to the campaign. The campaign is still sending with the old default tracking domain configuration, or the campaign settings were not saved after updating the tracking domain selection.
Fix: Navigate to the campaign settings and confirm the tracking domain selection shows your custom tracking domain, not the default. If it shows the default, update it and save. Send a test email to yourself and confirm the open tracking pixel in the email source code is loading from your custom domain (not the Instantly shared domain). If the pixel URL in the email source shows your custom domain, the configuration is correct and the issue may be image loading being disabled on recipient email clients.
Symptom: When recipients click tracked links in the email, they either get a security warning, the link does not redirect to the correct destination, or the click is not recorded in Instantly.
Cause: Three possible causes: (1) the tracking domain CNAME is resolving correctly but the subdomain has been flagged by an email security service, causing the redirect to be blocked; (2) the link was not inserted through Instantly's tracked link system; (3) the tracking domain is correctly configured but the destination URL has changed since the campaign was created.
Fix: For cause (1), check the tracking domain on MXToolbox Blacklist Check and on Virustotal. If flagged, pursue delisting or rotate to a new tracking domain. For cause (2), edit the campaign sequence and re-insert the link through Instantly's link insertion tool. For cause (3), update the destination URL in the tracked link within the campaign sequence editor.
Symptom: After checking the tracking domain on MXToolbox, it appears on one or more blacklists. Click rates have dropped and some recipients may be seeing security warnings.
Cause: The tracking domain's previous use (or current use if another subdomain on the same root domain is being used for spam) has triggered a blacklist listing. A new domain used for tracking too soon after registration can also get pre-emptively flagged by some conservative email security vendors.
Fix: Use MXToolbox's blacklist checker to identify which specific blacklists the domain appears on. Visit each blacklist operator's website and submit a delisting request. Most operators provide automated delisting for domains that meet their clean criteria. For domains that cannot be delisted, rotate to a new tracking domain. Ensure the new domain is at least 3–6 months old before using it as a tracking domain.
Symptom: When attempting to add the CNAME record for track.yourdomain.com, the DNS panel displays an error saying a record already exists for that name.
Cause: An existing A record, MX record, or another CNAME record already exists for the track subdomain. DNS does not allow a CNAME to coexist with other records for the same name.
Fix: In the DNS panel, view all records for the track subdomain. If there is an existing A record pointing to an IP address, check whether the subdomain is actively being used for another purpose. If it is not in use, delete the existing record and add the CNAME. If it is in active use (e.g., a web server at track.yourdomain.com), choose a different subdomain prefix (e.g., trk or em) for the tracking domain CNAME.
Symptom: The tracking domain was added and verified in Instantly's settings, but when opening campaign settings, the custom tracking domain does not appear in the tracking domain dropdown.
Cause: The tracking domain may need a hard refresh in Instantly's interface after verification, or the verification may not have actually completed despite appearing to succeed.
Fix: Log out of Instantly and log back in. Navigate to Settings → Tracking Domains and confirm the custom tracking domain shows a verified status. If it shows pending or unverified, repeat the verification process. If it shows verified, open the campaign settings again — the hard session refresh often resolves the dropdown not displaying newly verified domains.
Symptom: The CNAME record was added 2+ hours ago but MXToolbox still does not show it, and Instantly verification still fails.
Cause: Some DNS providers have longer propagation times than others, particularly legacy registrars or hosting provider DNS panels (as opposed to specialized DNS providers like Cloudflare). Propagation of up to 24 hours is technically possible with some providers.
Fix: Check your domain registrar or DNS provider's documentation for typical propagation times. If your DNS is managed through a legacy hosting provider (like GoDaddy's default DNS or certain ISP-managed DNS), propagation times can be 4–12 hours. If you regularly need faster DNS propagation, consider migrating DNS management to Cloudflare (free tier) where changes propagate in under 5 minutes. While waiting, do not add additional DNS records or modify the existing one — changes reset the propagation timer on some providers.
Symptom: When reviewing per-inbox analytics in Instantly, open rates and click rates look very different between inboxes in the same campaign, even though all inboxes should be reaching a similar audience.
Cause: This is typically not a tracking domain issue — it is a contact distribution issue. Different inboxes in a campaign are usually assigned different contact batches, and if one batch has lower quality (higher proportion of Apple Mail users where MPP fires automatically, or contacts at companies with aggressive email security gateways that block pixels), that inbox will show higher or lower open rates than others.
Fix: Navigate to the per-inbox breakdown in Campaign Analytics. Identify which inbox shows anomalous metrics. Compare the contact batches assigned to the anomalous inbox versus the normal inboxes. If contacts are clustered by company or industry in a specific inbox and that industry (legal, healthcare, government) commonly uses aggressive email security, the anomalous metrics are expected. No tracking domain fix is needed — the anomaly is in the audience, not the infrastructure.
Instantly reviews on G2 show practitioners using custom tracking domains as a standard part of their deliverability setup, particularly at volumes above 300 emails per day where shared domain risk accumulates faster.
Mailgun documentation provides technical reference on how CNAME-based tracking domains work and why dedicated domains improve deliverability isolation — the same principles apply regardless of email platform.
"I set up a custom tracking domain when I hit 500 emails per day. Before that, I had noticed that my click-through data was inconsistent — some campaigns showed 0% clicks when I knew links were being clicked. After moving to a dedicated tracking domain, the data became reliable and consistent. It took 20 minutes to set up and I have not thought about it since."
— Verified G2 reviewer, cold email operator, B2B SaaS, Instantly reviews on G2
"A shared tracking domain is a liability you do not control. If one bad actor on the same network gets their outreach flagged and the tracking domain hits a blacklist, your open tracking accuracy drops and your links get flagged. A dedicated tracking domain takes 15 minutes to set up and removes that dependency entirely."
— Verified G2 reviewer, cold email consultant, Instantly reviews on G2
| Need | Tool | Notes |
|---|---|---|
| Verified B2B contacts | Quarvio | One-time purchase, no subscription |
| Email inboxes | Inframail | Microsoft 365 inboxes, auto DNS |
| Cold email sending | Instantly | Sequences, warm-up, reply tracking |
| LinkedIn outreach | Aimfox | Connection campaigns, Unibox |
| Blacklist check | MXToolbox Blacklist Check | Free domain reputation check |
What is a custom tracking domain in Instantly and why does it matter?
A custom tracking domain is a dedicated subdomain (e.g., track.yourdomain.com) that Instantly uses exclusively for your account to record email opens and link clicks, rather than the shared tracking domain used by all Instantly users. It matters because shared tracking domains carry shared reputation risk: if another sender on the same shared domain gets blacklisted or triggers spam filters, your open and click tracking accuracy degrades immediately even though you did nothing wrong. A custom domain isolates your tracking infrastructure so only your sending behavior determines the domain's reputation.
How do I set up a custom tracking domain in Instantly step by step?
In Instantly, navigate to Settings → Tracking Domains and copy the CNAME value displayed for your account. Log in to your domain registrar's DNS management panel. Add a new CNAME record: Name = your chosen subdomain prefix (e.g., track), Value = the CNAME value copied from Instantly, TTL = 3600. Wait 30–60 minutes for DNS propagation. Return to Instantly's Tracking Domains settings, enter your full subdomain (track.yourdomain.com), and click Verify. Once verified, apply the tracking domain to your active campaigns in Campaign Settings. Send a test email to confirm tracking is working.
What CNAME record do I add for an Instantly custom tracking domain?
Type: CNAME. Name/Host: your chosen subdomain prefix (typically track, trk, or em). Value/Target: the exact value shown in Instantly's Settings → Tracking Domains screen for your account. TTL: 3600. The target value is specific to Instantly's infrastructure and is provided in your account — always copy it from there rather than using a value from memory or a guide. For Cloudflare users, set the record to DNS-only (grey cloud), not proxied (orange cloud).
Do I need a custom tracking domain on every sending domain in Instantly?
No. One custom tracking domain can serve all campaigns across all sending inboxes in your Instantly account. The tracking domain is completely separate from the sending domain — it only handles the open pixel and click redirect, not the actual email delivery. Add one custom tracking subdomain and apply it to all campaigns.
How long does DNS propagation take for an Instantly tracking domain?
For most DNS providers, 15–60 minutes. Cloudflare propagates changes in under 5 minutes. Legacy registrar DNS panels (GoDaddy default DNS, hosting provider DNS) can take up to 12–24 hours. If you need faster propagation, migrate DNS management to Cloudflare. Do not attempt verification in Instantly until at least 30 minutes have passed after adding the CNAME record, and use MXToolbox DNS Lookup to confirm propagation before troubleshooting.
Why is my Instantly custom tracking domain verification failing?
The most common causes are: (1) the CNAME value in your DNS does not exactly match the value shown in Instantly's settings — compare character by character; (2) DNS propagation is not yet complete — wait 30–60 minutes and try again; (3) you are entering the full subdomain in the Instantly verification field but your DNS entry only has the prefix without the root domain (or vice versa); (4) for Cloudflare users, the CNAME is set to proxied (orange cloud) instead of DNS-only (grey cloud). Resolve in this order before contacting support.
Will a custom tracking domain improve my open rate in Instantly?
Indirectly. A custom tracking domain prevents shared domain blacklisting from causing open tracking under-reporting. If your open rate was being suppressed by tracking pixel blocks caused by a shared domain issue, a custom domain will produce more accurate (and potentially higher-reported) open rates. However, the custom tracking domain itself does not change inbox placement. Inbox placement depends on sending domain warmup, DNS authentication (SPF, DKIM, DMARC), and contact list quality — not on the tracking domain.
What domain should I use for a custom tracking domain in Instantly?
Use a dedicated subdomain on a domain you already own that is not your primary business domain and not your sending domain. The best practice is to register a separate domain specifically for cold outreach tracking infrastructure — something like [yourname]-metrics.com or [brand]-track.com — and create a track. subdomain on it. This keeps tracking infrastructure on a dedicated domain that carries no primary brand reputation and no sending domain reputation.
Can I use the same tracking domain for multiple campaigns in Instantly?
Yes. One custom tracking domain handles all campaigns in your Instantly account. There is no need to create separate tracking domains per campaign. Advanced practitioners running very high volume (500+ emails per day) sometimes create separate tracking subdomains per campaign type (cold outreach, re-engagement, event-triggered) for additional reputation isolation, but this is not necessary for most use cases.
What happens if my tracking domain gets blacklisted?
If the tracking domain appears on a blacklist, click tracking links in your emails may trigger security warnings for recipients, and click rates will drop. Open tracking accuracy may also degrade. First, check which blacklists the domain appears on using MXToolbox Blacklist Check and submit delisting requests to each blacklist operator. If delisting is not possible, rotate to a new tracking domain: register a new domain, wait 3–6 months for it to age, configure it as the new tracking domain in Instantly, and update all campaigns.
How do I know if my custom tracking domain is working in Instantly?
Send a test email from the campaign to yourself. Open the email on a desktop email client with image loading enabled. Return to Instantly's Campaign Analytics within 5 minutes — if the tracking domain is working, the test open will appear in the analytics. Click any tracked links in the test email and confirm the click also appears. If the open appears and click is recorded, the tracking domain is working correctly.
Should I use a subdomain or a new domain for Instantly tracking?
Always use a subdomain of an existing domain (e.g., track.yourdomain.com), not a root domain (e.g., yourdomain.com). The tracking domain setup requires adding a CNAME record at the subdomain level — you cannot add a CNAME at the root domain level because root domains require an A record or similar. Use the subdomain approach: choose a prefix (track, trk, em), add it as a CNAME on an existing domain, and enter the full subdomain during Instantly verification.
How often do I need to update or reconfigure the tracking domain?
Once configured correctly, the tracking domain requires no routine maintenance. The CNAME record is permanent as long as Instantly's tracking server address does not change, and Instantly will notify you if their server address changes and your domain needs updating. The only reasons to reconfigure are: (1) the tracking domain gets blacklisted and needs rotation, (2) you want to consolidate to a new domain infrastructure, or (3) Instantly updates their CNAME target value and sends a notification to update your DNS.
Accurate tracking starts with contacts that actually open your emails
Custom tracking domains fix tracking accuracy; contact quality determines whether there are opens and clicks to track. Quarvio delivers pre-verified B2B contact lists that reach real inboxes — no invalid addresses to inflate bounce rates or trigger blacklisting on your sending domain. One-time purchase, credits valid 12 months, no subscription.