The Source Pixel enables tracking of users across multiple domains by sharing a cookie containing a unique identifier for each user. To ensure seamless tracking across different domains and subdomains, it is crucial to correctly configure your website domain during the onboarding process and implement the Source Pixel script on all relevant domains and subdomains.

For effective tracking across domains and subdomains, follow these guidelines:

When configuring your website domain, always select the highest-level domain you control. For instance, if your domains include source.app, auth.source.app, and t.auth.source.app, you should specify source.app as your website domain. This ensures that the cookie containing the user ID is accessible across all subdomains (e.g., auth.source.app and t.auth.source.app).

If you configure the website domain at a subdomain level (e.g., auth.source.app), the cookie will only be available for that specific subdomain and its subdomains (e.g., t.auth.source.app). This restricts tracking capabilities across other domains like source.app.

To ensure accurate user tracking, the Source Pixel script must be added to every domain and subdomain you wish to monitor. Follow these steps:

If your website operates on the following domains:

Set source.app as the primary domain during onboarding. This configuration allows the user ID cookie to be accessible across all these domains, enabling consistent user tracking regardless of where the user interacts with your site.