Serving the tracker from your own domain
Why the default cdn.truevisit.ai install can get blocked, the one CNAME record that fixes it, and what changes once it verifies.
Last updated
Why serve the tracker from your own domain
The default install loads the tracker from cdn.truevisit.ai and posts events to api.truevisit.ai. Both are third-party requests from your visitor's point of view, and a filter list such as EasyList blocks a good share of third-party analytics domains by name, ours included on some lists. A blocked visitor is not a bot, but they are invisible either way, which is its own kind of blind spot for a product built to make your traffic trustworthy.
A custom domain removes the distinction. Once your own subdomain, for example analytics.yoursite.com, is verified, the tracker and every event it sends both come from a domain the visitor already trusts, which a domain-based blocklist has no reason to block.
Set it up
- Open your site settings and find the Custom domain card.
- Enter a subdomain you control, for example analytics.yoursite.com. It needs to be a subdomain, not your bare root domain, because the DNS record below is a CNAME and a CNAME cannot be set at a root domain.
- Add the CNAME record the app shows you at your DNS provider. It is the only record this needs.
- Click Check status. Verification is usually done within a few minutes of the record going live, though your DNS provider's own propagation time can add to that.
- Once it verifies, swap the install snippet on your site for the one the app now shows on that same card. It no longer needs a site id attribute, because your domain already identifies the site.
<script defer src="https://analytics.yoursite.com/tracker.js"></script>What actually changes
Nothing about what is collected, how it is classified, or how it is billed changes. The only difference is which domain your visitor's browser talks to. Ownership of your domain is proven by the CNAME record itself, and TLS for it is issued and renewed automatically once verified, nothing further to manage on your side.
This does not point DNS at our server's real address. The CNAME target is a shared, indirect address, so your visitor's browser never learns our origin's IP, which changes nothing about the security model described on the privacy and data handling page.
Limits and troubleshooting
| Detail | Value |
|---|---|
| Domains per site | 1 |
| Must be | A subdomain you control, not your bare root domain |
| DNS record needed | One CNAME, shown in the app for your exact domain |
| Typical verification time | A few minutes after the record is live, longer if your DNS provider's TTL is high |
| Removing it | Reverts your install to the default cdn.truevisit.ai snippet immediately |
A domain already in use by another TrueVisit site cannot be added again, whether or not you own it: each verified domain identifies exactly one site. If Check status keeps reporting the domain as not yet verified after the CNAME has clearly propagated, the most common cause is a typo in the record, or a proxying DNS setting at your provider that changes the record type before it reaches us.