Mixpanel
Mixpanel is a real-time analytics platform that helps companies measure and optimize user engagement.
For more information about the API, see the Mixpanel Query API and Event Export API.
See the Schema section for a list of objects available for replication.Mixpanel integration summary
Preparing for authentication
To access your data, you need to authenticate the connection with your account credentials.
To obtain the project timezone and API secret:
- Make sure you have the Admin privileges in Mixpanel. You need them to access the API secret.
- Log into your Mixpanel account.
- In the dropdown menu in the upper left corner of the page, select the project you want to replicate data from.
- Hover over the Settings icon in the upper right corner. In the Project Settings section, click the name of your project.
- Copy the Project Timezone and API Secret.
Creating the connection
For more information, see Connecting to SaaS applications.
- Fill in the required connection properties.
Provide a name for the connection in Connection name.
Select Open connection metadata to define metadata for the connection when it has been created.
Click Create.
Setting | Description |
---|---|
Data gateway | Select a Data Movement gateway if required by your use case. Information note This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None. For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement. |
Start Date | Enter the date, in the format |
API Secret | API secret. |
Attribution Window (days) | Enter the number of days you want your tables’ attribution window to be. |
Project Timezone | Project timezone. |
Export Events (optional) | Enter the events separated by a comma. Example: Page Viewed, Signed Up . |
Select Properties By Default | To capture new properties automatically in the events and engage tables, select the check box. Otherwise, new properties will be ignored. |
EU Residency | To process and store your customers’ personal data in Europe, select the check box. |
Schema
Mixpanel free plan
The engage
and export
tables are not available if you are using the free Mixpanel plan.
Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.
The schema and info displayed below is for version 1.
Depending on your destination, table and column names may not appear as they are outlined below.
annotations
The annotations
table contains info about annotations.
Replication Method | Full Table |
Primary Key | date |
Useful links |
cohort_members
The cohort_members
table contains info about the cohorts user profiles belong to.
Replication Method | Full Table |
Primary Keys | cohort_id distinct_id |
Useful links |
cohorts
The cohorts
table contains info about the cohorts in a Mixpanel project.
Replication Method | Full Table |
Primary Key | id |
Useful links |
engage
The engage
table contains info about user profiles.
The schema for this table is dynamic, meaning that the detected columns are dependent upon the properties provided upon upload in Mixpanel. For every property available in Mixpanel for engage
records, a column will be displayed in the integration’s Tables to Replicate tab.
Replication Method | Full Table |
Primary Key | distinct_id |
Useful links |
export
The export
table contains “raw data dumps” of tracked events. The API endpoint for EU region servers will return a 200 terminated early
error code.
Table schema
The schema for this table is dynamic, meaning that the detected columns are dependent upon the properties provided upon upload in Mixpanel. For every property available in Mixpanel for export
records, a column will be displayed in the integration’s Tables to Replicate tab.
Replication with attribution window
This table is replicated using the Attribution Window value defined in the integration’s settings page. Refer to the Replication section for more info.
Distinct events and loading behavior
As a Primary Key is not used for this table, data will be loaded using Append-Only loading. This means you may see duplicate records in your destination, which requires a querying strategy that selects the latest version of each record.
This approach allows to track events without a distinct_id
. In Mixpanel, distinct_id
is used to identify a unique user:
Mixpanel’s client-side tracking libraries automatically assign a distinct_id to a user when they first visit a website or an application that has Mixpanel installed. Distinct_id should not contain any special characters such as forward slashes, as it will break the URL. Distinct_ids can and often should be sent in server-side implementations as well.
In order to replicate records’ distinct_id
attributes, your server-side Mixpanel implementation must send them with tracked events. If the server-side implementation doesn’t do this, this attribute will be null
.
Previous versions of Mixpanel integration used distinct_id
as part of a composite Primary Key for this table. However, due to the possibility of this attribute being null
, a Primary Key is not used for this table, as null
values in Primary Key columns will prevent successful Extraction.
When working with exports
data in your destination, you’ll need to use a querying strategy that accounts for the Append-Only loading used by this table. We recommend using the following columns to de-duplicate records, along with the approach outlined in the Querying Append-Only tables guide:
distinct_id
event
time
Replication Method | CDC |
Loading Behavior | Append-Only |
Replication Key | time |
Useful links |
funnels
The funnels
table contains data about your Mixpanel funnels, segmented by funnel and day.
Note: This table is replicated using the Attribution Window value defined in the integration’s settings page. Refer to the Replication section for more info.
Replication Method | CDC |
Primary Keys | funnel_id date |
Replication Key | date |
Useful links |
revenue
The revenue
table contains info about revenue, segmented by day. The API endpoint for EU region servers will return a 400 bad requests (Timeout Error)
code.
Note: This table is replicated using the Attribution Window value defined in the integration’s settings page. Refer to the Replication section for more info.
Replication Method | CDC |
Primary Key | date |
Replication Key | date |