An official MCP server to enable AI assistants such as Claude and Gemini to interact directly with Vero. Our initial release, as covered by this feature request, will focus on the following functionality: Ability to list all campaigns (broadcasts and journeys). Ability to read-only query the contents of a journey, for interrogation of what a journey covers and what messages it contains. Ability to read and write broadcasts. Ability to read and write campaign content, for both messages inside journeys and broadcasts. We will then expand functionality to include querying campaign results, logs and user profiles. We’ll create follow-up feature requests for these to more easily track progress.

Add the ability to toggle all elements in an email to “Both”, removing any differences between desktop and mobile for the entire campaign.

Catch textual differences between desktop and mobile email views on save, and require editor approval.

We're bringing everything you love about Vero to a completely rebuilt platform. Vero 2.0 is a ground-up rebuild designed to let us move faster and deliver the messaging automation features you've been asking for. This kind of transformation takes time — we're methodically migrating every capability while making meaningful improvements along the way — but the result is a platform that's more powerful, more reliable, and built to evolve with your needs. We appreciate your patience and think you'll love what's coming. You can try Vero 2.0 today and we’re looking forward to making it the default interface soon.

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.

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.

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

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.

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.

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.

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.

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 for customer support agents to search and see profile history but not campaigns.

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).

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

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

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.

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”.

Connect Vero directly to MongoDB to import audiences and data.

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.