Custom Tracking Domains

Every stream's snippet is already unique per customer — the script path, element ids, and event name are all randomly derived per stream (see the Integration Guides overview). But by default, every customer's page source still points at the same cloakingx.com hostname. A reviewer only has to scan for that ONE domain to see that a page is running Cloaking X at all — a custom tracking domain replaces it with a hostname unique to your own account.

In your dashboard, go to Domains and add a subdomain you control — e.g. t.yoursite.com. We recommend a dedicated subdomain rather than your bare root domain, so this never interferes with anything else already running there.

We show you a one-time TXT record to add at your DNS provider, under a _cloakingx-challenge subdomain — the same pattern used by Let's Encrypt and other providers' own domain verification, so it never disturbs anything else already configured on your hostname. Click Check Verification once it's live — DNS changes can take a few minutes to propagate.

Once verified, we show you a CNAME record to add: your hostname pointing at cname.vercel-dns.com.

Open a stream's Integration tab and choose your verified domain from the Serving Domain selector, right above the platform tabs. Every snippet/plugin download for that stream then uses your domain instead of cloakingx.com. One domain can be reused across as many streams as you like, or you can add a separate domain per stream if you want them kept isolated from each other.