Subdomains and separate websites

Decide whether example.com, app.example.com and docs.example.com should appear in one website report or separate reports before installing the tracker.

One report

Install the same website’s generated snippet on every host you want to include. Keep its data-site token and data-api value unchanged. Each host sends its own pathname and hostname to that website.

Page reports group pathnames, so /pricing on two hosts can contribute to the same page row. Overview → Sources → Hostnames shows traffic by reported hostname, but does not filter the page table by host. Choose separate websites if you need a separate page report for each host.

Separate reports

Create a website for each host from Your sites → Add website, then install that website’s own snippet on that host. Check the token on the published page: copying the main website’s snippet would send activity into the main website’s report instead.

Use Roll-up for the available combined account view. Separate website reports do not create cross-domain visitor journeys.

Visitor and session scope

With the website domain set to example.com, its subdomains share the same daily server-derived identity when they use the same token and IP/user-agent combination. Unrelated domains remain separately scoped. The identity changes at midnight UTC; separate website tokens never share identity. See technical privacy for the counting limits and legacy-data transition.

Cross-domain visitors

Save the hostnames under Settings → Installation → Dashboard or add data-domains="a.example,b.example" to the Explicit snippet on both sides. Use the same data-site token; a listed host also matches its subdomains. Clicked HTTP(S) links to another listed host carry _seean_v=<handoff token>. An opted-in landing tracker adopts it, stores the same-day token in sessionStorage and removes the URL parameter without counting another pageview. The server hashes the token by website and UTC day; it never stores the raw token in events.

Minimal configuration has up to two seconds to load. Failed or late configuration leaves handoff off; an incoming parameter alone cannot enable it. GPC, DNT and browser opt-out suppress handoff as well as collection. Typed URLs and bookmarks do not carry the token; blocked sessionStorage limits continuity to the current document. Links to the current hostname and non-HTTP(S) links are unchanged. The collector may continue the same session within 30 minutes; each document still captures its own landing path and referrer.

Referrals from another subdomain can appear as sources. The collector removes a referrer matching the configured website domain, with the www. prefix normalized; this is not a rule that removes every related subdomain referral.

Hostname exclusions and collection access

The website domain setting is not a collection allowlist. The public token routes incoming activity to a website; installing it elsewhere can send activity there too. Do not use it as a secret or an authorization credential.

Use Settings → Exclusions to discard activity from a known unwanted hostname, such as a preview host. A hostname exclusion is a collection rule, not an identity-sharing feature. Read the exact matching and retention behavior in Exclusions.

Verify each host

1. Publish the snippet once in the shared document on each intended host.
2. Open a page on each host, then visit a second pathname and reload. Check the token and hostname in the browser’s collection request.
3. Open the intended website’s activity log and verify its paths and event counts in the current period.
4. Check Settings → Installation → Setup health, while remembering that recent data from one host does not prove every host is installed correctly.

If a host is missing, check its published snippet, consent state, exclusions and browser blocking using installation troubleshooting. Installing a snippet on the main domain does not install it on independently hosted subdomains.

Something unclear? Contact support.