How to Merge Differently Named Properties for Unified Breakdown in Event Analysis

Ashton C. · 2026-02-15T23:50:07.076Z

If I want a breakdown by a property but the property is named differently in different events, please write the formula so i can use it to merge properties and breakdown by the new event

How to Merge Differently Named Properties for Unified Breakdown in Event Analysis | Mixpanel Community

2 comments

· Sorted by Oldest

kapa.ai
APP
·
·
Hi Ashton C., 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
·
·
Mixpanel doesn’t document a way to rename/alias multiple raw properties inside a single custom-property formula (e.g. coalesce(propA, propB)), so I can’t give you a guaranteed-working formula pattern from the sources. The documented ways to “merge” differently named properties for use in breakdowns are:
1. Merge properties in Lexicon (governance approach)
If property_A and property_B are really the same concept across events: 1. Go to Lexicon → Properties. 2. Select property_A and property_B. 3. Click Merge. 4. Choose which name should be the canonical merged property. 5. Save.After this, you can break down by the merged property name and it will cover both originals. [Merging data]This doesn’t use a formula; it changes how Mixpanel treats those properties project‑wide.
2. Use a Custom Event (if the issue is event names, not properties)
If the events are named differently but share the same property name, you can merge the events via a Custom Event, then break down that custom event by the shared property: 1. Create a Custom Event that includes both raw events. 2. Use that custom event in your report. 3. Apply a breakdown by the shared property. [Custom events]
3. Borrowed Properties (if the property is missing on some events)
If one event has property_X and another event doesn’t, you can “borrow” property_X from the prior event so that the later event appears to have it, then break down by that borrowed property: 1. Create a Custom Event Property. 2. Add a Borrowed Property that pulls property_X from the source event. 3. Use that custom property as the breakdown. [Borrowed properties]---If you specifically need a formula expression that aliases multiple differently named properties into one, the knowledge sources do not show an example or confirm that pattern, so I can’t provide a reliable formula snippet.
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.

kapa.ai
APP
·
·
Hi Ashton C., 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
·
·
Mixpanel doesn’t document a way to rename/alias multiple raw properties inside a single custom-property formula (e.g. coalesce(propA, propB)), so I can’t give you a guaranteed-working formula pattern from the sources. The documented ways to “merge” differently named properties for use in breakdowns are:
1. Merge properties in Lexicon (governance approach)
If property_A and property_B are really the same concept across events: 1. Go to Lexicon → Properties. 2. Select property_A and property_B. 3. Click Merge. 4. Choose which name should be the canonical merged property. 5. Save.After this, you can break down by the merged property name and it will cover both originals. [Merging data]This doesn’t use a formula; it changes how Mixpanel treats those properties project‑wide.
2. Use a Custom Event (if the issue is event names, not properties)
If the events are named differently but share the same property name, you can merge the events via a Custom Event, then break down that custom event by the shared property: 1. Create a Custom Event that includes both raw events. 2. Use that custom event in your report. 3. Apply a breakdown by the shared property. [Custom events]
3. Borrowed Properties (if the property is missing on some events)
If one event has property_X and another event doesn’t, you can “borrow” property_X from the prior event so that the later event appears to have it, then break down by that borrowed property: 1. Create a Custom Event Property. 2. Add a Borrowed Property that pulls property_X from the source event. 3. Use that custom property as the breakdown. [Borrowed properties]---If you specifically need a formula expression that aliases multiple differently named properties into one, the knowledge sources do not show an example or confirm that pattern, so I can’t provide a reliable formula snippet.
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.

2 comments

1. Merge properties in Lexicon (governance approach)

2. Use a Custom Event (if the issue is event names, not properties)

3. Borrowed Properties (if the property is missing on some events)

1. Merge properties in Lexicon (governance approach)

2. Use a Custom Event (if the issue is event names, not properties)

3. Borrowed Properties (if the property is missing on some events)