Mixpanel

SuprSend mixpanel integration enables you to export user cohorts from mixpanel and create subscriber lists on SuprSend. You can then trigger notification to this list using our broadcast API.

Getting Started

To start syncing mixpanel data, you need to first setup custom webhook integration in your mixpanel dashboard.

1. Go to SuprSend dashboard -> Settings -> Connectors page
2. Click on Mixpanel. It will open integrations page. Just add mapping key and click on enable. Mapping key is the unique identifier of user on SuprSend.

🚧

Choosing the mapping key

• Choose a key which is unique for all users and will correspond to the distinct_id of user on SuprSend.
• Once mapping key is defined, it cannot be changed, so choose it carefully.
• We recommend using mixpanel_distinct_id since it is unique identifier in mixpanel.

3. Once enabled, you'll see webhook configuration details. Go to Mixpanel dashboard -> Integrations -> Custom Webhook section and click on Add connection.
4. Copy paste the webhook details from SuprSend integrations page to Mixpanel custom webhook settings and click on "Continue"

SuprSend webhook is now setup in your mixpanel account. You can now start exporting user cohorts.

Export Cohorts

Cohort is a filtered list of users in mixpanel. You can export cohort to create subscriber list in SuprSend. Follow below steps to export cohort:

1. Go to Cohorts page and click on "Create Cohort"

2. It will open cohort settings. Add filter and give a name to the cohort. This name will also be the name of the subscriber list on SuprSend.

3. Once cohort is created, export the cohort to the SuprSend webhook that we just configured.

4. You can do 2 types of cohort exports - One time and Recurring. We recommend using recurring sync to keep Mixpanel and SuprSend data in sync. Click on Begin Sync to start cohort sync. Data is updated every 30 mins from sync start time.

Congratulations! Mixpanel integration is now complete. You can now track the status of cohort sync on mixpanel logs page. Logs can be accessed from the connector page itself.