Domains

A domain in StatelessID is a registered hostname whose page views you want to count. You can register more than one domain under the same account. All registered domains share the same monthly quota. Each domain gets its own site key and its own board view.

Registering a domain

To start counting visits for a new domain, go to the Setup page from the sidebar. Enter the hostname exactly as it appears in the browser address bar when a visitor is on that site. Use the bare hostname without a path or a protocol: example.com, not https://example.com or example.com/blog.

StatelessID matches beacons to domains by comparing the Host header in the beacon request to the registered hostname. If you register example.com and the beacon arrives with a Host of www.example.com, the beacon is rejected as a domain mismatch. Register the exact form you use in production — with www if your site redirects to www, without if it uses the bare domain.

After registration, the Setup page shows you the script snippet and the site key for the new domain. Install the snippet on every page of that domain that you want to track. Visits to pages without the snippet are not counted.

Multiple domains and the domain selector

You can register multiple domains under one account. All domains share the same monthly visit quota. If you have two active domains and each gets 80,000 page views in a month, the combined 160,000 draws from your single monthly cap.

The domain selector in the sidebar lists all registered domains. Clicking a different domain reloads the board for that domain, preserving the date range you had selected. The boards for different domains are completely independent — the page groups, referrers, countries, and error classes on the board for domain A do not mix with those for domain B.

There is no summary view that combines all domains into one board. Each board is scoped to a single domain. If you need a combined view, use the CSV exports for each domain and merge the files externally.

The site key

Each domain has its own site key. The site key is a short alphanumeric string that is embedded in the script snippet for that domain. When a beacon arrives, the site key in the request identifies which domain's aggregates to update. The site key is not a secret — it appears in the HTML source of any page that loads the script — but it should only be used on pages for the domain it was generated for.

If you use the wrong site key on a page — for example, copy-pasting the snippet from domain A onto a page for domain B — the beacons from that page will count against domain A's board and quota, not domain B's. Always verify the site key in the snippet matches the domain you intend to track.

You can view the site key for any registered domain on its Settings page within the dashboard. If you lose the snippet, return to Setup or Settings to retrieve it.

Removing a domain

Domain removal is available through the domain Settings page. Removing a domain stops future beacons for that site key from being counted. Historical data for the domain remains in your account and is still visible on the board if you navigate to that domain in the selector — it is not deleted when the domain is removed.

If you remove a domain and then register the same hostname again, a new site key is generated. The old site key stops being accepted. You will need to update the snippet on your site to use the new key.

Removing a domain does not reduce your monthly quota or change your billing. Quota is set per account, not per domain. You can remove a domain at any time without affecting your billing cycle.

Subdomains

Subdomains are treated as separate domains. A beacon from blog.example.com and a beacon from example.com are attributed to different boards if blog.example.com and example.com are both registered. If only example.com is registered, beacons from blog.example.com are matched against example.com and will be accepted because the host ends with .example.com.

If you want to track a subdomain separately from the main domain, register it as its own domain entry and install the corresponding snippet on the subdomain. If you want to combine subdomain traffic with the main domain, do not register the subdomain separately — the main domain entry will catch it automatically.

Troubleshooting

If beacons from your site are being rejected as domain mismatches, open your browser developer tools Network tab on a page that has the script, find the beacon request, and check the Host header. Compare it to the hostname registered in your dashboard Settings. They must match exactly, including the presence or absence of www.

If you need to track a staging or development version of your site separately, register the staging hostname as a separate domain with its own site key. Use a distinct site key for staging so that test traffic does not mix with your production board.