Allow further filtering of custom props

[metmarkosaric]

"Custom Goals.. clicking on a “Breakdown by" prop value -> it activates the filter for this value.

Now I would have expected to still see the other “Breakdown by” categories and be able to filter down further and get insights on how one “Breakdown by” category affects my other “Breakdown by” categories for this goal.

I would really love to see this!"

Update: You can now segment your audience by multiple custom properties. Just keep selecting additional custom properties in your dashboard as you’re filtering.

You can use the filter button on the top right of the dashboard to do the same too. There we’ve also added the “contains” option for even more powerful segmenting.

[ukutaht]

Good point. Seems like an arbitrary limitation in the UI currently.

Good use-case example is elementary.io's dashboard. It would make sense to want to see conversions of the Payment event filtered by Action=Complete and to then see a breakdown of the Amount.

[neuromusic]

+1 to this request. (see chanzuckerberg/napari-hub#76 (comment) for our use case)

[ukutaht]

Cheers. Clickhouse is working hard to add better support for semi-structured data: Their roadmap for 2021.

The Map datatype which we need is currently in experimental mode but I hope to see it stable soon. Once it is, I'm planning to migrate our custom prop data to the new datatype which offers more flexibility.

[UnamedRus]

Experimental status of map datatype was removed in that pr ClickHouse/ClickHouse#25773 .
So starting from 21.8, it's not experimental.

But internally it's still 2 arrays, so performance different from two key value arrays shoudn't be big.

[ukutaht]

Sweet. I'll probably get around to upgrading in the coming months after it reaches the Altinity stable channel: https://docs.altinity.com/altinitystablerelease/releasenotes/. Then I can start playing around with Maps

[Wolfkhan66]

Any update on this? More and more this is becoming an urgent requirement and we now starting to look at alternatives to plausible to fulfill this need

[ukutaht]

Current status is that we are waiting for JSON datatype support for Clickhouse which is supposed to be coming this year. The problem with Map is that it is must be supplied with a static type pair (e.g. Map(String, UInt64)) so it cannot handle mixed types which is an important aspect of custom props.

[dbstraight]

Is this potentially coming in 2023?

[earthboundkid]

It looks like the blocker from Clickhouse got resolved https://docs.altinity.com/releasenotes/altinity-stable-release-notes/22.8/altinity-stable-22.8.13/. How is this going on the Plausible side @ukutaht? I would like to use Plausible instead of going to GA4 (yuck), but the ability to drill down into custom props is a requirement for us, so we can't switch over without it.

[ukutaht]

How is this going on the Plausible side @ukutaht?

I don't want to make any promises. We are planning to work on the Clickhouse schema later this year so there's a good chance we will migrate the custom props over to the Map datatype as well.

[metmarkosaric]

Update: You can now segment your audience by multiple custom properties. Just keep selecting additional custom properties in your dashboard as you’re filtering.

You can use the filter button on the top right of the dashboard to do the same too. There we’ve also added the “contains” option for even more powerful segmenting.

[mir1198yusuf]

@metmarkosaric I am not able to select 2nd custom property filter if one exists. when i do, it replaces first custom property filter with new one .

In above image, I want to add a filter for new property is_admin, how can i do that ?