Tracking Domain

A tracking domain is the address every tracking link and pixel in your program is served from. It is where clicks land, where the click ID cookie is set, and where conversion pixels and postbacks fire. The single most important decision about it is ownership: a tracking domain you control — such as track.yourbrand.com — makes the attribution cookie first-party, and first-party is what survives today's browsers.

Why your own domain matters

Three reasons, in order of impact:

1. Browser privacy. Safari's ITP and similar protections restrict cookies set by third-party domains. When your tracking host matches your brand, the attribution cookie is first-party and far more likely to survive between click and conversion.
2. Trust and deliverability. A track.yourbrand.com link looks legitimate to users, email filters, and ad platforms — a shared or unknown tracking host looks like spam.
3. Continuity. Your links live on a domain you own, not on infrastructure you could lose access to.

A worked example

You add track.yourbrand.com and point a few DNS records at the platform. Within minutes it verifies, gets an HTTPS certificate, and goes live. Now every link you generate — https://track.yourbrand.com/c?o=12&aff=34 — runs on your brand. A visitor clicks, the click ID cookie is set on track.yourbrand.com, and because that aligns with your yourbrand.com site, the cookie is treated as first-party at conversion time and honored. Swap in a shared subdomain instead and that same cookie would often be withheld — the difference between a conversion that attributes and one that silently doesn't.

Subdomain vs root domain

A subdomain (track.yourbrand.com) is the common choice and needs a few CNAME records. A root domain (yourbrandtracking.com) works too but is set up by delegating nameservers, so use a domain dedicated to tracking rather than your main site's domain.

How this works in LimeliJourney

In LimeliJourney a tracking domain is required before you can generate links or pixels — it is the foundation of tracking. Add it under Settings → Domains, add the DNS records shown, and it verifies, issues HTTPS, and activates on its own, usually within minutes; you never come back for a second set of records. Your first active domain becomes your primary, the default for new links. Keep the HTTPS-certificate record in place permanently so the certificate auto-renews, and use Swap to migrate to a new domain with no downtime. LimeliChat can check your domain's status and tell you exactly which record isn't matching.