Docs

User Guide

User Guide / Sequences

Custom Tracking Domains

Configure an organization-owned subdomain for tracking links in sequence emails.

A custom tracking domain lets Rox serve email tracking through a subdomain your organization owns, such as track.example.com.

When open tracking is enabled, a small image in the email records an event when it loads. A custom tracking domain changes the domain used for that tracking request. It does not change the email address that sends the message or guarantee inbox placement.

Before you start

You need the Admin role in Rox and access to your domain's DNS configuration, or help from someone who manages it. Choose the subdomain you want to use and coordinate with your DNS administrator before changing records.

1. Add the domain in Rox

  1. Open Settings → Sequences.

  2. Find Custom Tracking Domains and select Add Custom Tracking Domain.

  3. Enter your chosen subdomain, such as track.example.com.

  4. Select Create.

Rox displays the domain as Pending and provides the CNAME target to configure.

2. Create the DNS record

At your DNS provider, add a CNAME record using the target displayed in Rox.

Setting

Example value

Type

CNAME

Name / Host

track for track.example.com, if your provider appends the parent domain automatically

Value / Target

cname.rx-prod-trk.com

TTL

Provider default

Proxy / CDN

Disabled. Use a DNS-only record

Check whether your provider expects the subdomain label or the full hostname in the name field. For Cloudflare, select DNS only rather than a proxied record.

3. Verify the domain

Return to Settings → Sequences and select Verify next to the domain. Rox checks that the CNAME points to the expected target.

After successful verification, the domain becomes Verified and Rox provisions a TLS certificate in the background. If verification fails, check the record and allow time for DNS propagation before trying again.

4. Activate the domain

Select Activate to enable the domain. Use Set as Default if you want it to be the organization's default tracking domain. Only one domain can be the organization default at a time.

If you use multiple sending domains, review the tracking-domain selection for each connected mailbox in Deliverability settings. See Multiple Mailboxes.

Troubleshoot verification

Issue

What to check

The domain cannot be verified

Confirm the hostname and CNAME target match the values in Rox.

The record was just added

Wait for DNS propagation, then retry verification.

The record uses a proxy

Disable the proxy and use a DNS-only CNAME.

Verification succeeds but setup is incomplete

Review the domain's activation state and any certificate-related status shown in Rox.

Your DNS administrator can inspect the record with:

The result should match the target displayed in Rox, for example:

Understand open-tracking results

A custom tracking domain changes the domain used for tracking requests. It does not distinguish recipient opens from automated scans or self-opens. See Understanding email open tracking for how Rox filters early opens and how to interpret the results.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.