Multiple websites

One Analytics environment can measure up to ten active website origins, including its primary website. For example, you can see your marketing website and web application in combined reports, then filter by domain.

Combined reporting and continuing a visit between websites are separate capabilities. Cookieless collection works across the allowed websites without enabling visitor recognition or SiteOS Cookie.

Add your websites

1. Select the Project and environment, then open Analytics → Settings → Domains.
2. Add each exact origin, such as https://example.com and https://app.example.com. Scheme, hostname and port matter; wildcard domains are not supported.
3. Install the same environment's Analytics configuration on each website. Keep only one collector per page.
4. Visit each origin and confirm its accepted activity. Check the domain filter in reports.

The primary website is managed in Project settings. Adding another origin registers it in the Project catalog and enables its Analytics membership; it does not configure other SiteOS services automatically. Keep staging in its own environment.

Read combined reports

Leave the domain filter unset for the combined report, or select an origin to inspect its activity. Pages are distinguished by origin and path, so /pricing on one website is not silently treated as the same page on another.

A visit can contain activity on more than one website when continuity is enabled. Domain-level visit counts are therefore not always additive. Older data without recorded origins remains unknown rather than being assigned to a website after the fact.

Continue visits between websites

Enable Continue visits between websites only when you want a permitted journey to continue from one allowed origin to another. Both websites need compatible installations, active recognition and affirmative recognition permission.

Review the consent setup for each origin. A published Cookie configuration must cover the relevant hostnames; see Cookie regions and domains. If a website uses a different Cookie banner, use Choose another banner, select the exact Cookie Project/environment, review its published configuration and choose Use this banner. Selecting a banner does not publish it or enable consent sharing.

Separate banners retain independent choices unless an explicitly configured Cookie sharing setup applies. Cross-domain Analytics does not transfer consent, copy recognition cookies or move People profiles between websites. It does not merge earlier visits or create cross-day identity by itself.

With the required setup and permission, supported links and GET-form navigation can carry a short-lived visit handoff. Navigation does not wait for Analytics. A last accepted event proves collection; it does not prove a linked visit. Test a complete journey and inspect its result.

JavaScript redirects

For an application-controlled redirect, prepare the destination through the installed runtime and fall back to ordinary navigation:

const destination = "https://app.example.com/signup";
const url = await window.SiteOSAnalytics?.prepareNavigation?.(destination);
window.location.assign(url ?? destination);

Use a trusted destination chosen by your application. The helper cannot grant recognition permission or make an unconfigured destination eligible.

Remove a website

Removing an additional origin stops future collection and pending buffered delivery from it. Previously accepted data remains subject to the environment's retention settings. Change the primary website through Project settings.

Traffic-exclusion preferences are also origin-specific. When excluding your own browser, select the website you actually want to exclude and verify the preference there.