Mixpanel Integration

About Mixpanel

Mixpanel makes analytics self-serve for your product teams and enables everyone to answer questions around user conversion, retention and activation.

Mixpanel Integration

The Mixpanel Integration with MoEngage consists of two parts -

Cohort Sync from Mixpanel to MoEngage:

This integration allows you to export cohorts in Mixpanel to Moengage and send personalized campaigns to all the users under this cohort from MoEngage. 

Streaming MoEngage Events to Mixpanel

This integration allows you to export the campaign interaction events generated after your users engage with the MoEngage campaigns to Mixpanel.

How can this integration help you?

The Mixpanel - MoEngage Integration will allow you to leverage the advanced cohorts that you have in Mixpanel and target them through one of the Moengage campaigns directly and also see the campaign events from MoEngage in your Mixpanel cohorts / analytics views.

Below are a few use-cases where the integration can add a lot of value to your analytics + user engagement activities -

  • E-commerce: Understand the seasonal changes in purchase trends that are happening and send rich push notifications to such users via MoEngage. For example, target the cohort of users who purchase high value items during summers and send the rich push notifications with similar recommended items.

  • Travel: You can create a cohort in Mixpanel of millennial users who are also premium users of your app and send them popular and unique holiday destination recommendations via MoEngage emails.

  • E-learning: Understand where your users are dropping off while watching a video series on your platform and bring them back with engaging campaigns! Through insights into user behavior, you are armed with a holistic picture of exactly what actions can trigger a user to return to the app.

Enabling Mixpanel <> MoEngage Integration for your account.

  1. Cohort Sync from Mixpanel to MoEngage: This integration will be listed in your Mixpanel account now and you can go to your Mixpanel dashboard and enable this.

  2. Exporting Campaign Events from MoEngage to Mixpanel: To do this, you need to reach out to your MoEngage Customer Success Manager or write a note to support@moengage.com with a few details mentioned in the next sections.

Setting up MoEngage integration on Mixpanel

To setup MoEngage Integration on Mixpanel, follow the below steps:

Step 1: Login to Mixpanel and navigate to Data Management -> Integrations

Screen_Shot_2020-09-10_at_2.03.51_PM.png

Step 2: On the Integrations page, search MoEngage and click on the CONNECT button. You will see a pop-up to enter the MoEngage credentials as shown below -

Screen_Shot_2020-09-10_at_2.15.11_PM.png

Here, the Moengage APP_KEY (DATA API KEY) and DATA API SECRET are available on the Moengage dashboard.


Step 3: Find MoEngage App Id and Secret Key on the MoEngage Dashboard. Login to your MoEngage Dashboard and navigate to Settings -> API Settings. Pick up the Data API ID and Data API Key as shown in the below image -

Screen_Shot_2020-09-10_at_2.17.10_PM.png

Step 5: Complete the Integrations Setup:

After configuration on the Mixpanel dashboard, click save on continue to connect MoEngage as an integration.

Exporting Cohorts from Mixpanel to MoEngage

To export specific cohorts from Mixpanel to MoEngage, please follow the below steps:

Step 1: Go to the cohorts page on Mixpanel dashboard as shown below -

Screen_Shot_2020-09-10_at_2.26.29_PM.png

 

Step 2: Click on the three dots menu on the right-hand side of any cohort that you want to export to MoEngage. Once you click here, you will see an option to export this cohort to MoEngage.

Screen_Shot_2020-09-10_at_2.05.50_PM.png

Step-3: Click on the export to MoEngage option. A pop-up will open up with the below options 

Screen_Shot_2020-09-10_at_2.06.06_PM.png

Select any one of the following options:

  • One-time export: This will only export the users under the cohort to MoEngage once and the cohort will not sync thereafter.
  • Dynamic sync: This option will ensure that the updated information of the cohorts like the new users who qualify for this cohort and the existing users who are removed from the cohort are sent to MoEngage every two hours.

Step-4: You can check the export status after you export the cohort as shown below -

Screen_Shot_2020-09-10_at_2.06.28_PM.png

Using Cohorts in MoEngage Campaigns

Once an export is complete, you would be able to see the cohort as a custom segment in MoEngage like below - 

 Screen_Shot_2020-09-10_at_4.17.27_PM.png

The custom segment can be used in any MoEngage campaigns to send personalized messages to the users under this segment.

 

Exporting Campaign Data from MoEngage to Mixpanel

Setup

Please send an email to your MoEngage Customer Success Manager or to support@moengage.com with the below details -

  1. Integration Name - Mixpanel
  2. Mixpanel project token - This is available on your Mixpanel Dashboard -> Settings -> Overview -> Access Keys -> Project Token as shown below -
    mixpanelsettings.png
  3. (Optional) Additional events, user attributes or device attributes that you want to see with each event in Mixpanel. By default, MoEngage will be sending the data points mentioned in the next section to Mixpanel.

Data

Following data points will be sent by default to Mixpanel:

Event Name Event Code Type (for reference only) Channel Description
Card Sent n_c_s Delivery Cards Tracked when a Card notification is sent to the user, doesn't indicate if the notification is delivered to the App Inbox
Card Delivered

MOE_CARD

_CAMPAIGN_DELIVERED

Delivery Cards Tracked when a Card is delivered to the App Inbox, after the user has opened the Inbox
Card Viewed

MOE_CARD

_CAMPAIGN_VIEWED

Delivery Cards Tracked when the user views a Card or scrolls down to it in the App Inbox
Card Clicked

MOE_CARD

_CAMPAIGN_CLICKED

Interaction Cards Tracked when the user clicks the Card in the App Inbox
Connector Sent MOE_CONNECTOR_SENT Delivery Connector Tracked when a connector was sent successfully.
Email Sent MOE_EMAIL_SENT Delivery Email Tracked when our system sends an email to a user.
Email Deferred MOE_EMAIL_DEFERRED Delivery Email Tracked when the receiving server is unable to accept your request, email sending will be re-tried in this case
Email Delivered MOE_EMAIL_DELIVERED Delivery Email Tracked when an email is delivered in an inbox
Email Dropped MOE_EMAIL_DROP Delivery Email Tracked when a user opens an email.
Email Bounced

MOE_EMAIL

_HARD_BOUNCE

Delivery Email Tracked when a user clicks on any link in the email.
Email Soft Bounced

MOE_EMAIL

_SOFT_BOUNCE

Delivery Email Tracked when an email is dropped. Email is dropped, when it's part of the bounce list, the unsubscribe list or the spam report list.
Email Opened MOE_EMAIL_OPEN Interaction Email Tracked when our system finds an email is soft bounced. Typically happens when there is a temporary delivery issue.
Email Clicked MOE_EMAIL_CLICK Interaction Email Tracked when our system finds an email is hard bounced. Typically happens when email address doesn't exist.
Email Unsubscribed

MOE_EMAIL

_UNSUBSCRIBE

Interaction Email Tracked when a user marks the email as spam.

Email Spam

Complained

MOE_EMAIL_SPAM Interaction Email Tracked when a user unsubscribes from receiving emails.

In-App Shown

Android

IN_APP_SHOWN Interaction In-App Tracked when an In-App message is shown to the user on Android device.

In-App Clicked

Android

IN_APP_CLICKED Interaction In-App Tracked when a user clicks In-App message on Android device.

In-App Closed

Android

IN_APP_CLOSE_CLICKED Interaction In-App Tracked when a user dismisses In-App message by clicking on close button on Android device.
In-App Shown iOS iOS_IN_APP_SHOWN Interaction In-App Tracked when a In-App message is shown to the user on iOS device.
In-App Clicked iOS iOS_IN_APP_CLICKED Interaction In-App Tracked when a user clicks In-App message on iOS device.
In-App Closed iOS

iOS_IN_APP

_CLOSE_CLICKED

Interaction In-App Tracked when a user dismisses In-App message by clicking on close button on iOS device.

Mobile In-App

Shown

MOE_IN_APP_SHOWN Interaction In-App V3 Tracked when a user is shown an in-app version 3 campaign

Mobile In-App

Clicked

MOE_IN_APP_CLICKED Interaction In-App V3 Tracked when a user clicks an in-app version 3 campaign

Mobile In-App

Dismissed

MOE_IN_APP_DISMISSED Interaction In-App V3 Tracked when a user closes an in-app version 3 campaign
Notification Received Android NOTIFICA TION_RECEIVED_MOE Delivery Push Tracked when a user receives a notification on an Android device.
Notification Clicked Android NOTIFICA TION_CLICKED_MOE Interaction Push Tracked when a user clicks notification on an Android device.
Notification Sent iOS n_i_s Delivery Push Tracked when a user receives a notification on an iOS device.

NOTIFICATION

_RECEIVED

_IOS_MOE

NOTIFICATION_RECEIVED

_IOS_MOE

Delivery Push Tracked when App in foreground and user receives the notification on iOS.
Notification Clicked iOS

NOTIFICA TION_CLICKED

_IOS_MOE

Interaction Push Tracked when a user clicks notification on an iOS device.

Notification

Received Web

NOTIFICATION_RECEIVED

_WEB_MOE

Delivery Push Tracked when a user receives a notification on a browser.

Notification

Clicked Web

NOTIFICATION_CLICKED

_WEB_MOE

Interaction Push Tracked when a user clicks notification on the browser.

On-site

Message

Shown

MOE_ONSITE

_MESSAGE_SHOWN

Interaction On-site Tracked when an on-site messaging campaign is shown to a user

On-site

Message

Clicked

MOE_ONSITE

_MESSAGE_CLICKED

Interaction On-site Tracked when an on-site messaging campaign is clicked by a user

On-site

Message

Closed

MOE_ONSITE

_MESSAGE_CLOSED

Interaction On-site Tracked when an on-site messaging campaign is closed by a user
Web Personalization Message Shown

MOE_WEBP

_MESSAGE_SHOWN

Interaction Web Personalization Tracked when a web personalization campaign is shown to a user
Web Personalization Message Clicked

MOE_WEBP_MESSAGE

_CLICKED

Interaction Web Personalization Tracked when a web personalization campaign is clicked by a user
Web Personalization Message Closed

MOE_WEBP_MESSAGE

_CLOSED

Interaction Web Personalization Tracked when a web personalization campaign is closed by a user
SMS Sent SMS_SENT Delivery SMS Tracked when our system sends SMS to a user.
SMS Delivered SMS_DELIVERED Delivery SMS Tracked when our system receives a delivery receipt for the SMS sent to a user.
User Entered Flow USER_ENTERED_FLOW Delivery Flows Tracked when a user falls in the target audience and has qualified for entry in the Flow.
User Exited Flow USER_EXITED_FLOW Delivery Flows Tracked when a user exits from a Stop Cell of the Flow.
User Added To Control Group

MOE_CAMPAIGN

_CONTROL_GROUP

Delivery All Campaigns Tracked when a user is added to a control group
User Removed From Control Group

MOE_USER_REMOVED

_FROM_CONTROL_GROUP

Delivery All Campaigns Tracked when a user is removed from a control group
User Removed From Campaign Due to Control Group

MOE_CAMPAIGN_USER_

REMOVED_DUE

_TO_CONTROL_GROUP

Delivery All Campaigns Tracked when a user is removed from a campaign due to the user being a part of the control group

 

Few things to note for the events that will be sent to Mixpanel -

  • Along with all events sent to Mixpanel, uid will be present by default. This captures the value of the ID which is present in unique user profile in MoEngage. This is also used to match a user in Mixpanel basis the value of the mixpanel_distinct_id.
  • Along with all campaign events, campaign_id, campaign_name, campaign_type, campaign_channel will be present by default
  • For all email campaign events, email_id will be present by default as moe_email_id
  • For all push campaign events, push_id will be present by default as moe_push_id
  • For all sms campaign events, mobile number will be present by default as moe_mobile_number
  • For all campaign events, if the campaign is a part of MoEngage Flows, there will be two additional attributes - parent_flow_id and parent_flow_name.
  • For all campaigns which have multiple variations / locales, there will be additional attributes - variation_id, locale_id, locale_name
  • All events will contain a moengage_user_id by default. This is a moengage internal user identifier and is populated with each event in MoEngage.
  • All events which are generated from the mobile app will contain a moengage_device_id which is a moengage internal identifier.

 

You can also see all the events sent by MoEngage in Mixpanel by filtering basis $source = MOENGAGE

These events will be sent to Mixpanel in near real time and will use the mixpanel distinct_id for mapping user profiles between MoEngage and Mixpanel. Please ensure that you are setting the mixpanel_distinct_id as the unique user id in MoEngage.

 

User Mapping between Mixpanel and MoEngage

When you are exporting cohorts from Mixpanel to MoEngage, all users in your Mixpanel cohort will be attempted to be mapped with unique user profiles in MoEngage. We will be relying on a unique user identifier that will be present across Mixpanel and MoEngage users for mapping. This identifier will also be used when sending campaign events from MoEngage to Mixpanel.

You need to ensure that you are adding an alias for your Mixpanel distinct_id and that the same identifier is used as ID (unique user id) in MoEngage.

For more information on tracking unique user id in MoEngage, please refer the following moengage source specific documentation - 

 

Was this article helpful?
0 out of 0 found this helpful