Mixpanel connector
Set up the Mixpanel connector in Kaivo: authentication, configuration, the 6 BigQuery tables it syncs, and answers to common questions.
Mixpanel connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Mixpanel data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your marketing and sales data instead of moving it.
What is the Mixpanel connector
Section titled “What is the Mixpanel connector”Sync your Mixpanel product analytics into BigQuery with Kaivo to analyse events and user behaviour alongside the rest of your data.
| Category | Marketing & Sales, Tech |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Mixpanel connector
Section titled “Getting started with the Mixpanel connector”- Sign up for Kaivo and create a workspace.
- Connect your Mixpanel account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating Mixpanel
Section titled “Authenticating Mixpanel”The Mixpanel connector supports 2 ways to connect. Pick the one that fits how you work.
Service Account
Section titled “Service Account”Authenticate with your Mixpanel credentials. You provide:
| Field | Description |
|---|---|
| Username | |
| Mixpanel Service Account Username. See the docs for more information on how to obtain this. |
| | Secret |
Mixpanel Service Account Secret. See the docs for more information on how to obtain this.
| | Project ID |
Your project ID number. See the docs for more information on how to obtain this.
|
Project Secret
Section titled “Project Secret”Authenticate with your Project Secret.
| Field | Description |
|---|---|
| Project Secret | |
| Mixpanel project secret. See the docs for more information on how to obtain this. |
|
Configuring the Mixpanel connector
Section titled “Configuring the Mixpanel connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Attribution Window | |
| A period of time for attributing results to ads and the lookback period after those actions occur during which ad results are counted. |
| | Project Timezone |
Time zone in which integer date times are stored. The project timezone may be found in the project settings in the Mixpanel console.
| | Select Properties By Default |
Setting this config parameter to TRUE ensures that new properties on events and engage records are captured. Otherwise new properties will be ignored.
| | Start Date |
Any data before this date will not be fetched.
| | Region |
The region of your Mixpanel instance, either US or EU.
|
Tables and columns synced from Mixpanel
Section titled “Tables and columns synced from Mixpanel”Kaivo syncs 6 tables from Mixpanel into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
annotations (9 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
date |
TIMESTAMP |
The date of the annotation in ISO 8601 date-time format. |
project_id |
INT64 |
The identifier of the project to which the annotation belongs. |
id |
INT64 |
The unique identifier of the annotation. |
description |
STRING |
The description or notes associated with the annotation. |
user__id |
INT64 |
The unique identifier of the user. |
user__first_name |
STRING |
The first name of the user. |
user__last_name |
STRING |
The last name of the user. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
cohort_members (17 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
cohort_id |
INT64 |
The unique identifier of the cohort to which the member belongs |
distinct_id |
STRING |
The distinct identifier of the cohort member |
browser |
STRING |
The web browser used by the cohort member |
browser_version |
STRING |
The version of the web browser used by the cohort member |
city |
STRING |
The city where the cohort member is located |
country_code |
STRING |
The country code of the country where the cohort member is located |
region |
STRING |
The region where the cohort member is located |
timezone |
STRING |
The timezone of the cohort member |
last_seen |
TIMESTAMP |
The date and time when the cohort member was last seen |
email |
STRING |
The email address of the cohort member |
name |
STRING |
The name of the cohort member |
first_name |
STRING |
The first name of the cohort member |
last_name |
STRING |
The last name of the cohort member |
id |
STRING |
The unique identifier of the cohort member |
unblocked |
STRING |
Indicator of whether the cohort member is unblocked |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
cohorts (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
The unique identifier of the cohort data. |
data_group_id |
INT64 |
The identifier of the data group to which the cohort belongs. |
name |
STRING |
The name or title of the cohort data. |
description |
STRING |
A brief description or summary of the cohort data. |
created |
TIMESTAMP |
The date and time when the cohort data was created. |
count |
INT64 |
The total count or number associated with the cohort data. |
is_visible |
INT64 |
A flag indicating the visibility status of the cohort data. |
project_id |
INT64 |
The identifier of the project to which the cohort data belongs. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
engage (16 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
distinct_id |
STRING |
The unique identifier for the user. |
browser |
STRING |
The type of browser used by the user. |
browser_version |
STRING |
The version of the browser used by the user. |
city |
STRING |
The city where the user is located. |
country_code |
STRING |
The country code of the user’s location. |
region |
STRING |
The region where the user is located. |
timezone |
STRING |
The timezone of the user’s location. |
last_seen |
TIMESTAMP |
The date and time when the user was last seen. |
email |
STRING |
The email address of the user. |
name |
STRING |
The full name of the user. |
first_name |
STRING |
The first name of the user. |
last_name |
STRING |
The last name of the user. |
id |
STRING |
The unique ID associated with the user. |
unblocked |
STRING |
Indicates whether the user is unblocked or not. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
funnels (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
funnel_id |
INT64 |
Unique identifier for the funnel. |
name |
STRING |
Name of the funnel. |
date |
DATE |
Date field for the funnel data. |
datetime |
TIMESTAMP |
Date and time field for the funnel data. |
analysis__completion |
INT64 |
Completion metric value. |
analysis__starting_amount |
INT64 |
Starting amount of users in the funnel. |
analysis__steps |
INT64 |
Total number of steps in the funnel. |
analysis__worst |
INT64 |
Worst performing step in the funnel. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: funnels__steps
Section titled “Subtable: funnels__steps”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
count |
INT64 |
Count of users in this step. |
custom_event |
BOOL |
Custom event associated with the step. |
custom_event_id |
INT64 |
Unique identifier for the custom event. |
avg_time |
FLOAT64 |
Average time taken in the step. |
avg_time_from_start |
FLOAT64 |
Average time taken from the start to this step. |
goal |
STRING |
Goal set for the step. |
overall_conv_ratio |
FLOAT64 |
Overall conversion ratio for the step. |
step_conv_ratio |
FLOAT64 |
Conversion ratio for the step. |
event |
STRING |
Event triggered in this step. |
session_event |
STRING |
Session event recorded for the step. |
step_label |
STRING |
Label for the step. |
selector |
STRING |
Selector for the step. |
selector_params__step_label |
STRING |
Label for the step selector. |
time_buckets_from_start__lower |
INT64 |
Lower range boundary for time buckets. |
time_buckets_from_start__higher |
INT64 |
Higher range boundary for time buckets. |
time_buckets_from_prev__lower |
INT64 |
Lower range boundary for time buckets. |
time_buckets_from_prev__higher |
INT64 |
Higher range boundary for time buckets. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: funnels__steps__time_buckets_from_start__buckets
Section titled “Subtable: funnels__steps__time_buckets_from_start__buckets”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: funnels__steps__time_buckets_from_prev__buckets
Section titled “Subtable: funnels__steps__time_buckets_from_prev__buckets”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
revenue (7 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
date |
DATE |
Date for which the revenue data is recorded |
datetime |
TIMESTAMP |
Date and time for which the revenue data is recorded |
count |
INT64 |
Number of revenue transactions for the specified date |
paid_count |
INT64 |
Number of successful paid transactions for the specified date |
amount |
FLOAT64 |
Total revenue amount for the specified date |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Mixpanel sync works
Section titled “How the Mixpanel sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Mixpanel supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for Mixpanel?
Section titled “How long does the initial sync take for Mixpanel?”It depends on how much history is in your Mixpanel account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when Mixpanel’s schema changes?
Section titled “What happens when Mixpanel’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Mixpanel, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Mixpanel instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Mixpanel connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Mixpanel data
Section titled “Common use cases for Mixpanel data”Event analysis
Section titled “Event analysis”Analyse your Mixpanel events to study the actions that matter most over time.
Funnel and retention
Section titled “Funnel and retention”Use event and user data to track how users move through key flows and come back.
Product context
Section titled “Product context”Join product behaviour with your revenue data to connect usage to outcomes.
Use Mixpanel data in your AI and BI tools
Section titled “Use Mixpanel data in your AI and BI tools”Once Mixpanel data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Mixpanel data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Mixpanel connector pricing and plan details.
Related connectors
Section titled “Related connectors”- Google Ads: Sync Google Ads to BigQuery.
- Custobar: Sync Custobar to BigQuery.
- Google Search Console: Sync Google Search Console to BigQuery.
- HubSpot: Sync HubSpot to BigQuery.
- Adform: Sync Adform to BigQuery.
- Amplitude: Sync Amplitude to BigQuery.