Currently, we can only block the entire event in itself or the property name alone and not by a specific value for that property.
100% necessary to have more granular control. The current implementation seems to assume that all logical events are split as discrete events which isn’t true for lots of cases. Often it’s better to have common event names and differentiate meaning based on properties.
so in order to block chatty or defunct types of those common events we need to be able to block and filter on event names with properties values.
And if not possible for all property, then at least for “Sources”, “Platform and “Version”
Yes!! I tried to do this today after yesterday’s data governance webinar and was unable to do so. The overall event is fine, but properties for a given period of time were not implemented properly and I therefore want to omit
Since Amplitude is event volume pricing, they are not incentivized to ship this feature. But we, customers, need it
Following up here to let folks know that this is possible with Amplitude! See the screenshot below to understand how you would block data with specific event property attributes.
Hi, I’d like to request a feature: it would be really helpful to have the ability to shuffle or reorder properties within an event, especially when grouping. Right now, adjusting the order of grouped outputs is quite cumbersome.
When changing a property value, because we often have complex and long values, we paste the exact value in the search bar. However the matching value will appear at the very top but all other values will remain, which makes the search complex and we lose a few seconds each time Here is a loom to show my point Thanks !!
I am creating a template for our experiments dashboards I would like it to be as self serve as possible, making stakeholders changing the fewest things as possible. They have the ability to change the properties values but NOT the exposure key, which is a problem as they have to go in every chart and change the key, which…
Hey everyone, I wanted to share a few lessons I’ve learned running A/B tests using Amplitude Experiment and open up a conversation around how others are approaching it in real-world settings. We’ve been using Amplitude for product analytics for a while, but recently moved some of our experimentation flows over to Amplitude…
