Mixpanel Community Icon

Join Our Community

Tracking Likes in Mixpanel: Can I Include Multiple IDs in One Event? | Mixpanel Community

Tracking Likes in Mixpanel: Can I Include Multiple IDs in One Event?

·

·

Hello kapa.ai, I want to track when a user likes a post in Mixpanel and be able to analyze:

Who liked the post – using user properties like age and gender (available via distinct_id).
Which post was liked and who created that post – using the post ID and creator's user ID.

Currently, I send the distinct_id as the ID of the user who liked the post. But I also want to include the post ID and creator's user ID in the event so that I can break down reports by post and post creator as well. The question is: Can Mixpanel track an event where I have one distinct_id (liker) and also include additional identifiers (like post ID and creator's user ID) as properties — and then use those additional IDs to break down or filter the event data in reports? In short: Is it possible to include multiple useful IDs in one event, where only one is the distinct_id, and still be able to analyze based on the others?

14 comments

kapa.ai
APP
·
·
Please stand by Paras as I search the knowledge base. I normally take about 15 seconds or so. 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
kapa.ai
APP
·
·
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:Example event structure::**LBKS```LBKS{ "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.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Paras
·
·
kapa.ai If the creator (who received the like) is not mapped to distinct id, would it be possible to get creator name/info from the userbase?
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
If the creator's user ID (who received the like) is included in the event only as a property (e.g., post_creator_id) and not as the distinct_id, you will not be able to automatically join or retrieve the creator's user profile information (such as name, age, etc.) in Mixpanel reports for that event. Mixpanel joins user profile properties to events based on the event's distinct_id. Only the user whose distinct_id is set on the event (the liker, in your case) will have their user properties (like name, age, gender) available for breakdowns and filtering in reports. The creator's user profile properties will not be automatically accessible for breakdowns or enrichment unless the creator's user ID is the distinct_id on the event User Profiles: FAQ | User Profiles Overview.Summary: You can include the creator's user ID as a property (e.g., post_creator_id) and use it for filtering or breakdowns, but you cannot automatically access the creator's user profile info (like name) in reports unless that user is the distinct_id for the event. If you need to display or analyze creator info, you would need to either: - Store the creator's info redundantly as event properties (e.g., include creator_name in the event), or - Use an external lookup (outside Mixpanel) to map creator IDs to their info.This is a limitation of how Mixpanel joins user profiles to events—only via distinct_id User Profiles: FAQ.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Paras
·
·
kapa.ai Same way if Post id is not mapped to distinct id, should i be able to find the post title or other details about the post ?
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
If the post ID is included in the event only as a property (e.g., post_id) and not as the distinct_id, Mixpanel will not automatically join or enrich the event with additional post details (like post title or other metadata) from a separate "post" entity. By default, Mixpanel only joins user profile properties to events via the distinct_id, and group profile properties via a group key. There is no built-in mechanism to join arbitrary event properties (like post_id) to a separate set of post details unless you use a specific Mixpanel feature for this purpose.However, Mixpanel does offer a feature called Lookup Tables. Lookup Tables allow you to map additional properties (such as post title, category, etc.) to an existing event or user property (like post_id). Once you set up a Lookup Table and map it to the post_id property, you can use those additional post details for filtering, breakdowns, and analysis in your reports Data Model: How Mixpanel data is organized | Types of Properties in Mixpanel.Summary: - If you only send post_id as an event property, you cannot automatically access post title or other post details in reports. - To enrich events with post details, use a Lookup Table mapped to post_id. This will allow you to analyze and break down events by post title or other post attributes Types of Properties in Mixpanel.If you do not use Lookup Tables, you would need to redundantly include post details (like post title) as event properties at the time the event is sent.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Paras
·
·
kapa.ai Is it possible to maintain the lookup table automatically or is it a manual process by having to upload CSV in a regular interval ?
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
Yes, it is possible to maintain a Mixpanel Lookup Table automatically—you do not have to rely solely on manual CSV uploads. Mixpanel provides several ways to keep Lookup Tables up to date: - API: You can programmatically replace the contents of a Lookup Table using the Mixpanel API. This allows you to automate updates from your source-of-truth system. For example, you can use a script or integration to push updates as needed, rather than uploading a CSV manually each time "Replace a Lookup Table" API. - Warehouse Connectors: Lookup Tables can also be kept in sync automatically using Mixpanel’s Warehouse Connectors. This enables you to connect your data warehouse and have Mixpanel update the Lookup Table on a recurring basis, without manual intervention Lookup Tables: Enrich ingested data using a CSV | FAQ.Manual CSV uploads are still supported, but automation via API or Warehouse Connectors is recommended for ongoing, regular updates.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Paras
·
·
As the documentation mentioned the lookup tables can created in mixpanel UI only and then be updated via lookups, could you please share the steps to create the lookup table kapa.ai
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
To create a Lookup Table in Mixpanel, you must use the Mixpanel UI. Here are the steps based on the documentation: 1. Prepare your CSV file: - The CSV must have at least two columns: a join key column (e.g., post_id) and one or more property columns (e.g., post_title, category). - The first row should be a header with unique column names. - The first column is reserved for the join key and each value must be unique and non-empty (Create a Lookup Table).2. Go to Lexicon in Mixpanel: - In the Mixpanel UI, navigate to Lexicon. - Click on Import and select Lookup Table.3. Upload your CSV file: - Upload the prepared CSV file. - Only project Owners and Admins can create global Lookup Table mappings via Lexicon (Upload a Lookup Table).4. Map the Lookup Table: - After uploading, map the Lookup Table to an event or user profile property (e.g., map the join key column to the post_id property). - Mixpanel will join the first column of your CSV (the ID) with the selected property.5. Save and use: - Once mapped, the Lookup Table properties become available for use in reports as filters, breakdowns, or in custom properties (Use a Lookup Table).Note: - Free plan users can only upload and map Lookup Tables locally within a report. Growth and Enterprise plan users can create globally persistent mappings via Lexicon. - Lookup Tables can be replaced or updated later via the UI, API, or Warehouse Connectors (FAQ).For more details and examples, see the Mixpanel documentation on Lookup Tables.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.