Does Mixpanel Track Unique IDs for Multiple Tabs in the Same Browser?
Does Mixpanel track different distinct id for same browser but different tabs
Does Mixpanel track different distinct id for same browser but different tabs
Hi Nainik M., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> đź‘‹
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
Based on the knowledge sources provided, Mixpanel does not track different distinct IDs for the same browser but different tabs. The distinct ID is typically associated with the user or device, not individual browser tabs.According to the Identity Management Overview, Mixpanel uses a Distinct ID to uniquely identify users across devices and sessions. For web applications, the JavaScript SDK automatically generates a Distinct ID for a user when they access the product through a website.The Distinct ID is stored in the browser's local storage or cookies, which are shared across tabs of the same browser. This means that if a user opens multiple tabs in the same browser, they will have the same Distinct ID across those tabs.It's important to note that if a user accesses the product from different devices or browsers, they may initially have different Distinct IDs. However, these can be merged into a single identity cluster when the user is identified (e.g., upon login) using Mixpanel's identity management features.If you need more specific information about how Mixpanel handles browser tabs, it's not explicitly covered in the provided knowledge sources.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
How does this works Mixpanel's identity management features
Let me check the knowledge base for you again. One moment! đź“š
Mixpanel's identity management features work by allowing you to connect different identifiers for a user, ensuring that their activity across different devices or sessions is attributed to a single user profile. Let me explain how this works based on the information from the knowledge sources: 1. Anonymous and Identified States: When a user first interacts with your product, they are typically in an anonymous state. Mixpanel assigns them a random $device_id (also called an Anonymous ID). Once the user is identified (e.g., after logging in), you can assign them a known $user_id. 2. ID Merge: Mixpanel offers two versions of ID Merge: a) Original ID Merge API: As described in the [Identifying Users (Original) documentation](https://docs.mixpanel.com/docs/tracking-methods/id-management/identifying-users-original#mechanism), this system uses special events like $identify, $create_alias, and $merge to link various user identifiers. b) Simplified ID Merge API: According to the [Identifying Users (Simplified) documentation](https://docs.mixpanel.com/docs/tracking-methods/id-management/identifying-users-simplified#mechanism), this newer system only requires including the reserved event properties $device_id and $user_id on the events for identity merging to take place. 3. Merging Process: When you identify a user, Mixpanel creates an identity cluster that links the anonymous ID ($device_id) with the known user ID ($user_id). This allows Mixpanel to attribute all of the user's activities, both before and after identification, to the same user profile. 4. Cross-Device Tracking: If a user accesses your product from multiple devices, each device will initially have its own $device_id. When the user logs in on each device, you can call the identify method with their $user_id, which will merge all these identities into a single user profile. 5. Retroactive Merging: Mixpanel can retroactively merge user data. This means that even if a user has multiple anonymous sessions across different devices before logging in, all that data can be connected to their identified user profile once they do log in. 6. Implementation: For client-side implementations (web/mobile SDKs), you typically call the identify() method when a user logs in and reset() when they log out. For server-side implementations, you need to manage the IDs yourself and include the appropriate $device_id and $user_id properties with your events. It's worth noting that the specific implementation details may vary depending on which ID Merge system your project is using (Original or Simplified). You can check which system you're using in your [project settings](https://mixpanel.com/settings/project/id-management).
For a more detailed understanding of how these systems work, including example user flows, you can refer to the Identifying Users (Original) or Identifying Users (Simplified) documentation, depending on which system you're using.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Let me check the knowledge base for you again. One moment! đź“š
To answer your question about what happens in the case of subdomains on a platform with Mixpanel, I'll refer to the relevant information from the knowledge sources.According to the Mixpanel Cookie documentation, Mixpanel cookies work across subdomains by default. This means that Mixpanel's Distinct ID and Super Properties are consistent across your subdomains. However, there's an important consideration for hosted subdomains: 1. For hosted subdomains (e.g., yourdomain.hostapp.com) that don't allow cross-subdomain cookies, you have two options: a) Disable cross-subdomain cookies: You can set the cross_subdomain_cookie configuration option to false. Here's an example of how to do this:
'cross_subdomain_cookie': false // prevent cookie persistence across subdomains
});
```LBKSLBKS b) Use a CNAME: Alternatively, you can use a CNAME to change from `[yourdomain.hostapp.com](http://yourdomain.hostapp.com)` to `[yourdomain.com](http://yourdomain.com)`.LBKS2. If you're using subdomains on your own domain (e.g., [app.yourdomain.com](http://app.yourdomain.com), [blog.yourdomain.com](http://blog.yourdomain.com)), the default behavior should work, keeping the Distinct ID and Super Properties consistent across these subdomains.LBKSIt's important to note that if you disable cross-subdomain cookies, each subdomain will be treated as a separate domain in terms of user tracking. This means a user visiting different subdomains might be counted as separate users unless you implement additional identity management strategies.LBKSFor the most accurate tracking across subdomains, it's recommended to use Mixpanel's identity management features, such as the `identify()` method, to ensure users are correctly identified across different subdomains and sessions.LBKSIf you need more specific information about handling subdomains in your particular setup, you may want to consult with Mixpanel's support team, as the provided knowledge sources don't cover all possible scenarios.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
How to contact Mixpanel's support team
Let me check the knowledge base for you again. One moment! đź“š
Based on the knowledge sources provided, there are several ways to contact Mixpanel's support team: 1. Through the Mixpanel interface: If you're logged into Mixpanel, you can click on "Contact Support" in the Help Menu. This is mentioned in the Response Times documentation.2. Via the support form: If you're not logged in, you can access the support form by going to mixpanel.com/get-support. This link is referenced in multiple documents.3. Email: For specific inquiries, you can email the Customer Success team at <success@​mixpanel.com> , as mentioned in the Migration documentation.4. Community support: Mixpanel also has an active Mixpanel Community Slack where you can ask other experienced Mixpanel users for help. However, this is not direct contact with the Mixpanel support team.The response time for your inquiry will depend on your Mixpanel plan and the priority of your issue. For detailed information about support offerings and response times, you can refer to the Response Times documentation.Remember that for any system-wide issues, you can check the Mixpanel Status Page for updates or subscribe to receive notifications about future status updates.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.