Mixpanel Cloud Mode Integration

After you have successfully instrumented Mixpanel as a destination in RudderStack, follow this guide to correctly send your events to Mixpanel in cloud mode.

Find the open source transformer code for this destination in the GitHub repository.

Identify

You can use the identify call to create or update a user in Mixpanel.

Mixpanel needs an identifier to uniquely identify a user. If you pass userId and anonymousId along with the Mixpanel API Secret (in the dashboard settings), then RudderStack first makes an identify call to Mixpanel using the userId and the traits. RudderStack then passes the userId and anonymousId via Mixpanel’s Merge Identities feature, so that the two identifiers are glued to a single user profile.

Note the following when sending events to Mixpanel in cloud mode:

• You can only create a new user in Mixpanel using identify events if you have selected the Simplified ID Merge dashboard setting. To perform identity merging, you need to use the track or page/screen calls.
• When sending events to Mixpanel with Simplified ID Merge, RudderStack recommends passing deviceId generated by the Mixpanel SDK as anonymousId in the RudderStack server-side calls to merge two profiles together successfully. For more information, see Mixpanel User Profiles documentation.

A sample identify call is as shown:

rudderanalytics.identify("12345", {
  firstname: "Alex",
  city: "New Orleans",
  country: "USA",
  phone: "8005550100",
  email: "alex@example.com"
})

You can prevent the $last_seen attribute getting updated with incorrect times by setting active to false in the context object, as shown in the following snippet:

rudderanalytics.identify("12345", {
  firstname: "Alex",
  city: "New Orleans",
  country: "USA"
}, {
  context: {
    active: false
  }
})

Setting active to false sets Mixpanel’s $ignore_time attribute to true. This way, you can bypass the “Last Seen” date property.

Property mappings

When sending events in cloud mode, RudderStack maps the following identify fields to the Mixpanel fields before sending them over Mixpanel’s HTTP API.

In addition to the above properties, RudderStack also maps the below properties to specific Mixpanel fields depending on the platform:

Properties to set only once

RudderStack lets you set the identify traits as Mixpanel properties whose values you do not want to change at the user profile level, that is, Mixpanel will not overwrite the existing property values. See Mixpanel documentation for more information on this feature.

To use this feature, add the identify traits in the Properties to set only once setting.

RudderStack expects the traits specified in the above field to be present in the message.traits or message.context.traits (message.traits has higher precedence) object within the identify event.

For example, if your identify event contains the following and you specify address.city in the Properties to set only once field:

"traits": {
  "address": {
    "city": "London"
  }
}

...

"context": {
  "traits": {
    "address": {
      "city": "Berlin"
    }
  }
}

Then, RudderStack maps city as London as the traits object gets precedence over context.traits.

Reserved Mixpanel properties

Mixpanel has some reserved properties:

• $first_name
• $last_name
• $name
• $username
• $created
• $email
• $phone
• $avatar
• $city
• $country_code
• $region
• $unsubscribed

You should not create custom properties that begin with a $ sign.

Deleting a user

You can delete a user in Mixpanel using the Suppression with Delete regulation of RudderStack’s User Suppression API.

To delete a user, you must specify their userId in the event. Additionally, you can specify a custom identifier (optional) in the event.

A sample regulation request body for deleting a user in Mixpanel is shown below:

{
  "regulationType": "suppress_with_delete",
  "destinationIds": [
    "2FIKkByqn37FhzczP23eZmURciA"
  ],
  "users": [{
    "userId": "1hKOmRA4GRlm",
    "<customKey>": "<customValue>"
  }]
}

RudderStack internally uses the deletion API specified in the User Deletion dashboard setting. For more information on these deletion APIs, see Connection settings.

To see the deletion requests created by RudderStack using the Delete Profile and Associated Events option, log in to your Mixpanel dashboard and navigate to Organization Settings > Data & Privacy.

Deletion requests created using the Delete Profile API are not shown in this dashboard.

Track

To track user events, use the track method with the event name and the associated properties.

When you select Simplified ID Merge in the Identity Merge dashboard setting, RudderStack sets the event’s userId and anonymousId using Mixpanel’s Simplified ID Merge API so that the two identifiers are glued to a single user profile.

A sample track call is as shown:

rudderanalytics.track("track event", {
    test_prop1: 50,
    test_prop2: "prop_value"
});

Track revenue

Mixpanel lets you track revenue events. If you send revenue as a property in your track event, RudderStack tracks it as a revenue event.

Revenue tracking is done with a distinct_id (userId that you provide in your identify call; if userId is not present then it will be associated with an anonymousId.)

A sample revenue track call is as shown:

rudderanalytics.track("Purchase", {
  revenue: 100,
  currency: "USD"
});

Track charge

If Use Mixpanel People setting is toggled on in your RudderStack dashboard and you include revenue as an event property, RudderStack will track a charge for the current user.

Property mappings

Page

RudderStack passes all page properties that you provide via the page call to Mixpanel, along with the other default properties. It sets the event name as Page for a page call and Screen for a screen call.

When you select Simplified ID Merge in the Identity Merge dashboard setting, RudderStack sets the event’s userId and anonymousId using Mixpanel’s Simplified ID Merge API so that the two identifiers are glued to a single user profile.

A sample page call is shown below:

rudderanalytics.page();

Property mappings

Screen

The screen method lets you record whenever a user sees their mobile screen along with any optional properties about the viewed screen.

A sample screen call is shown below:

[[RSClient sharedInstance] screen:@"Sample Screen Name" properties:@{@"prop_key" : @"prop_value"}];

Alias

The alias call lets you associate multiple identities of a known user.

The alias call is deprecated with the Simplified ID Merge dashboard setting.

A sample alias call is as shown:

analytics.alias('userId', `previousId`);

Group

The group call lets you link an identified user with a group such as a company, organization, or an account, and record any traits associated with that group, for example, company name, number of employees, etc. For more information on how the group call works in Mixpanel, see Mixpanel’s Group Analytics documentation.

RudderStack lets you record the custom traits associated with a user group and send this information to Mixpanel.

A sample group call is shown below:

rudderanalytics.group(
  "sample_group_id", {
    name: "Tech group",
    industry: "Technology",
    employees: 100,
  }
);

Group key

You can create group keys in the Mixpanel project settings, which act as the group identifiers in Mixpanel. To successfully send a group call to Mixpanel, you must specify at least one group key in the Group Key RudderStack dashboard setting:

Note the following:

• If you map the groupId as a group key, RudderStack looks up its value in the following priority order:
  1. In message.groupId
  2. In message.traits.groupId
• If you map any other field as a group key, RudderStack looks up its value in message.traits.groupKey.
• You can specify multiple values for a group key and send them in an array in the group event payload.

Send historic events

Mixpanel supports importing historical event data. However, note that the event timestamp should be within the last 5 years. Mixpanel rejects any data older than this duration. To send historic events, provide the timestamp in the timestamp field of the message. RudderStack will then send the event with the same timestamp to Mixpanel.

Mixpanel special traits

The following table lists all properties that RudderStack sends to Mixpanel as special traits:

Send UTM parameters to Mixpanel

This section is applicable for track, page, and screen events.

RudderStack maps the following keys (derived from the event’s context.campaign object) to the Mixpanel standard UTM parameters:

Any contextual fields apart from the ones mentioned above are sent as utm_{key} to Mixpanel. An example is shown below:

{
  "context": {
    "campaign": {
      "name": "test_name",
      "source": "test_source",
      "medium": "test_mediun",
      "content": "test_content",
      "term": "test_term",
      "keyword": "test_keyword"
    }
  }
}

utm_campaign
utm_source
utm_medium
utm_content
utm_term
utm_keyword

In the above example, RudderStack sends utm_keyword as a custom UTM parameter to Mixpanel.

Increment properties in Mixpanel People

To increment properties in Mixpanel People, you can add them in the Properties to Increment in People dashboard setting.

RudderStack calls Mixpanel’s increment when you attach a number to the specified property. For example, 'items purchased': 5.

FAQ

Can I pass null and empty values for the properties?

Yes, RudderStack supports passing empty or null values for the properties sent to Mixpanel.

Why am I getting the ‘Request Header Fields Too Large’ error?

Mixpanel imposes certain limitations on its API requests such as:

• Any GET request URL above 19K characters (around 19 KB+) is blocked.
• The header size more than 15KB is not allowed.
• The body of the request more than 20MB is not allowed.
• Each event can have up to 255 event properties.

If your requests are larger than the above-mentioned limits, you will get a ‘Request Header Fields Too Large’ error.

See Mixpanel’s Community FAQ for more information.

Questions? Contact us by email or on Slack