Custom tracking domains

A custom tracking domain lets the open-tracking pixel and click-redirect links in your emails run through a subdomain you own (for example track.yourdomain.com, set as a CNAME to the vendor) instead of the vendor's shared tracking domain. Buyers care because a shared tracking domain pools every customer's reputation. If one spammer on the platform gets the shared domain blocklisted, everyone's links look suspect.

#How it works

Open tracking embeds a tiny image whose URL is unique per recipient. When the image loads, the vendor records an "open". Click tracking rewrites every link to a vendor redirect that logs the click and forwards the reader. Both need a hostname. By default that is the vendor's: Instantly documents that without a custom domain it uses a shared URL like "xyz.inreg1.com/[code]" across all customers. With a custom domain the user adds a CNAME (Instantly's target is prox.itrackly.com), and links then show the sender's own domain.

#Who does it well

There is little to separate vendors on the domain itself: a CNAME and a verification check. Instantly does the most around it. It publishes registrar-specific setup guides, lets you turn off open tracking for every campaign, and can send the first email as plain text. Its open-tracking help says global settings override campaign settings, so one switch enforces the policy across an agency's clients.

#Where implementations differ

• Setup friction. Manual CNAME setup per domain multiplies with Inbox rotation. An agency with 50 domains needs 50 records. Automating DNS through registrar APIs or bundled infrastructure (Inbox & domain infrastructure) is the differentiator, not the feature itself.
• Scope. Per workspace (EmailBison) versus per domain or mailbox. Domain alignment, where each sending domain uses its own tracking subdomain, is the cleanest. One tracking domain shared across 50 sending domains creates a cross-domain footprint that ties the whole fleet together.
• Defaults. No leader documents tracking as off by default. Instantly's open-tracking article tells users to enable it manually per campaign (help).

#Risks and abuse

Shared tracking domains are a commons that the worst customer can ruin. That is the reason for the feature, and a platform-level liability for the vendor (Platform liability: what the sequencer itself risks). Custom domains move the risk to the customer, but a single tracking domain reused across a rotated fleet links otherwise separate sending domains for any filter that looks at link hosts (Content and tracking, How filtering works). Open tracking is also increasingly unreliable: Apple Mail Privacy Protection loads pixels automatically, and many corporate gateways pre-click links to scan them, which creates fake "clicks". Decisions built on these signals (A/B testing, Conditional sequences and subsequences) inherit the noise.

#What this means for an entrant

• Ship custom tracking domains with automatic DNS setup and HTTPS, one tracking subdomain per sending domain, configured at domain purchase (Infrastructure strategy: build or partner).
• Default open tracking off and make click tracking opt-in per link. Explain why in the UI.
• Build Campaign analytics around replies, positive replies and meetings, so turning tracking off costs the user nothing they need.
• Detect bot clicks from security gateways and exclude them from metrics and branching. Few vendors document doing this.
• Never let customer traffic share a tracking hostname. It is cheap insurance against platform-wide blocklisting.