Hello, I'm having an issue with identifying users in Mixpanel. I have an integration set up where my app sends events to Segment, and Segment then forwards them to Mixpanel. However, I am seeing a data mismatch between the two.
Example:
Today Segment recorded 9 profile_created events, and I can see them marked as successfully forwarded to Mixpanel. (The data matches in the CRM too, 9 new users in Hubspot)
On Mixpanel, in the Events table, only 5 profile_created events appear.
The Users Table, only shows 5 new users.
At first I thought this was just an ingestion delay (since I’ve read that Mixpanel can take up to 24–48 hours to process and merge events), but that doesn’t seem to be the case here — the numbers remain mismatched even after waiting. The project uses the simplified ID Merge API. To summarise:
Anonymous usage: Before login, events are tracked as anonymous. These anonymous events do show up in Mixpanel.
Identify: When the user is known (sign-in, app relaunch with session, or profile creation), we call identify(userId).
sign-in -> works correctly
app relaunch with session -> works correctly
profile creation: After the profile is created, we call identify(userId) and trackEvent('profile_created'); here is where we intermittently see the drop in Mixpanel.
I followed the guide and everything makes sense, but I still don't understand what is causing the issue. Some help would be much appreciated! Thanks :)
Hi Alessandro- Julianne from Mixpanel Support here! Diving right in, since the data is making it to Segment, it sounds like the issue is likely either with Segment sending the data to Mixpanel or Mixpanel ingesting the data. Do all of the profile_created events show as delivered in the 'Delivery Overview' for the Mixpanel destination? If they do, can you submit a ticket directly via our web form? When you submit the ticket, it would be helpful if you included a specific payload being sent from Segment that is missing in Mixpanel. Note, you may need to reach out to Segment support for the payload. This will allow a support engineer to look into the specific project in which you're seeing the behavior.
