Yes, you can absolutely include multiple useful IDs as properties in a single Mixpanel event, even though only one will be used as the distinct_id (the user who liked the post). Mixpanel’s data model is designed for this: you can add any number of custom properties to an event, such as post ID and the creator’s user ID, alongside the distinct_id of the user performing the action.
How this works:
- The event (e.g., "Post Liked") should have the liker’s user ID as the distinct_id.
- You can add additional properties like post_id and post_creator_id to the event.
- In Mixpanel reports, you can filter, break down, and analyze events by any property you include, not just distinct_id. For example, you can break down "Post Liked" events by post_id to see which posts are most liked, or by post_creator_id to analyze which creators get the most likes.
- You can also use user properties (like age and gender) for the user who performed the like, since those are tied to the distinct_id.
Example event structure:
{
"event": "Post Liked",
"properties": {
"distinct_id": "liker_user_id_123",
"post_id": "post_456",
"post_creator_id": "creator_user_id_789",
"token": "YOUR_PROJECT_TOKEN"
}
}
Analysis in Mixpanel:
- You can break down or filter "Post Liked" events by post_id or post_creator_id in your reports.
- You can also analyze by user properties (age, gender) of the liker, since those are associated with the distinct_id.
This approach is standard in Mixpanel and is supported by the platform’s event and property model. You do not need to use multiple distinct_ids in a single event; just include the other IDs as properties for flexible analysis later on Events: Capture behaviors and actions | Anatomy of an Event.
If you want to analyze at the group level (e.g., by company or team), Mixpanel also supports Group Analytics, but for your use case (post and creator IDs), event properties are the right solution Build Your Tracking Strategy.
Summary:
Yes, you can include multiple IDs as properties in a Mixpanel event and analyze your data by those properties in reports, even though only one is the distinct_id.
