Export Mixpanel cohorts to MoEngage to create custom segments that you can apply in your MoEngage campaigns. Manage the MoEngage integration from the Mixpanel integrations page.
MoEngage also supports an integration to send messaging interactions to Mixpanel - for more details, see MoEngage's Mixpanel integration.
Permissions
You must be a Mixpanel project admin to enable the MoEngage integration. Read more about project roles and permissions here.
Enable the Integration
To enable the integration, select Integrations under the Data Management tab in the top navigation bar:
From the Integrations page, select the MoEngage dropdown, and select Connect.
The connection uses a Basic Authorization Username/Password system. You will need to provide two credentials to authorize the connection:
- Username: MoEngage APP ID
- Password: MoEngage API Key
You will additionally provide one credential to authorize the cohort exports:
- MOE-APPKEY: MoEngage APP ID
You can find these values in your MoEngage settings page - note that MoEngage App ID is used in both the Username and MOE-APPKEY fields.
The MoEngage integration will show a "Connected" tag in the UI once the connection succeeds.
Matching Users between MoEngage and Mixpanel
Mixpanel only exports identified user profiles to match to MoEngage - users without user profiles (i.e. anonymous users) will not export.
If the values you provide for users' distinct_id differ from the values used for MoEngage's Unique ID, the user's Mixpanel profile must contain a user property, "$moengage_user_id", whose value is a string representing that user's Unique ID in MoEngage. Exports will include this joining key to match to corresponding the Unique ID in MoEngage.
In addition, when its ingestion service detects calls setting this user property, Mixpanel will also alias the value of "$moengage_user_id" to the user's distinct_id when setting that user property. This ensures that messaging events passed from MoEngage to Mixpanel still attribute to the correct user.
If you use the same system of user identifiers in both tools, you do not have to declare "$moengage_user_id" - MoEngage will instead use the Mixpanel distinct_id to map a user to its MoEngage equivalent if no "$moengage_user_id" is present for a user.
Note that exports are used solely for matching user identities between products - the integration will not send the full set of a user's profile properties to MoEngage, nor will it generate new user profiles in MoEngage.
Export a Cohort
You can export a cohort to MoEngage from the Cohorts report. Navigate to Cohorts by clicking Cohorts under Users in the navigation bar.
Select the cohort that you want to export. Click on the three-dot icon on the right side of the cohort.
Click Export to MoEngage. Select either one-time sync or dynamic sync. Click Start Sync.
Sync Types
This integration supports two types of exports: one-time export and dynamic sync.
One-Time Export
In a one-time export, Mixpanel sends MoEngage a static export of users who currently qualify for the cohort. The cohort data will not be updated in MoEngage after a one-time export.
Dynamic Sync
In dynamic sync, Mixpanel initiates sync between a cohort and MoEngage every two hours. The exported cohort will be updated every two hours to reflect the most recent list of users in a cohort.
When you generate a one-time export or dynamic sync, it overwrites the previous export with an updated export that reflects users who qualify for the cohort at the time of export.
Select the Custom Segment in MoEngage
Once the export completes, you will see a custom segment reflecting the set of users from your Mixpanel cohort (e.g. "Power Users"):
MoEngage events into Mixpanel & MTU exemptions
MoEngage offers the ability to forward campaign interaction events to Mixpanel. For more detail, please refer to MoEngage's integration guide.
Events coming from MoEngage are marked with the property "$source" to denote the source product.
Mixpanel will exempt certain messaging outreach events from MTU calculations, meaning you're free to send campaigns to dormant users without them counting towards MTU billing (only once a user engages with a message will they then be counted towards that tally).
The following events are exempt from MTU calculations:
Card SentCard DeliveredConnector SentEmail SentEmail DeferredEmail DeliveredEmail DroppedEmail BouncedEmail Soft BouncedNotification Received AndroidNotification Sent iOSNOTIFICATION_RECEIVED_IOS_MOENotification Received WebSMS SentSMS DeliveredUser Entered FlowUser Exited Flow
Comments
Article is closed for comments.