Mixpanel Community Icon

Cross-Domain Tracking Strategies for Multi-Brand Setup | Mixpanel Community

Community Questions

Cross-Domain Tracking Strategies for Multi-Brand Setup

·Jun 09, 2025 07:59 AM·

Guidance needed on cross-domain tracking and multi-brand setup Hi everyone, I’d appreciate your help with a setup challenge we’re facing. Our company operates several brands, each with its own website (e.g., alpha.com, bravo.io, etc.). Some features—like our website builder—are shared across multiple brands and embedded within their respective sites. We also have scenarios where a user’s journey within a single brand can temporarily cross into a different domain. Mixpanel identifies users via domain-based cookies and device IDs, which leads to two challenges: 1. Single-brand journey across multiple domains Here’s a simplified user flow: Page visit on alpha.com >Page visit on alpha.com/page2 >Page visit on alpha.com/page3 >Page visit on bravo.io/page2 All of this is a continuous journey from the user’s perspective within alpha.com and the user is identified under alpha.com, but because of the domain switch, I assume Mixpanel treats it as a separate user or session. What would be the recommended way to track this as a unified journey? 2. Cross-brand feature analysis We have shared products, like our website builder, that are embedded into multiple brand domains. Ideally, the website builder team would like to analyze usage across all brands in one Mixpanel project. We can assign a global user ID across brands, but we’re unsure whether this would lead to identity issues and multiple other. The clean approach would be keeping them separated and analysing each feature in the context of the website they're embedded, but I can understand how usefule it would be to analyse a let's say a funnel conversion for the feature and then break it down by a different domain to identify differences Should we send all events into a single project or keep them separated per brand? What setup would you recommend for a clean, scalable solution? Is there a concept of Portfolio (like ion Amplitude) ? Thanks in advance for your guidance! Best, Luka

Andrew S.
·
·
We have a couple of JS plugins that we deploy on different retailer websites. We have each of those plugins writing to a single Mixpanel project. We capture the URLs of events, which (using custom properties to clean the URLs to just the base domain) gives us the "where" something happens. We also track the "js_source" which tells us which of the plugins the event was coming from. These let us track activities across the plugins. We wrote some code for within our plugins to check if one, two or three of the plugins are installed, and we prioritized them in that code, so that only one of the plugins at any installation is firing the page_view events (otherwise we'd have 3x the page_view events coming in). Not sure if that gives you any ideas to consider for your situation but it certainly works for ours.
Luka O.
·
·
Thanks, Andrew — super helpful to hear how you’ve handled it. The part that still trips me up a bit is user identification across domains and brands. In our case, a single user might interact with multiple domains (e.g., during onboarding) and also belong to different brands, though they share the same top-level user ID. I’m trying to figure out how best to stitch that together in Mixpanel so the journey feels coherent in analysis — not split or misattributed. We agreed to run a POC where we send events to different mixpanel projects and keep users separate although some of them might have accounts in domain1.com and domain2.com 🤞
Tim V.
·
·
Luka O. curious to hear if you managed to get anywhere with this - I'm hoping to achieve something similar.
Andrew S.
·
·
And Luka O. sorry I did not see your response last month and Tim V. maybe this comment is applicable to you as well. We have one situation where we have plugins that get installed on multiple merchant sites. And in some cases, up to 3 different plugins on any given site. So for every event, I have a an "implementation_domain" property that I pass. I also have a "plugin" property that I pass. This lets me aggregate or segregate results by domain (same site) or by plugin (across sites) or by domain and plugin (same site, just specific plugins). We are not do user identification on these bc the users are not necessarily logged in, but because of cookies and distinct IDs, I can see (generally) users who did stuff across the sites. Tracking blockers and expired cookies do not give me 100% accurate data but directionally it works for what I want. If they were logging in and I had that data (user_id) then it could certainly be stronger data.