How to Merge Semantically Similar Event Properties in Analytics Data?

Chris S. · 2026-02-25T12:42:42.654Z

I have 2 events, Preview Template and Start Download. Preview Template has an event property called 'Template Title' and Start Download has an event property called 'Scribe Template Title'. Semantically they're the same event property, but technically different event properties. How can I merge them together?

How to Merge Semantically Similar Event Properties in Analytics Data? | Mixpanel Community

2 comments

· Sorted by Oldest

kapa.ai
APP
·
·
Hi Chris S., 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
·
·
You have two good options, depending on what you want to achieve:
1. Merge the properties in Lexicon (governance-level, changes the canonical name)
If Template Title and Scribe Template Title really are the same concept everywhere, you can merge them in Lexicon so they appear as a single property in analysis:
1.
Go to Lexicon → Properties.
2.
Select both Template Title and Scribe Template Title.
3.
Click Merge.
4.
Choose which one should be the canonical property name (e.g. Template Title).
5.
Confirm Merge.
After this, Mixpanel will treat both raw properties as one merged property in reports. Raw data isn’t changed, but analysis uses the merged property. [Merging data]
2. Create a Custom Property that combines them (analysis-level, non-destructive)
If you’d rather not change naming globally, you can create a Custom Event Property that coalesces the two:
1.
In a report, click the + next to the property search bar and choose Custom Event Property. [Custom properties]
2.
In the formula, use logic like “if Template Title is set, use it, else use Scribe Template Title”.
3.
Name it something like Unified Template Title and Save so it’s reusable.
This gives you a single property to use in breakdowns/filters without touching the underlying schema.
Rule of thumb:
Use Lexicon merge if these should be one property everywhere, long term.
Use a Custom Property if you want a safer, reversible, analysis-only combination.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

kapa.ai
APP
·
·
Hi Chris S., 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
·
·
You have two good options, depending on what you want to achieve:
1. Merge the properties in Lexicon (governance-level, changes the canonical name)
If Template Title and Scribe Template Title really are the same concept everywhere, you can merge them in Lexicon so they appear as a single property in analysis:
1.
Go to Lexicon → Properties.
2.
Select both Template Title and Scribe Template Title.
3.
Click Merge.
4.
Choose which one should be the canonical property name (e.g. Template Title).
5.
Confirm Merge.
After this, Mixpanel will treat both raw properties as one merged property in reports. Raw data isn’t changed, but analysis uses the merged property. [Merging data]
2. Create a Custom Property that combines them (analysis-level, non-destructive)
If you’d rather not change naming globally, you can create a Custom Event Property that coalesces the two:
1.
In a report, click the + next to the property search bar and choose Custom Event Property. [Custom properties]
2.
In the formula, use logic like “if Template Title is set, use it, else use Scribe Template Title”.
3.
Name it something like Unified Template Title and Save so it’s reusable.
This gives you a single property to use in breakdowns/filters without touching the underlying schema.
Rule of thumb:
Use Lexicon merge if these should be one property everywhere, long term.
Use a Custom Property if you want a safer, reversible, analysis-only combination.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

2 comments

1. Merge the properties in Lexicon (governance-level, changes the canonical name)

2. Create a Custom Property that combines them (analysis-level, non-destructive)

1. Merge the properties in Lexicon (governance-level, changes the canonical name)

2. Create a Custom Property that combines them (analysis-level, non-destructive)