Mixpanel Community Icon

Join Our Community

How to Inherit Parameters in Mixpanel Custom Events from SDK Events

·

·

Given: A view_page event is set up via the Client-Side SDK, which triggers on every page load and sends Mixpanel's default parameters such as $distinct_id, $device_id, and $current_url. When: In the Mixpanel interface's Insight Report, when selecting a Metric, the "Custom Event" feature is used to define a new event view_analytics_report based on the condition that the event view_page has a $current_url containing /dashboard/analytics OR /dashboard/organicTraffic. (Note: This event is not set up through the Client-Side SDK but is created post-processing within Mixpanel.) Then: When checking the view_analytics_report Custom Event in Mixpanel's Lexicon feature, it does not inherit the event parameters from the original view_page event, such as $distinct_id, $device_id, and $current_url. Question: How can the post-processed Custom Event view_analytics_report in Mixpanel also inherit the event properties and their values such as $distinct_id, $device_id, and $current_url from the orgianl view_page event triggered by the Client-Side SDK?

5 comments

kapa.ai
APP
·
·
Hi Sharon L., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
kapa.ai
APP
·
·
Based on the information provided in the knowledge sources, I can answer your question about inheriting event properties for custom events in Mixpanel.Custom events in Mixpanel, like the one you've created called "view_analytics_report", do indeed inherit the properties from the original events they are based on. This includes default properties like $distinct_id, $device_id, and $current_url.According to the Custom Events documentation, custom events are virtual events created from one or more existing events, optionally filtered by a set of properties. When you create a custom event, it should automatically include all the properties of the original event(s) it's based on.However, if you're not seeing these properties in Lexicon, it's likely due to how Lexicon displays information about custom events. Lexicon may not show inherited properties for custom events in the same way it does for regular events.To confirm that your custom event is indeed inheriting the properties from the original "view_page" event, you can try the following: 1. Use the custom event "view_analytics_report" in an Insights report. 2. Add a breakdown by one of the properties you expect to see (e.g., $current_url). 3. If the breakdown works and shows data, it confirms that the property is present on the custom event.If you still don't see the expected properties, you may want to check if there are any data governance settings in place that might be hiding certain properties.It's also worth noting that custom events are computed at query time, so they should always reflect the most up-to-date data and properties from the original events they're based on.If you continue to experience issues with property inheritance for your custom event, I recommend reaching out to Mixpanel's support team for further assistance, as this behavior is not expected based on the information provided in the knowledge sources.
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.
Sharon L.
·
·
kapa.ai Do custom events inherit both custom properties such as "plan" and Mixpanel/default properties from the original events?
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
Yes, custom events in Mixpanel inherit both custom properties (like "plan") and Mixpanel's default properties from the original events they are based on.According to the Custom Events documentation, custom events are virtual events created from one or more existing events, and they include all the properties of the original event(s) they're based on. This means that both custom properties you've defined (such as "plan") and Mixpanel's default properties (like $distinct_id, $device_id, $current_url, etc.) should be inherited by the custom event.Mixpanel's default properties, also known as automatically collected properties, are described in the Default Properties documentation. These include various event and user properties that Mixpanel collects automatically, depending on the SDK and platform you're using.It's important to note that while these properties are inherited, they might not always be visible in the Lexicon feature of Mixpanel. However, you should be able to use both custom and default properties when creating reports or analyses based on your custom events.To verify that your custom event has inherited both types of properties, you can: 1. Use the custom event in an Insights report. 2. Try to break down the data by both your custom property (e.g., "plan") and a Mixpanel default property (e.g., $current_url). 3. If the breakdowns work and show data, it confirms that both types of properties are present on the custom event.If you encounter any issues with property inheritance, it's recommended to check your data governance settings or contact Mixpanel support for further assistance.
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.