how can I adapt this to export the Identity resolution master table instead of these two events? import requests, json, time, random import pandas as pd from datetime import datetime, timedelta # Auth & API config AUTH = my_auth # base64(api_secret:) URL = “https://data-eu.mixpanel.com/api/2.0/export” EVENTS = json.dumps([“Loaded a Page”,“Product Action Completed”]) HEADERS = {“Authorization”: AUTH, “Accept”: “text/plain”}
Hi Elena 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
To export the Identity Resolution master table (the identity mappings table) from Mixpanel, you cannot use the Raw Event Export API endpoint (/export) as you would for events. The identity mappings table is a separate data source, and its export is only supported via Mixpanel’s Data Pipelines product (specifically, JSON Pipelines or Schematized Export Pipelines), not via the standard event export API.
How to export the identity mappings table:
- You need to use Mixpanel’s Data Pipelines add-on, which allows you to export three types of data: events, people (user profiles), and identity mappings.
- The identity mappings table contains mappings between distinct_id and resolved_distinct_id and is required for accurate user identity resolution, especially if you have ID merge enabled.
- The exported identity mappings table will have columns like distinct_id and resolved_distinct_id [Mixpanel Docs: JSON Pipelines].
Example structure of the identity mappings table:
How to export: - Set up a Data Pipeline in Mixpanel to your data warehouse or cloud storage. - Select "identity" as the data source for your pipeline. - The exported data will be available in your destination as a table or file.
You cannot adapt your current script (which uses the Raw Event Export API) to export the identity mappings table, because that API does not support this data source. You must use Data Pipelines for this purpose [Mixpanel Docs: JSON Pipelines].
If you do not have access to Data Pipelines, there is no supported API endpoint to export the identity mappings table directly.
References: - JSON Pipelines: User Identity Resolution - Data Pipelines Overview
If you need help setting up Data Pipelines, please let me know!
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 export the Identity Resolution master table (identity mappings) using a JSON pipeline in Mixpanel, you need to set up a Data Pipeline from the Mixpanel UI and select "identity" as the data source. Here’s how you can do it:
1. Go to the Integrations page in your Mixpanel project.
2. Create a new pipeline and choose your destination (e.g., BigQuery, AWS S3, Google Cloud Storage, etc.).
3. Select "identity" as the data source when configuring the pipeline. This will export the identity mappings table, which contains distinct_id and resolved_distinct_id columns.
4. Complete the setup and start the pipeline. The exported data will appear in your destination as a table or files, depending on your configuration.
You do not need to use a script or API call for this export—the process is managed through the Mixpanel UI. The exported identity mappings will allow you to resolve user identities in your warehouse or storage, matching Mixpanel’s own identity resolution logic. Always use the latest view/table as Mixpanel may update the underlying tables with each export [JSON Pipelines: User Identity Resolution].
Note: The knowledge sources do not provide a way to export the identity mappings table via a direct API call or Python script; it must be done through the Data Pipelines feature in the UI.
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! 📚
The term JSON pipeline refers to a type of Data Pipeline in Mixpanel. In Mixpanel documentation, "Data Pipelines" is the general feature that allows you to export your Mixpanel data (events, user profiles, identity mappings) to a data warehouse or cloud storage. There are two main types of Data Pipelines: JSON pipelines and Schematized pipelines.
- JSON Pipeline:
- Exports data in a high-level JSON format, with all properties under a properties key.
- Supports exporting events, people (user profiles), and identity mappings.
- The exported data is structured for flexibility and easier querying, especially in modern data warehouses.
- When you set up a JSON pipeline, you choose the data source (events, people, or identity), and the data is exported in JSON format to your destination [Json Pipelines].
- Data Pipeline (General): - Refers to the overall feature that includes both JSON pipelines and Schematized pipelines. - The setup process and management are the same; you choose the pipeline type and data source during configuration. - The term "Data Pipeline" encompasses all export options, not just JSON format [Data Pipelines Overview].
In summary: A JSON pipeline is a specific type of Data Pipeline that exports data in JSON format. All JSON pipelines are Data Pipelines, but not all Data Pipelines are JSON pipelines (some may be schematized, exporting data in a table schema format). The process for exporting the identity mappings table is the same: you use the Data Pipelines feature, select JSON pipeline, and choose "identity" as the data source.
If you want to export the identity resolution master table, you must use a Data Pipeline of type JSON pipeline and select "identity" as the data source during setup [Json Pipelines].
If you need more details on the differences between JSON and schematized pipelines, let me know!
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! 📚
The people and identity data sources in Mixpanel Data Pipelines serve different purposes:
- People data source exports user profiles. A user profile is a key/value store that holds state about a user, such as their properties (e.g., name, email, plan). This data is mutable and is replaced with the latest user profiles each time an export occurs. The exported table is typically named mp_people_data and contains columns like distinct_id and a JSON object of user properties under the properties key [People Data Support].
- Identity data source exports the identity mappings table. This table is crucial for projects with ID merge enabled, as it maps multiple identifiers (distinct_ids) to a single resolved user identifier (resolved_distinct_id). This allows you to accurately replicate Mixpanel’s user counting and identity resolution logic in your own data warehouse. The identity mappings table contains columns like distinct_id and resolved_distinct_id [User Identity Resolution].
In summary: - People: User profile properties (state about a user). - Identity: Mappings between user identifiers for identity resolution.
These data sources are both available when setting up a JSON pipeline, but they serve distinct analytical and operational needs.
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! 📚
I'm sorry, but the knowledge sources do not mention any way to extract the identity data (identity mappings table) from Mixpanel without using a Data Pipeline or JSON pipeline. The documentation specifies that exporting the identity mappings table is supported via Data Pipelines, where you select "identity" as the data source during pipeline setup. There is no reference to an API or other method for exporting this data outside of the Data Pipelines feature JSON Pipelines: User Identity Resolution.
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.
