Avo Feature Requests

To make the translation of the tracking plan changes into code changes more precise and intuative, it would be helpful to be able to tailor the pseudocode snippets to the implementation methods teams are using. For example if the web source is implemented with Google Tag manager, then the pseudocode would be on the GTM format, using the datalayer.push() method.

Make it easier to add and drop users in Avo.

Be able to add/remove property bundles on event variants

It would be really useful for admins to know if there have been any failures in publishing integrations. Whether by email or slack. Currently, if there is a failure with a publishing integration, we are only alerted if we check the Publishing page, or if an end user sees something.

Make it possible to copy a single trigger across multiple events and be able to see which events are attached to said trigger.

The output JSON file from the publishing Webhook, while exhaustive, is not compatible with the GCP/BigQuery import for creating tables, making it harder to create custom logic which tries validating collected data against the AVO Tracking plan. Suggest one or more of the following: Ability to select which fields to output as part of the JSON Export (Thus making it possible to output a flattened JSON file) Set up a BQ-compatible version of the JSON Export using Newline Delimited JSON

Developers migrating their swift codebases to swift 6 will go through a process of marking which types / functions are Sendable (i.e. thread safe). The generated Avo code has no annotations so it is not clear which (if any) types are thread safe It would be very useful to have the generated code updated. Ideally to be sendable but if that is not possible annotated to indicate which parts are and are not

In order to easily share an Avo branch and it's context with collegues, it would be great if there was a ticketing integration with tools like Jira.

Let's say I have created this great event property with a description and a bunch of constraints – but then I realise it should be a user property. It would be great if I could just convert it to a user property without having to define it from the scratch.

Can duplicating an event properly clone property presences please? I duplicate an event and all the property presences are wrong, and I have to audit every single one and correct them.