Add a break down by event property in User Paths visualisation

[dansimau]

Is your feature request related to a problem?

• Use case: Visualising user journeys on mobile
• Currently using Mixpanel, trying to migrate to PostHog
• Working on a mobile app built in React Native, using React Navigation
• Working with an existing custom event called navigation.navigated with a property routeName
• Trying to use "User Paths" in PostHog (similar to "Flow Insights" in Mixpanel)
• When I use User Paths in PostHog, I can see paths between my navigation.navigated events but I can't see the screen/route names and there is no ability to break down events by property value

Screenshot comparison

Mixpanel Flow Insight:

PostHog User Path:

Describe the solution you'd like

• Ability to add property breakdowns for custom events in User Paths

Describe alternatives you've considered

• Using built in "Screen views" feature
  • Screen views doesn't seem to be supported on iOS and/or React Native
• Instrumenting a new event with the screen name in the event name
  • This could work, but not on historical data
  • Pretty clunky, we'd have to stop sending the existing event which will break backwards compatibility or double emit for a single event which could have problems in the path analysis (would have to exclude 1 of the events)

[benjackwhite]

Hello!

Thanks for the issue. I've actually been working hard on a reworked React Native library that is more React "Native" which has more features as well as fits in nicely to something like React Native navigation. It will be released today as version 2.0.0 so perhaps that is something you can try.

For the current RN library, screens isn't perfect as it RN has a lot of abstractions away from the underlying navigation system. You can manually track a screen view which would allow you to use the "screen events" more reliably based on your own naming from react-native-navigation (this is what V2 does).

For example this is from me testing it on my personal project using the .screen() function:

As you say though it would be great to be able to specify an event sub-property to create paths based on any events. Should be doable...