Using Your Own Tracking Domain
Why campaign links should use your own domain instead of the platform hostname, and the two steps needed to set it up.
Updated September 2026
By default, MailWizz rewrites every link in your campaigns, and the open tracking pixel, to point at your server’s platform hostname. A tracking domain replaces that hostname with one of your own, so recipients see links on your domain instead.
Why this matters
Mailbox providers evaluate the domains that appear inside a message, not just the domain it was sent from. Two things work against you with the default setup:
- The From domain and the link domain do not match. Your message says it is from
yourdomain.com, but every link points somewhere else. That mismatch is a signal providers weigh when deciding placement. - The platform hostname has no reputation of its own as far as your recipients’ providers are concerned, and it is not a domain your recipients recognise.
Recipients also see the real destination when they hover over a link. A link on your own domain looks like what it is. A link on an unfamiliar hostname looks like something to be cautious about, which costs you clicks even when the message reaches the inbox.
What you need
A subdomain of your sending domain, dedicated to tracking. The convention is track.yourdomain.com, but any subdomain works.
Use a subdomain of the same domain you send from. A tracking domain on an unrelated domain reintroduces the mismatch you are trying to remove.
Step 1: create the DNS record
Point the subdomain at your MailWizz server. Either record type works.
A CNAME to your server’s platform hostname:
Type: CNAME
Name: track.yourdomain.com.
Value: mailwizz.yourserver.protectedserver.net.
TTL: 3600
Or an A record to your server’s IP address:
Type: A
Name: track.yourdomain.com.
Value: 203.0.113.10
TTL: 3600
Your platform hostname and server IP are both in your welcome email, and in the client area under your service.
Do not enable a proxy or CDN on this record. If your DNS provider offers proxying, such as Cloudflare’s orange cloud, leave it off. The certificate for this hostname is issued on the server, and proxying prevents that from completing.
Step 2: open a ticket so we can complete the server side
Once the DNS record resolves, open a support ticket telling us the tracking hostname you created.
We add it to your server’s web configuration and issue an HTTPS certificate for it. This takes a few minutes and requires no downtime. We will confirm on the ticket when it is ready.
This step is on our side because the certificate is issued against your domain on the server itself. It cannot be done from inside the MailWizz interface.
Step 3: add the tracking domain in MailWizz
After we confirm:
- In your customer area, go to Domains, then Tracking domains
- Choose Create new
- Enter
track.yourdomain.com - Save, then Verify
Once verified, new campaigns use it automatically for link tracking and open tracking.
What changes, and what does not
Campaigns created after the tracking domain is active will rewrite their links through it. Campaigns already sent keep the links they were sent with, because those links live in messages already in recipients’ mailboxes. Never remove a tracking domain that older campaigns used, or the links in those messages stop working.
Your unsubscribe links also move to the tracking domain, which is a further improvement. An unsubscribe link on your own domain is more likely to be trusted and used, and a recipient who unsubscribes is far better for your reputation than one who reports the message as spam.
Verifying it worked
Send yourself a campaign test and hover over any link. The status bar should show track.yourdomain.com. If it still shows the platform hostname, the campaign was created before the tracking domain was verified, so create a fresh one and test again.