Bulk delete campaigns, segments, templates and others in the UI
Ability to select and delete multiple campaigns, segments, templates and other objects within the Vero UI.
Trigger Workflows when user enters segment
Workflows can currently only be triggered by "events" (actions users take). This would enable you to trigger workflows when a user enters a segment.
Trigger Workflow based on email events (sent, delivered, opened, clicked)
Trigger Workflows based on email events, not just the events that you trigger manually.
Update user properties based on Workflows
When a user has either completed a Workflow or engaged with a message, it would be useful to trigger an update to specific user properties.
API access to all features in the UI such as campaigns, segments, templates, etc.
Release a full API that provides access to all elements of the UI programmatically.
Add CC to email template
Currently, I can specify "To", "From", and "BCC", but not "CC" in the transactional email template. We'd like our campaign to send an email a third party with our client CC'd. This would enable the third party--who has an existing relationship with our client--to see that our client is aware of the email. When we put both the third party and our client as a list in the "To" recipient, the email is not sent.
Conditional based on triggering event property
We can currently query events by a property being equal to, greater than, etc a hard-defined value set up in the workflow. I think there would be a lot of benefit to allowing workflows to query events based on being equal to, greater than, etc a property from the original triggering event. This, for example, is similar to the existing logic of "has not triggered X event since this workflow started". That's just 'second_event.date > original_event.date` = 0. But open this up for all property types, like 'second_event.category = original_event.category'. This could greatly expand the power of scoped queries, removing the need for them and generalizing them to filter / branch steps instead of a global workflow. This would also solve https://getvero.canny.io/feature-requests/p/scope-by-property-for-filters
Clone (duplicate) a filter rule in a filter node of a workflow
A single filter rule in a filter node of a workflow can often consist of 4 separate inputs: * the type of filter * something to compare to * a comparison operator * a value Setting up a long list of similar filters (for example a workflow may be restricted to a certain set of locales until additional translations have been completed) can be a very menial task this way. If a filter rule had a clone button you could set up a single filter and duplicate it, after which only the value would need to be changed. It's not a big thing but quality of life features like this can have a large impact on a person's experience and prevent a user's frustration with the product. Which is of course completely unrelated to me submitting this request ;)