Custom Domains

Some networks and browser extensions block requests to third-party analytics domains: corporate filters, DNS-level blockers, regional restrictions, privacy extensions. Served from your own subdomain, the script is a first-party request on your site and keeps working in those environments.

A custom domain is a subdomain you control, such as metrics.yoursite.com, pointed at the TRACIO edge. Once DNS and the certificate are confirmed, the script, its bundle and the signal requests are served from that subdomain. You do not need to run a proxy.

How Activation Works

1. You add the subdomain in the dashboard and create the A records it shows at your DNS provider.
2. TRACIO detects the records and issues a TLS certificate for the subdomain automatically.
3. The first visit to a page that loads the script from the subdomain with your public key activates the host.

The dashboard shows these three stages — the A records, the certificate and the first visit with your key — and re-checks them automatically. Check now forces a re-check.

Set Up a Custom Domain

1. Open Get Started and expand Install the SDK and send your first event. Its first item asks where the script loads from: choose Your own subdomain and enter it. The same wizard lives under Settings → Custom Hosts.
2. Add the A records shown in the dashboard at your DNS provider. If your domain is on Cloudflare, add them with the proxy turned off (grey cloud, DNS only): with the proxy on, Cloudflare replaces the addresses and requests do not reach TRACIO.
3. Wait until the DNS and Certificate stages are confirmed. Propagation and issuance take from a few minutes to a few hours.
4. Put the snippet on your pages. The first visit with your key activates the host.

If your site already tracks via the shared domain, switch the tag only after the DNS and Certificate stages are confirmed: until then the script does not load from the new subdomain.

Snippets

Script tag:

<script src="https://metrics.yoursite.com/s.js?k=PUBLIC_KEY" async></script>

npm packages: pass the subdomain as endpoint. The SDK loads the script from it and sends signals to it. When endpoint is set, the region option is ignored. Do not use scriptUrl for this: it replaces the whole script URL, including the public key.

import { Tracio } from "@tracio/sdk"

const tracio = Tracio.init({
  publicKey: "PUBLIC_KEY",
  endpoint: "https://metrics.yoursite.com",
})

The framework packages accept the same endpoint option — see the SDK pages.

Limits

• Use a subdomain you control, such as metrics.yoursite.com, that serves nothing else.
• On Cloudflare the records must be DNS only (grey cloud).
• A subdomain that is active in another workspace cannot be added.

Next Steps

• Quick Start — install the SDK and read your first result
• Troubleshooting — blocked requests and cookie issues