The inSided x Mixpanel integration is in beta. Currently, additional configuration may be required from inSided, e.g. to ensure compatibility between Mixpanel tracking and your cookie management system for end users.
The inSided x Mixpanel integration helps you to track end user behaviour on your community alongside your product usage data in Mixpanel, helping you to understand the relationship between community activity and product usage.
How to set up the inSided x Mixpanel integration
The Mixpanel integration is not yet self-service. Contact firstname.lastname@example.org if you’d like to set up the integration. You’ll need to provide us with your the project token for the Mixpanel project where you’d like to send events.
What events and properties are sent to Mixpanel?
We send the following events to Mixpanel:
- [Community] User Registered
- [Community] User Visited
- [Community] Page Viewed
- [Community] Topic Created
- [Community] Reply Created
- [Community] Question Answered
- [Community] Post Liked
- [Community] Homepage Element Clicked
- [Community] Helpfulness Voted
Please see the attached file ‘inSided Mixpanel Integration event spec’ for a detailed breakdown of events and properties, including more detail about what triggers each event.
Note: the super properties for each event (e.g. user role/rank) always reflect the user who triggers the event. E.g. for [Community] Question Answered, the super properties reflect the user who marked an answer.
What user profile data is synced to Mixpanel and when?
We sync the following people properties to Mixpanel:
- [Community] User Custom Roles
- [Community] User Email
- [Community] User Name
- [Community] User Primary Role
- [Community] User Rank
If there have been changes to these people properties on inSided, then the next time the user visits the community, the Mixpanel profiles will be updated with the latest values.
Mixpanel Integration Cookie Behaviour
Visitors (users who are not logged in)
- When the Mixpanel integration is enabled for a community and a user first visits the community, then a Mixpanel cookie is set for them.
- The cookie stores a Distinct ID representing the user as a random unique hash. The cookie also stores metadata about the user such as the browser the user uses or the region where the user is from.
- When a tracking event is sent to Mixpanel, the Distinct ID and metadata are read from the cookie and appended to the tracking event.
- Sending the Distinct ID ensures that tracking events from the same user can be aggregated.
- Mixpanel cookies are stored for anonymous users as well as for registered users.
When a user registers, logs in, or logs out of inSided
- When a user registers or logs in, the random Distinct ID is updated in the format of communityId:userId e.g. inspired-en:2001.
- All subsequent tracking events have the new Distinct ID appended. Mixpanel uses an internal lookup table so that events with the initial random Distinct ID can be aggregated with events with the new Distinct ID.
- When a user logs out, the Distinct ID is updated to a new random unique hash, so that a new anonymous user can be tracked.
If you’re using SSO on your community, then users will be identified by their SSO User Id when they authenticate on the community.
Using SSO means your Community User Profile will be the same as any existing User Profiles you have for that user in Mixpanel, which means that there is a matching distinct_id for both profiles.