Do custom click-tracking domains matter for newsletters?

Search for advice on a custom click tracking domain and you get cold-outreach vendors telling you a branded CNAME will rescue your inbox placement. That framing comes from a world where the shared redirect host is crowded with people mailing strangers. Newsletters are not that world, and the advice does not transfer. A custom click-tracking domain is a branding and risk-isolation decision. Treating it as a deliverability fix is how people spend a Tuesday on DNS and change nothing about their open rate.

Why your newsletter links point at a domain you do not own

Every ESP with click tracking enabled rewrites your anchors before the message leaves. A link you wrote as https://example.com/pricing ships as a link to a host the vendor runs. That host logs the click and redirects to your real destination, which is why the click registers even though the subscriber lands where you intended.

The defaults are worth knowing by name, because they are what shows up on hover. Amazon SES routes clicks and opens through region-specific hosts it operates, such as r.us-east-1.awstrack.me. Klaviyo's shared default is trk.klaviyomail.com or trk.klclick.com. Mailchimp's transactional product writes both the open pixel and the click URLs against mandrillapp.com. SendGrid puts sendgrid.net in the links, or eu.sendgrid.net for regional sending.

What it takes to replace those varies more than the marketing pages suggest. Resend hands custom tracking domains to every account at no cost. HubSpot lets you set a click tracking domain, but managing a separate one per brand needs the paid Brands add-on. SendGrid's link branding is not a single record: the setup adds two pairs of CNAMEs, four in total, and two more if you let SendGrid auto-provision the SSL certificate. On Amazon SES the custom redirect domain is a property of a configuration set rather than of your account, so two config sets in the same account can point at different hosts.

What a custom click-tracking domain changes

Two effects are real. The hostname on hover becomes yours, which matters more in sectors where phishing has trained people to read a URL first. And your link reputation stops being collective: if a vendor redirect host picks up a listing because of somebody else's campaign, your message is the one carrying a listed hostname.

The effect people expect and do not get is a deliverability lift. Nothing about pointing a CNAME at your ESP changes your authentication, your complaint rate, your list hygiene, or your engagement history. Those are what mailbox providers weigh. If your last six sends have been sliding, the answer is in the open rate decline diagnostic, not in your DNS zone.

There is a way to make things worse, and the SES setup is where we see it. Serving a custom redirect domain over HTTPS means putting a CDN such as CloudFront in front of the SES tracking host and uploading your own certificate. Skip that and you are on the default HttpsPolicy of OPTIONAL, which wraps open-tracking links in plain HTTP. A branded domain that downgrades to HTTP is worse than the vendor host you replaced, because now the insecure hostname has your brand on it.

Shared vs custom tracking domain: the real tradeoff

A shared vendor host is warm. It carries enormous volume daily, mailbox providers have years of history with it, and the vendor has commercial reasons to keep it clean. You get that for free and configure nothing. What you accept is that its reputation is not yours to control.

A custom domain inverts both halves. Nobody else can hurt it, and nobody else is helping it either. You are warming a subdomain that only your sends touch, and every listing your own links cause lands on a hostname with your name on it. Klaviyo makes a related point in its own docs: using the same root domain for click tracking and sending creates alignment across the two, which is a genuine argument for branding, and a different argument from deliverability rescue.

This is where cold-email advice goes wrong for newsletter senders. Their premise is that a shared redirect pool is full of senders mailing people who never asked. A Klaviyo or SendGrid marketing pool is mostly brands mailing opted-in lists. Pool composition is the entire argument, and almost nobody writing about tracking domains states it. Read the top results for this query and check how many describe who else is on the host they are telling you to leave.

Why domain blocklists treat your link host separately

Spamhaus DBL, SURBL and URIBL are domain and URI lists. They answer questions about hostnames found inside a message, which is why the host in your href has a reputation independent of the IP that delivered the mail. A clean sending IP does not vouch for a redirect host, and the reverse holds too.

We treat these as separate problems in our own infrastructure. Newsletrix runs a DNSBL sweep once a week, Sunday at 03:00 UTC, over every distinct sender domain across the newsletters we have analyzed, querying three zones: dbl.spamhaus.org, multi.surbl.org and multi.uribl.com. Building that taught us something that is not in most explainers. Both genuine listings and operational errors come back encoded inside 127.0.0.0/8. DBL listings live in 127.0.1.2 through 127.0.1.254. URIBL returns 127.0.0.1 to mean the query was refused, which is not a listing at all. Treat any 127.* answer as a hit and you will manufacture false positives, so we interpret return codes per zone.

The other thing that bites people: Spamhaus and URIBL refuse queries arriving through large public resolvers and answer with a sentinel code instead. Point a lookup at your ISP resolver and the result is meaningless. You need a recursive resolver you operate, or Spamhaus DQS, which is not subject to that block. Most "are we blocklisted" panics we have watched unfold turned out to be a resolver problem rather than a listing.

A custom click-tracking domain does not hide your ESP

Some people brand their click domain hoping to disappear from competitor tracking. It does not work, and we can say that from the inside, because our detector never looks at your links.

Platform detection in Newsletrix reads headers. High-confidence identification comes from vendor headers such as X-MC-User for Mailchimp, X-SG-EID for SendGrid, X-Klaviyo, X-Brevo, X-ConvertKit and X-HubSpot, plus the Return-Path, the Message-ID and the Received chain. When none of those resolve, we fall back to the List-Unsubscribe host at medium confidence. Not one branch of that logic asks where a link points. Branding your links hides you from a subscriber hovering an anchor and from nobody who reads a header. If you want the full version of that argument, we walk through it in how to find out what ESP any company uses.

The nuance is that some vendors bundle link branding with things that do matter. Brevo's branded subdomain replaces the tracking links and the Return-Path domain in one setup, so there the change does remove a header signal. Klaviyo's dedicated click tracking sits under your branded sending domain, producing hosts like trk.send.helloworld.com, so the two move together. Amazon SES keeps them separate: a configuration set's redirect domain has nothing to do with your verified sending identity. That asymmetry is why migration timing reads differently per platform, which we cover in how to tell if a company switched ESP. Our Klaviyo analytics comparison lays out which of these signals its reporting exposes.

How to check your own links in five minutes

Send yourself the next issue and open it on desktop. Hover a link and read the status bar. That hostname is what your subscribers see. Then view the source and read the raw href, because the visible text and the target are different strings and only one of them gets evaluated.

Check three things in the source. Whether the host is a vendor default or yours. Whether the scheme is https or has quietly downgraded. Whether anything else is stacked in front of your destination.

That last one is where we find the most damage. Our link extractor reads the href exactly as it ships, before any redirect resolves, because the pre-redirect string is what a content filter evaluates. Every wrapped link puts at least one vendor host in front of your destination, which is normal and fine. Put a public URL shortener inside a tracked link and there are now two hosts with two separate reputations before anyone reaches your page, and one of them is a shortener, which is a category filters have learned to distrust. Newsletters that do this are usually also over-linking, so it is worth reading alongside how many links a newsletter should have.

When to leave the shared domain alone

One ESP, modest volume, no complaints about the hostname on hover: do nothing. You would trade a warm host the vendor polices for a cold one you warm yourself, and pay in DNS surface for the privilege. The setup has sharper edges than the docs let on. Klaviyo cannot issue the certificate for your click subdomain unless your root CAA records allow 0 issue pki.goog, and it cannot verify the record at all if your DNS provider is proxying it. That pair of details costs people an afternoon.

Brand your click domain when you want your name on the hostname, or when your volume is high enough that you would rather own your link reputation outright than share it. Do it because you have decided the hover text is part of the brand, or because you want the blast radius to be yours alone. Do not do it expecting your inbox placement to move, and if placement is the actual problem, start with why your newsletter emails go to spam instead. The CNAME is a branding decision wearing a deliverability costume.

Frequently asked questions

Does click tracking hurt email deliverability?

Click tracking on its own does not hurt deliverability. What can hurt you is the reputation of the host your links point at, because domain blocklists like Spamhaus DBL, SURBL and URIBL evaluate hostnames found inside the message, not just the sending IP. A vendor redirect host used by thousands of senders is normally watched closely by that vendor, so the practical risk is low. The risk rises if you wrap tracked links in a second layer such as a public URL shortener.

What is a custom click tracking domain?

A custom click-tracking domain is a subdomain you own, such as links.example.com, pointed by CNAME at your ESP's redirect infrastructure. Your ESP still rewrites every link and still records every click, but the hostname a subscriber sees on hover is yours instead of the vendor's. Amazon SES calls it a custom redirect domain, SendGrid calls it link branding, Klaviyo calls it dedicated click tracking, and Brevo calls it a branded subdomain.

Why do newsletter links show a different domain?

Because the ESP rewrites the href before the message is sent. The link in the inbox points at a host the vendor runs, which records the click and redirects to your real destination. Common defaults are sendgrid.net, region-specific awstrack.me hosts on Amazon SES, trk.klaviyomail.com or trk.klclick.com on Klaviyo, and mandrillapp.com on Mailchimp Transactional.

Is a branded link domain worth it for a small newsletter?

Usually not, if you send from a single ESP at low volume and nobody has complained about the hostname on hover. You give up a heavily-trafficked vendor host that the vendor polices and start warming a cold subdomain that only you use, plus you take on the DNS and certificate surface. It becomes worth doing when the brand-visibility argument matters to you, or when you send enough that you want your link reputation isolated from other tenants.

Can I keep click tracking off entirely?

Yes. Most ESPs let you disable click tracking per domain, per configuration set, or per campaign, and your links then ship as written with no redirect host in front of them. The cost is that you lose click and click-to-open reporting, so you cannot measure which sections of an issue work. Server-side alternatives such as UTM parameters read by your own analytics keep attribution without a redirect.

Related reading