Avo Feature Requests

I'd like to be able to update user properties in a specific Event Variant, without updating them on the base event.

Would love this feature similar to properties merged option. Why? Duplicates happen when PMs and Analysts are doing a CSV import and its time consuming for them to find the duplicates once in Avo and takes time to delete/archive as there is no merge option.

When Snowplow is used as destination, the event needs to point to the Snowplow schema. This can best be done with a pinned property. It would be nice to see in the AVO interface when there is something wrong with this property, or if it is not pinned or pinned to an inconsistant value (i.e. when you duplicate an event the schema property is still pinned to the source event) Now we get feedback from the devs that there is something wrong with the schema; would be great if there is a check on this schema property when building a branch or merging it to main

It would be great to have the ability to preview the contents of a complex property, like an array of objects. Seeing the exact contents of such properties would make it easier to confirm that the app sends the correct telemetry payload.

Currently, there is no way to automate the tracking plan release. This would open up new possibilities, increase product flexibility, and would aid adoption as there is less friction in introducing Avo to certain workflows/use cases.

My usual workflow for adding screenshots to tools, would be to just have the screenshot in my clipboard and then paste it wherever I need it. It would be nice if triggers would allow to add images from the clipboard.

Ensure to publish with the correct version increment. Currently, manual intervention is required to move a Snowplow release to production. After a publish, update Avo's pinned Snowplow schema version to match the new release. Currently, manual updating is necessary to keep Avo in sync with Snowplow's production updates.

Teams are asking for improved sorting/ordering of events, properties and categories. We've gotten request to be able to order/sort the following items: Order categories Order events within categories Order properties within events In the following way: Alphabetically Manually

A common error are missing schema keys for snowplow entities. It would be great, if the audit could check for the existence of the schema as well as for the pinned value.

Currently Avo allows for standard casing conventions to be enforced when naming event and properties, and custom casing conventions for events. Some teams do however have custom casing for property names, for example snake_case with two underscores differentiating between parts of a sentence.