Custom domains

Run your tracker and your public dashboard on a subdomain of your own site, like stats.example.com. The tag then loads from your domain and reports back to it.

Set it up

Open your site’s dashboard. Under Custom domain in the sidebar, type the subdomain, like stats for stats.example.com, and press Add.
Add the record it shows where you manage your domain: a CNAME from stats.example.com to proxy.simplytics.dev.
Wait for Active. It usually takes a few minutes once the record is live, while the certificate is issued.
Optional: swap your snippet for the one it shows. The one already on your site keeps counting; this one loads from your own domain, where ad blockers are less likely to stop it.

<script async src="https://stats.example.com/track.js" data-key="YOUR_SITE_KEY"></script>

If your dashboard is Public, it is also at https://stats.example.com/, under your own name and logo.

You can also do this with the API or the MCP server.

What it serves

Only the tracker, its beacons and, when the site is Public, its public dashboard. Sign-in, your account and everything else stay on simplytics.dev. Your subdomain sets no cookies.

Rules

One per site, on that site’s own domain: a subdomain, not the domain itself or its www.
It needs the same check as making your dashboard public: our tag on your homepage, or a DNS record. It runs when you press Add.
One that is not Active within 7 days is removed, so nobody can hold a name they don’t control.
When your subscription ends, your custom domains are released. Add one back any time: if its CNAME is still there, no new DNS step is needed.
Stopped using it? Remove the CNAME too.

Your logo

Upload a PNG, JPEG or WebP, up to 100 KB, under Logo in the same sidebar. It replaces ours at the top of your public dashboard, with a small “Powered by Simplytics” link at the end.

Still waiting, or an error?

A typo in the record. The name must be exactly your subdomain and the target proxy.simplytics.dev.
A CAA record. If your domain has one that leaves out the certificate authority, no certificate can be issued. The sidebar shows the error in Cloudflare’s words.
A Content-Security-Policy. If your site sends one, add https://stats.example.com to script-src and connect-src.