Hello kapa.ai. Some of our app registered users are not showing up in mixpanel (not even after a delay). I haven't found any patterns, or data points, that explains why most users are in mixpanel but some are not.
Please stand by Mattias N. as I search the knowledge base. I normally take about 15 seconds or so. đź‘‹
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
There are several reasons why some of your registered users might not be showing up in Mixpanel. Based on the knowledge sources, here are the most common causes and troubleshooting steps:
Ad Blockers and Do Not Track Settings
Client-side tracking can be unreliable, potentially causing you to lose events for 30-50% of your users. Users with ad blockers or Do Not Track (DNT) browser settings enabled won't send data to Mixpanel.Solution: Consider sending events through a proxy or implementing server-side tracking, which is more reliable and easier to maintain than web/mobile tracking.
Hidden Events and Properties
Events might be hidden in Lexicon by Project Owner and Admin users. Additionally, Mixpanel's report dropdown menus hide events that haven't been fired within the last 30 days.Solution: Check Lexicon to see if relevant events are hidden, and verify if the events you're looking for are inactive.
Data Residency Configuration
If your project has EU or India data residency but your SDK is configured with the wrong API host, events will be rejected.Solution: Ensure you're using the correct API host that matches your project's data residency:
- US: [api.mixpanel.com](http://api.mixpanel.com)
(default)
- EU: [api-eu.mixpanel.com](http://api-eu.mixpanel.com)
- India: [api-in.mixpanel.com](http://api-in.mixpanel.com)
This is especially important for India data residency, where events will be rejected if sent to the wrong endpoint.
Debugging Steps
1. Enable Debug Mode in your SDK to confirm requests are being sent to Mixpanel:
- JavaScript Debug Mode
- iOS Debugging and Logging
- Android Debugging and Logging2. Check Browser Console (for web implementations):
- Enable debug mode on your website
- Open your browser's developer console (Network > Fetch/XHR tab)
- Perform actions that trigger Mixpanel tracking
- Look for requests to the Mixpanel API and check for error messages3. Verify Project Token:
- Ensure the "token" in the data payload matches the token in your Project Settings4. Check for Opt-Out Settings:
- Users might have been opted out of tracking using the opt_out_tracking()
method
- If your SDK is configured with opt_out_tracking_by_default: true
, users won't be tracked unless they explicitly opt inIf you're still unable to identify the pattern after these steps, I recommend implementing server-side tracking as a more reliable solution to compare with your current implementation and identify discrepancies.
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.
kapa.ai Is there another place then "Users" where I can see all users, or is there a log or somewhere else where I could see some errors why I a user wasn't registered. Which data is the minimum for a user to be registered (to have a registered distinct id).
Let me check the knowledge base for you again. One moment! 📚
Based on the knowledge sources, here are the places where you can see users in Mixpanel and troubleshoot registration issues:
Viewing Users in Mixpanel
The primary place to view users is the Users page, which allows you to: - View all users who have completed any event (by selecting "All Users") - View users with profile properties (by selecting "User Profiles") - Explore individual user histories - Create cohorts based on user behavior or propertiesUsers: Explore your user base in Mixpanel explains that you can toggle between "User Profiles" and "All Users" views. The "All Users" view will show all users who have completed any event, even if they don't have profile properties set.
Troubleshooting Missing Users
For debugging why some users aren't being registered, you can use: 1. Events report - The Events report shows events and their properties as they flow into Mixpanel, which can help identify if user events are being tracked at all.2. User Profile Activity Feed - This report contains all information about specific users and is particularly useful for identity management issues: - You can examine the Identity Cluster to see all Distinct IDs linked to a user - Search through all events with the most recent one listed on top - This is the only report with query-time identity management mergingAs noted in Check Your Implementation, "The User Profile Activity Feed report is the only report with query-time identity management merging. All other reports in Mixpanel may still show separate Distinct IDs while merging is still being processed."3. Debug Mode - Enable Debug Mode in Mixpanel's Client-Side SDKs to log any Mixpanel calls to the browser console or development platforms.
Minimum Data for User Registration
For a user to be registered in Mixpanel, the minimum requirement is a distinct_id. This is the fundamental identifier Mixpanel uses to track unique users.For client-side implementations:
- Mixpanel automatically generates a $device_id
for anonymous users
- When you call .identify(<user_id> )
, Mixpanel creates an identity mapping between the $device_id
and your $user_id
For server-side implementations:
- You need to manually manage the distinct_id
- It's recommended to set both $device_id
and $user_id
properties rather than setting distinct_id directlyIf you're using the Simplified ID Merge API, the distinct_id will be set to:
- The $device_id
value if only $device_id
is present
- The $user_id
value if $user_id
is presentIdentity merging can take up to 24 hours to propagate throughout the system, though the Activity Feed view updates in real-time (less than 1 minute delay).If you're still having issues, I recommend checking if your implementation correctly handles identity management according to the guidelines in Identifying Users (Simplified).
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.
kapa.ai How do I toggle between "User Profiles" and "All Users" views. The "All Users" view will show all users who have completed any event, even if they don't have profile properties set.
Let me check the knowledge base for you again. One moment! 📚
Based on the knowledge sources, here's how to toggle between "User Profiles" and "All Users" views in Mixpanel: On the Users page in Mixpanel, you can select between "User Profiles" or "All Users" views. This toggle allows you to switch between seeing only users with profile properties set or all users who have completed any event.As described in the documentation: "You can select User Profiles or All Users in the Users page. If you select User Profiles, the page will only show users that have at least one user profile property set. If you select All Users, the page will show all users who have completed any event." Users: Explore your user base in MixpanelThe "All Users" view is particularly helpful when you want to see all users who have interacted with your product in any way, regardless of whether they have profile properties set. This can help you identify users who might be missing profile information but are still active in your application.Once you've selected your preferred view, you can further explore individual user histories by clicking on a user's name in the table, which will take you to their user profile with more detailed information about their activity.
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.
kapa.ai thanks, I think the Users > "Users" instead of "User with profiles" did the trick. I can see many more users now which I thought were missing.
Let me check the knowledge base for you again. One moment! 📚
I'm glad to hear that switching to the "All Users" view in the Users page helped you find the users you thought were missing! This confirms what the documentation mentions - the "All Users" view shows everyone who has completed any event in your application, even if they don't have profile properties set.This is a common point of confusion for Mixpanel users. The "User Profiles" view only shows users who have at least one profile property set, which can make it seem like some users are missing when they're actually just lacking profile properties.Now that you can see these users, you might want to consider: 1. Setting up profile properties for these users to make them appear in both views 2. Using this complete user list to create cohorts for further analysis 3. Exploring individual user histories by clicking on specific usersIs there anything specific you'd like to know about working with these newly found users in Mixpanel?
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.
kapa.ai a follow-up question, when does a user become a "user with profile" vs "users", i.e. at what point is the profile created for a user.
Let me check the knowledge base for you again. One moment! 📚
Based on the knowledge sources, I can explain when a user becomes a "user with profile" versus just a "user" in Mixpanel:
User Profiles vs. All Users
A user becomes a "user with profile" (appears in the "User Profiles" view) only when at least one profile property has been set for that user. Until then, they'll only appear in the "All Users" view if they've completed any event.
Creating User Profiles
User profiles are not created automatically. They require explicit profile property setting through one of these methods: 1. Using SDK methods: You must call both .identify()
and a profile property setting method like .people.set()
or .getPeople().set()
For example, in JavaScript: LBKS// You must call identify to associate the profile update with the user mixpanel.identify('12345'); mixpanel.people.set({ plan: 'Premium' });LBKS
As noted in the documentation: "The people.set() method is the required call to set user properties on a user profile. However, the people.set() call also requires an identify() call at some point in the same session, so that Mixpanel knows which User ID to associate the profile properties to." Identity Management Best Practices2. Via API: Using the HTTP Engage API to set profile properties3. Importing profiles: Through the UI by uploading CSVs or using Warehouse Connectors4. Integration partners: Through various integration partners that can create profilesIt's important to note that simply calling .identify()
alone does not create a user profile. As the documentation states: "The mixpanel.identify() call does not create a User Profile in Mixpanel." You must explicitly set at least one profile property.If you call .people.set()
without first calling .identify()
in the same session, Mixpanel will store the profile properties locally until that user hits an identify() call.This explains why you were seeing users in the "All Users" view but not in the "User Profiles" view - they had generated events but didn't have any profile properties set.Would you like more information about how to set up user profiles for your existing users?
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.
kapa.ai, how long can it take for a new user to be registered (either in Users or Users with profile) ?
Let me check the knowledge base for you again. One moment! 📚
Based on the knowledge sources, there are different timeframes for when users appear in Mixpanel depending on whether you're looking at basic users or user profiles with properties.For basic users (appearing in "All Users" view): - Events are typically processed and visible in Mixpanel within minutes of being sent - Users who have completed any event should appear in the "All Users" view shortly after their first event is processedFor user profiles (appearing in "User Profiles" view): - Profile updates are processed similarly to events, usually within minutes - However, when identity management is involved (linking anonymous users to identified users), there can be delaysSpecifically for identity management: - For debugging purposes in the Activity Feed view, user identity updates happen in near real-time (less than 1 minute delay) - However, it may take up to 24 hours for identity mappings to fully propagate throughout the Mixpanel systemAs mentioned in the documentation: "It may take up to 24 hours for this mapping to propagate to all other parts of the system. This means that, in some cases, when analyzing a funnel that spans pre-login and post-login behavior in real-time, some may be shown as dropped-off, even though they've performed the conversion event." Identifying Users (Simplified)So in summary: - Basic user registration: Minutes - User profiles with properties: Minutes - Complete identity resolution across the system: Up to 24 hoursThis explains why you might see users in one view but not another immediately after they're created, especially if identity management is involved.Is there a specific scenario you're troubleshooting with user registration delays?
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.