Thena

Hello YJ Kim, Zach here with Mixpanel Support 👋 thanks for writing into the Community 🙂 I understand your concern about the delay in ID merge and its impact on your real-time onboarding funnel analysis. This delay is indeed a known behavior in Mixpanel due to the process of merging pre- and post-auth events. It can take up to 24 hours for the identities to be merged and for the funnels to show accurate results. This is because there is an ID Merge delay for the anonymous and identified user activity to be linked together across Mixpanel. Unfortunately, there isn't a way to speed up this process within Mixpanel. The delay is inherent to the process of merging pre-auth and post-auth events, which allows Mixpanel to connect these events and see them as a single user performing those events. Because of this delay, using Funnels for same day / real-time analysis is generally not recommended. The best practice would be to look at least a day back (24 hours) in your Funnels Date Range to allow the merges to settle. This would ensure that you're looking at complete data. For debugging purposes, the Activity Feed view of a single user is updated in near real-time (less than 1 minute delay), so you can at least verify individual user journeys there. Thanks for your understanding! Hope this helps at least confirm what you're seeing. Zach Mixpanel | Support Engineer

Hi Steven! Julianne from Mixpanel Support here. Have you already seen the Group Analytics Implementation doc? It walks through how to implement group analytics in Mixpanel, including example code snippets for various SDKs. You can also test out the functionality in our B2B demo dataset. For example, this Funnel is based on 'Company' conversions rather than user. Can you share more about the issue that you're having with it not consistently working? If you're open to sharing feedback about what's confusing in the docs, I'd love to flag it internally!

Hi Rohit- Julianne from Mixpanel Support here. Happy to help with Heatmaps! The Heatmaps doc goes over setup and usage and is a great place to start. What specific question do you have about Heatmaps? Are you looking to set them up for the first time, or troubleshooting something specific?

Hi Emily- Julianne from Mixpanel Support here! I can replicate the behavior you're seeing with the Firefox browser on Android. This seems like a bug on our end, and I've gone ahead and reported it to the engineering team. Thank you for flagging this. In terms of the browser detection limitations, the JavaScript SDK relies on the User Agent to detect and classify browsers. Chrome-based browsers often don’t expose their actual browser branding in the standard User Agent string. If your use case requires more granular details about the browser brand, you can track this in your implementation by using navigator.userAgentData and setting it as a super property. 

Hi Darin- Julianne from Mixpanel Support here. I'm sorry that you're having trouble setting up the BigQuery data connector. Warehouse Connectors is a free add-on currently available on the Growth or Enterprise plans. The lack of Project Settings > Warehouse Connections entry indicates that your organization is likely on a Free plan, which isn't expected to have the connector as an option. Can you confirm which plan you are on? You can see this in the Organization Settings > Plan Details & Billing. If you are on a Free plan, the Growth plan includes up to 1 million events for free, so it may be a good option if you are looking to test the connection. 

Hi Lothain- Julianne from Mixpanel Support here! It is expected that custom events will be accessible in the drop-down menu to be used for analysis. The custom events are indicated by the asterisk on the event icon. If you don't want to use the actual tracked event for analysis, you can hide it in Lexicon to remove it from the menu. It's not currently possible to change this behavior, but I recommend submitting your use case and request for this behavior via the 'Submit Feedback' form (under the ? menu). This will flag it to the Product team, who use the logged gaps to develop improvements for the product.

Hey Julianne, We are good. ThanksOn Jan 25, 2026 at 3:01 AM +0500, Support support@mixpanel.com , wrote: To unsubscribe from this group and stop receiving emails from it, send an email to .

Hi Udit- Julianne from Mixpanel Support here. Mixpanel automatically records a property called "Session Duration (Seconds)" with every "Session Start" and "Session End" event. You can perform aggregate calculations per user on this "Session Duration" property to find the average session time per user. That said, the virtual session events are calculated based on event data being sent to your project. This means it would be unexpected for there just to be "Session Start" and "Session End" events. In order to calculate sessions, you would need to send event data. The Sessions doc has more information on how the virtual events are calculated and the properties available on them. 

Hi Sarvin- Julianne from Mixpanel Support here! Yes, the JavaScript SDK has configurable batching behavior. By default, it batches up to 50 events and flushes every 10 seconds, but you can adjust these settings during initialization by configuring the batch_size and  batch_flush_interval_ms. You can see the entire default config here. 

It would depend on when a user tracked the events. As an example, let's say a user tracked 'level_start' on Jan 3 and Jan 8. For the 'Uniques' count, they would be counted on the 3rd and once on the 8th. For 'Uniques- Last Segment', they would only be counted on the 8th (their last segment tracked).