Avo Feature Requests

Reverse ETLs allow writing of (for example) user properties to target systems without an event taking place—ie. a sync. It would be great to be able to account for these processes and ensure that only approved properties can be written to target systems according to Avo definitions. See attached for how we plan to work around this by creating a pseudo-event called census_sync which represents a daily sync.

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

It would be useful of Inspector would detect significant event volume drops and spikes, for example between versions. And even better if it would alert me!

Be able to add/remove property bundles on event variants

Ability to generate a single Service Account to access Avo's APIs for all workspaces within that organization

If a branch is approved by the admin n weeks ago but not merged by the creator, ping creator and admin

Would like to be able to define event and user properties that have the same name. Use case: When subscribing to a service it makes sense to both track the plan subscribed to on the event as an event property as well as updating a user property with the same value.

On the "View changes" screen for branches, it would be very helpful to be able to "mark as resolved" (collapse) comments. Currently it seems like all that can be done to clean up the view is to delete them entirely.

I currently have no way to change the name of an event variant, the only way to do it is to archive the whole variant and start over

Some times the scope of a branch changes over the course of implementation; for sanity's sake, I'd like the ability to be able to rename a branch to better represent the scope