Segments in Vero 2.0

Vero 2.0 currently does not support the same ability to create segments of users as Vero 1.0, but that is soon to change. Not only are we bringing the full set of segmentation features to Vero 2.0, we’re also making some significant updates, with new conditions, improved UX and a some backend speed improvements to boot.

Branch Node in Journeys (Vero 2.0)

In Vero 1.0 Workflows we support Branch nodes, which act as 'if/else' statements that are processed at certain points of the customer's journey and evaluate and take the user down one of two paths when they reach the node. We could not support this functionality in Vero 2.0 Journeys due to having no ability to process conditional logic or segmentation. Branch nodes in Vero 1.0 have most of the same conditions as segments, so it made sense to build segmentation first. A new and improved Segmentation feature in Vero 2.0 is well underway, branching will follow shortly after.

Webhooks in Vero 2.0

Update the Vero 2.0 UI to allow adding and editing webhooks.

Profiles in Vero 2.0

We’re bringing fully editable profiles to Vero 2.0. Previously labeled ‘Subscriptions’, we’re updating the UI to include the same detailed profiles from Vero 1.0 into Vero 2.0, giving you full visibility to all the data stored about a user, as well as the ability to edit and see all user activity in one place. This is a crucial update that allows us to bring an entirely new Segmentation experience to Vero 2.0 later this year.

Add a webhook for when a user's preferences have changed

For the Beta Preference feature, it would be great if there was a dedicated webhook for these changes. As of right now, only the user_updated webhook contains this data, but it’s extremely noisy because it gets triggered so frequently.

Add the ability to toggle whether a newsletter allows duplicates to be sent

Some customers need to maintain multiple profiles with an identical email address in their projects. However, there are times when they want to send a newsletter that will only send once per email, regardless of how many profiles with that email address are in the newsletter audience. Adding the ability to toggle this on/off on a per newsletter basis would be an ideal solution.

Reporting: improve project-level reporting

Help provide insight on the performance of Vero and the improvements driven by messaging across the business. Metrics that might be included: Total reach. Overall customer growth. Over unsubscribed customers growth. Metrics for the above vs. hold out group (who receives no messages). Insights into deliverability and movements. How often are customers messaged? How does this change over time? Compare a few groups/segments.

A/B testing: create a global hold-out group

Ability to define a percentage of users that do not receive any campaigns at all and report on the performance of this group vs. other groups.

User role: Customer support access to customer records but not campaigns

User role for customer support agents to search and see profile history but not campaigns.

A/B testing: workflow improvements

Including: Ability to “pick a winner” and Vero automatically “handles” the other branches. Keep a history of what was there previously (see @Add versions to Workflows, Templates, etc. as this is related).

Reporting: conversion reports improvements

Report on 1, 7 and 30 day windows. Report for multiple events. Ideally even “after the fact”.

User role: Edit but not publish

Users that can edit campaigns but not publish changes. Relies on @Add versions to Workflows, Templates, etc.

"Smart message" that automatically attempts different channels

When creating a message, specify content for more than one channel, e.g. email, SMS and iOS/Android push all at once. Set rules globally or at the campaign-level used to control which message is sent first and when other channels are attempted. Look at logic to optimise this per-recipient.

Ability to "validate" Campaign workflow object in new Campaigns API

An endpoint that can be used to validate a Campaign workflow object is valid prior to POST/PUT-ing an update. The use case is to run a test suit against multiple campaigns and only proceed to pushing changes if the changes are valid. Alternatively: it would be okay to submit updates if there was a way to conduct multiple updates as a “transaction”.

Data source: MongoDB

Connect Vero directly to MongoDB to import audiences and data.

Alert when the subject line has a Liquid mistake

Similar to what you have in the email editor, when editing a liquid, it doesn’t let you save the email and alerts you that the liquid has an error. We found that having a liquid in the subject line lets you save it and continue. It even lets you schedule the email or launch a workflow, but then, at the moment of sending, the email fails to be sent due to this mistake.

Automatic translated draft generation for multilingual campaigns (i18n)

Automate translation drafts for multilingual campaigns, helping clients simplify their process. Feature Workflow: Update an “Enable Languages” feature when creating a newsletter/Email Content within Workflows Click “Translate” to generate drafts in selected languages (e.g., Spanish, French, based on user’s locale) AI-generated drafts appear within the editor, ready for quick review and edits instead of an empty area which we have now Locale-based delivery sends emails in each recipient’s preferred language. Interface: Language-specific drafts show up in tabs or sections within the editor, allowing efficient review and minor adjustments. Why Needed: Reduces manual work for clients handling 6-10 languages. Ensures quicker, consistent multilingual messaging for diverse audiences. Technology: Anthropic or GPT models to create initial “good enough” translation drafts

Add visibility of users to delays in Workflows

It would be great to see when users enter a delay in a workflow, how many there are, who they are, and how long they’ve been in the delay to know exactly when they are supposed to move to the next step in the workflow. Thanks so much!

Click heatmaps in email reports/logs

Most email automation tools I've used in other roles offer the ability to see exactly which part of your email was clicked using heat maps (click maps). Vero currently only shows the link URLs that were clicked, the unique clicks, and total clicks. But if we have a link that is linked multiple times in an email, we'd like to track which placement of the link performed better within each email send! This functionality is extremely helpful when optimizing CTR and total clicks for various templates and campaigns. I'd love to see this built into Vero's product roadmap to help my team optimize our templates and email copy. Thanks so much!

Track "bot clicks" and "bot opens" separately from human opens and clicks

Recognise and record opens and clicks that come from a non-human source, such as Google’s automated image downloads.