The issue you're experiencing is related to how Mixpanel handles identity resolution and how this data is represented in exported data versus the Mixpanel interface. Let me explain why you're unable to find the resolved_distinct_id in the Mixpanel interface:
1. Identity Resolution in Exports:
When you export data from Mixpanel to BigQuery (or other data warehouses), Mixpanel provides an identity mappings table that includes both the original distinct_id and a resolved_distinct_id. This resolved_distinct_id is the canonical identifier that Mixpanel uses internally to represent a unique user after merging multiple identifiers.
2. Mixpanel Interface Display:
In the Mixpanel interface, you don't see the resolved_distinct_id directly. Instead, Mixpanel chooses one of the identifiers from the user's identity cluster to display as the user's ID. This is explained in the [Identifying Users (Original) FAQ](https://docs.mixpanel.com/docs/tracking-methods/id-management/identifying-users-original#faq):
"The canonical distinct_id is selected by Mixpanel using any of the IDs inside of a cluster. This means that even after identifying your user, Mixpanel may choose your user ID or one of the other IDs inside of the cluster (such as the device ID) to serve as the displayed ID for the user. **This is random and not user-configurable.**"
3. Best Practice for User Identification:
To address this discrepancy, Mixpanel recommends setting your chosen user ID (like UUID or email) as a separate user profile property and event property. This way, you can always query and see your own chosen user ID. As stated in the same FAQ:
"As a best practice, please set your chosen user ID as a separate user profile property and event property so that you can always query and see your own chosen user ID."
To resolve your specific issue:
1. Make sure you're setting your UUID and email as separate user profile properties when identifying users.
2. In your BigQuery queries, join the identity mappings table with your events table as you're doing, but also include a join with the user profiles table to retrieve the UUID and email fields you've set.
Here's an example of how you might modify your query to include these fields (note that this is a conceptual example and may need to be adjusted based on your exact schema):
