Event/source dependent allow lists for properties
complete
Jared Torre
We use common event properties across a wide range of events because only select number of properties are by default visible in our analytics reporting platform. For example, we have a property called ui.location, which is meant to contain information about the location in the UI where the user performed that action. Depending on what the event is capturing (adding text to their graphic, opening a settings dialog, etc), the allow list will be very different. This causes confusion to engineers if an allow list is defined for a property on an event that is not relevant for the features they are developing.
We'd also like to have this allow list dependent on source since we use sources to differentiate apps, which have very different designs and feature sets, but all use the same properties that are compatible with our analytics reporting platform.
Solvi Logason
complete
Thank you for the feature request Jared Torre!
It sounds like what you're looking for here are event-specific and source-specific allowed values, which are already available in Avo today. You can specify on which events, event variants, and sources each value should be allowed.
More in the docs here: https://www.avo.app/docs/data-design/avo-tracking-plan/properties#enumeration-of-allowed-string-values
Let me know if this is not what you're looking for here!