Mixpanel
Prerequisites
To set up the Mixpanel source connector, you'll need a Mixpanel Service Account and it's Project ID, the Project Timezone, and the Project region (US or EU).
Setting up the Mixpanel connector
| No | Item | Required | Example | Notes |
|---|---|---|---|---|
| 1 | Authentication * | Yes | Choose how to authenticate to Mixpanel Refer to the documentation in the form while using the connector Service AccountProject Secret | |
| 2 | Project ID | No | Your project ID number. See the docs for more information on how to obtain this. | |
| 3 | Attribution Window | No | A period of time for attributing results to ads and the lookback period after those actions occur during which ad results are counted. Default attribution window is 5 days. | |
| 4 | Project Timezone | No | US/Pacific UTC | Time zone in which integer date times are stored. The project timezone may be found in the project settings in the Mixpanel console. |
| 5 | Select Properties By Default | No | Setting this config parameter to TRUE ensures that new properties on events and engage records are captured. Otherwise new properties will be ignored. | |
| 6 | Start Date | No | 2021-11-16 | The date in the format YYYY-MM-DD. Any data before this date will not be replicated. If this option is not set, the connector will replicate data from up to one year ago by default. |
| 7 | End Date | No | 2021-11-16 | The date in the format YYYY-MM-DD. Any data after this date will not be replicated. Left empty to always sync to most recent date |
| 8 | Region | No | The region of mixpanel domain instance either US or EU. | |
| 9 | Date slicing window | No | Defines window size in days, that used to slice through data. You can reduce it, if amount of data in each window is too big for your environment. |
Tables in the Mixpanel connector
| No | Table Name | Columns | Primary Keys | Read Mode | Inc. Sync Keys | API Info |
|---|---|---|---|---|---|---|
| 1 | cohort_members | 15 | distinct_id | Full Refresh | last_seen | |
| 2 | revenue | 5 | Full Refresh | date | API Reference | |
| 3 | engage | 14 | Full Refresh | API Reference | ||
| 4 | funnels | 6 | funnel_id, date | Full Refresh, Incremental | date | API Reference |
| 5 | annotations | 4 | Full Refresh | API Reference | ||
| 6 | export | 6 | Full Refresh | time | API Reference | |
| 7 | cohorts | 8 | id | Full Refresh | created | API Reference |
Table: cohort_members
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | last_seen | VARCHAR | Incremental sync key |
| 2 | city | VARCHAR | |
| 3 | timezone | VARCHAR | |
| 4 | last_name | VARCHAR | |
| 5 | cohort_id | INTEGER | |
| 6 | country_code | VARCHAR | |
| 7 | unblocked | VARCHAR | |
| 8 | distinct_id | VARCHAR | Primary Key |
| 9 | browser | VARCHAR | |
| 10 | name | VARCHAR | |
| 11 | browser_version | VARCHAR | |
| 12 | id | VARCHAR | |
| 13 | region | VARCHAR | |
| 14 | first_name | VARCHAR | |
| 15 | email | VARCHAR |
Table: revenue
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | date | VARCHAR | Incremental sync key |
| 2 | paid_count | INTEGER | |
| 3 | datetime | VARCHAR | |
| 4 | amount | DOUBLE | |
| 5 | count | INTEGER |
Table: engage
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | last_seen | VARCHAR | |
| 2 | city | VARCHAR | |
| 3 | timezone | VARCHAR | |
| 4 | last_name | VARCHAR | |
| 5 | country_code | VARCHAR | |
| 6 | unblocked | VARCHAR | |
| 7 | distinct_id | VARCHAR | |
| 8 | browser | VARCHAR | |
| 9 | name | VARCHAR | |
| 10 | browser_version | VARCHAR | |
| 11 | id | VARCHAR | |
| 12 | region | VARCHAR | |
| 13 | first_name | VARCHAR | |
| 14 | email | VARCHAR |
Table: funnels
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | date | VARCHAR | Incremental sync key, Primary Key |
| 2 | datetime | VARCHAR | |
| 3 | funnel_id | INTEGER | Primary Key |
| 4 | name | VARCHAR | |
| 5 | analysis | VARCHAR | |
| 6 | steps | VARCHAR |
Table: annotations
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | date | VARCHAR | |
| 2 | project_id | INTEGER | |
| 3 | description | VARCHAR | |
| 4 | id | INTEGER |
Table: export
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | distinct_id | VARCHAR | |
| 2 | time | VARCHAR | Incremental sync key |
| 3 | event | VARCHAR | |
| 4 | sampling_factor | INTEGER | |
| 5 | dataset | VARCHAR | |
| 6 | labels | VARCHAR |
Table: cohorts
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | is_visible | INTEGER | |
| 2 | project_id | INTEGER | |
| 3 | data_group_id | INTEGER | |
| 4 | created | VARCHAR | Incremental sync key |
| 5 | name | VARCHAR | |
| 6 | count | INTEGER | |
| 7 | description | VARCHAR | |
| 8 | id | INTEGER | Primary Key |
External Resources
- Service Account
- Project Id
- Project Timezone
- Mixpanel Service Account Secret
- Mixpanel Project Id
- Timezone
- Region
- Cohort Members
Zipstack Cloud features a powerful SQL querying engine on top of many types of connectors, including those from Trino, some custom connectors and connectors from the open source Airbyte project. Some Zipstack cloud connectors are designed to utilize and expand upon Airbyte's connector protocol, but they do not use Airbyte's EL core. Additionally, some parts of the documentation for these connectors have been adapted from the connector documentation found in Airbyte's open source project.