Skip to main content

Site aliases

Site aliases let one analytics site accept events from multiple allowed hostnames.

Example​

Canonical site:

example.com

Allowed aliases:

www.example.com
app.example.com
checkout.example.com

PureStats stores aliases separately and resolves incoming events through the canonical site ID.

Why aliases matter​

Without aliases, a tracker running on www.example.com would be rejected if the configured site is example.com. Aliases prevent accidental data loss while still blocking invalid or malicious hostnames.

When to use aliases​

Use aliases for:

  • www and non-www versions.
  • App and marketing subdomains.
  • Checkout domains.
  • Documentation or help center domains owned by the same product.

Do not use aliases for unrelated client sites. Create separate sites instead.

Cross-domain sessions​

Aliases allow events to be accepted. Cross-domain session stitching is a separate setting that helps connect a visitor journey across those allowed hostnames.

Verification​

After adding an alias, open a page on that hostname and check Site Health. The latest hit should show the alias hostname and accepted status.