Subdomain

A subdomain like blog.example.com is a separate origin from example.com. Register it as its own site and paste the correct key so its page views stay distinct.

Why subdomains need their own registration

StatelessID groups page views by origin. An origin is the combination of protocol, host, and port — https://blog.example.com and https://example.com are different origins even though they share the same registrar account and DNS zone.

When a visitor loads a page on your blog subdomain, the beacon carries the subdomain origin. If your dashboard only has example.com registered, the beacon lands on an unmatched origin and is not counted. You need a site registration for each subdomain you want to measure.

The upside is that you get clean, separated data. Your main site's page views do not mix with your blog, your docs, your status page, or any other subdomain. You can look at each one independently and see how they trend over time.

Registering a subdomain site

Log in to your StatelessID dashboard and add a new site. Use the full subdomain as the site identifier — for example blog.example.com. The dashboard gives you a new snippet with a unique data-k value for that subdomain.

Copy that snippet and paste it into the template or layout file for the subdomain. If the blog runs WordPress, paste it in the blog's theme footer. If it is a static site, paste it in the base layout. The principle is the same as any other install: one snippet in every page template.

Save and deploy. Load a page on the subdomain in your browser, then check the subdomain's entry in your dashboard. You should see the page view appear within a minute.

Measuring multiple subdomains efficiently

If you run several subdomains — blog, docs, help, status — register each one and note its key. A simple naming convention keeps them organized: use the full hostname as the site name so you recognize them at a glance in the dashboard dropdown.

Some CMS setups let you inject a global header snippet across all subdomains from one admin panel. If yours does that, be careful: a single key spread across multiple subdomains merges their data. That is only correct if you want a combined view. For separated views, use a per-subdomain key.

If a subdomain is a staging or development environment, you probably do not want it counted in production data. Either do not install the snippet on staging, or register it with a staging-specific site entry and keep that data separate.

Wildcard subdomains and user-generated subdomains

Some platforms give users their own subdomain — user1.example.com, user2.example.com. StatelessID does not support wildcard measurements across user-generated subdomains in a single dashboard view. Each distinct subdomain would need its own registration, which is not practical at scale.

For platforms where every user gets a subdomain, the practical approach is to measure from the operator's perspective: install the snippet on the shared template that renders all user subdomains, register a single site that captures aggregate traffic across all of them, and use the Pages column in your dashboard to distinguish which paths are popular.

If precise per-user subdomain breakdowns matter, open a help request through your dashboard and describe your setup. There may be a configuration that works for your specific case.

Troubleshooting

I added the snippet to my subdomain but the dashboard shows no data for it. Confirm you created a separate site registration for the subdomain and copied that site's specific key — not the key from your main domain — into the subdomain's template.

Page views from my subdomain are showing up under my main domain. The snippet on the subdomain is using the main domain's key. Open the subdomain template, find the data-k attribute, and replace its value with the key assigned to the subdomain site registration.

My subdomain is behind a reverse proxy that rewrites the host header. The beacon reads the actual URL the browser loaded, not the upstream host. As long as the visitor's browser shows blog.example.com in the address bar, the beacon will carry that origin correctly.