Avo Feature Requests

Send workspace notifications to MS Teams

When setting up your Avo workspace for Snowplow it would be helpful to be able to import the Snowplow context objects and include the nested properties that should be in that object. Workaround today: import a property with the name of the Snowplow object you need and of type object import all nested props as standalone properties Then in the Avo UI: Link the respective properties to the object, check the Snowplow object checkbox on the object property and pin the schema field to the relevant Snowplow schema.

With existing events in Avo we probably have enough context to let a LLM conceptualize new tracking definitions. It would be great if you could provide a MCP server to read and also write events / properties.

We would like the base owner as a required reviewer whenever a new variant is created (as the subject matter expert for that type of tracking consult to the engineering team - as there are typically a bunch of questions about the properties included and what they are, etc)

To help communicating what string constraint applies in which situation, it would be helpful to add a description to each string constraint. Current workaround is documenting constraint descriptions in the property description.

Being able to annotate for a specific event what the property description is more specifically would be helpful. For example: Property: "id" Global description: "contains immutable non-localized strings identifying the object" Local description for "Item Added": "the matchname of the item added"

Property values are currently truncated in Metrics (e.g. when it comes to allowed values for filters). It would be much easier to see the full parameters of the metric definition if the property values would wrap rather than truncate.

Sometimes when the base event is updated the changes only apply to a subset of the variants of the event. It's no problem if the variants are few to go through each of them and modify. But when the variant are many, the job to update all of them becomes very tedious and error prone. So it would be helpful to be able to pick which, if any, variants the change applies to.

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.