XTRACKER

Custom landing domains via CNAME

Serve your XTRACKER landings on your own domain in two steps: point a CNAME at the tracker origin and add the domain in the dashboard. Cloudflare handles TLS.

By default your landings live on the tracker domain. To run them on your own domain — for branding or ad-platform trust — you point a CNAME at the origin and register the domain. No server config, no certificates to manage.

Two steps

1. Point a CNAME

In your DNS provider, add a record for the hostname you want to use:

track.yourbrand.com   CNAME   origin.xtracker.cc

If you use Cloudflare in front (recommended), keep it proxied (orange) and on Flexible SSL — Cloudflare terminates HTTPS for your visitors and talks HTTP to the origin. You manage your own certificate; the tracker origin just accepts the host.

2. Register the domain

Add track.yourbrand.com in the dashboard under Domains for your space. The tracker resolves an incoming request's Host → domain → space → link, so your slugs work on the new domain immediately.

How routing works

Every landing request is matched by host. Because slugs are unique per space, the domain is what tells the tracker which space a request belongs to. That's why the domain must be registered — an unknown host has no space to resolve to and returns not found.

TLS

You don't need to do anything on the tracker for TLS. With Cloudflare Flexible the origin only ever speaks HTTP on port 80; Cloudflare presents the certificate to your visitors. If you front the domain with something else, just make sure it can reach the origin over HTTP.

Verifying

Once DNS propagates, open https://track.yourbrand.com/<your-slug> — you should see the same landing you get on the tracker domain. Clicks minted there are attributed to the same space and link.

Next