You can surface a nested value via a Custom Property, but you cannot make Mixpanel treat that Custom Property as the same underlying property as the top‑level one just by giving it the same name.
Key points from the docs:
Custom Properties let you compute new properties from existing ones (including objects) and then use them like normal properties in filters/breakdowns/funnels. [Custom properties; Common use cases]
You can query into objects/lists with functions (the docs show examples of querying a list and say “the same syntax works with objects”), so you can define a Custom Event Property that pulls out your nested ID. [Common use cases]
However, renaming or display‑renaming does not change the raw property name Mixpanel uses internally; display names are just UI labels. [Renaming properties]
Lexicon “merge properties” lets you merge multiple raw properties into one logical property, but that operates on ingested properties, not on Custom Properties. [Merging data]
So in practice:
- 1.
Create a Custom Event Property that extracts the nested ID from the object.
- 2.
Use that Custom Property as the breakdown/filter in your funnel (it will behave like a normal property there).
- 3.
But Mixpanel will still see:
Property A = your original top‑level property on some events.
Property B = your new Custom Property on others.
They are separate; simply giving B the same label as A doesn’t make the Funnel “recognize them as the same property.”
If you need them to truly be one canonical property everywhere (e.g., for “hold property constant” across all steps), the docs don’t show a way to do that purely via Custom Properties; you’d need to normalize at ingestion (or use Lexicon property merge on real properties, not on a Custom Property). [Hold property constant; Merging data]
The knowledge sources don’t explicitly document using a Custom Property as the same property across steps for “hold property constant,” so I can’t confirm that specific behavior.
