It’s been a big few weeks — we’ve introduced new Journey building blocks, added more MCP tools and API endpoints and shipped a solid run of fixes and improvements. We’re also making good progress on some long awaited features, which we will be bringing you more info about soon.

As a reminder, the Campaigns API and MCP server are enabled on a per-account basis. Contact support@getvero.com if you'd like access.

New

• Preference Center V2 (early access) – Group your messages into topics and give recipients a hosted page where they can choose what they hear about, instead of unsubscribing from everything. Topic preferences are respected across email, SMS and push, and can be set through the API or MCP. Available on request while we work towards the full rollout in Vero 2.0 — get in touch at support@getvero.com to request access and read the help docs to find out more.

• Random Split node in Journeys – A new Random Split node sends a set percentage of profiles down each path, so you can test variations of a journey against each other. Use it to compare message content, timing or channel choices within a single journey, rather than building and maintaining separate journeys to do the same thing.

• Remove Exit nodes from Journeys – We've added a handy new way to remove exit nodes and rejoin them to different places in your journey. This makes it easy to undo adding an exit node, and adds another bit of flexibility when you're reshaping a journey that's already live.

• A new sign-in experience – Vero has a new login page and a single, consistent sign-in, sign-up and logout flow across Vero 1.0 and Vero 2.0. Email and password and Google sign-in both work as before, and your existing login details carry across — there's nothing you need to do differently.

• Connect AI clients to Vero with OAuth - MCP-enabled AI clients can now connect to Vero by signing in through your browser, rather than being configured with an API key. Authorise the client once and it picks up your existing Vero access.

• Trigger Vero events from MCP - You can now trigger a Vero event for an existing customer profile directly from an MCP-enabled workflow, allowing events to start configured journeys or campaigns.

• Journey and broadcast metrics in MCP - You can now retrieve performance metrics for journeys and broadcasts through MCP, including sends, deliveries, opens, clicks, unsubscribes, reporting dates, and per-message or per-run breakdowns.

• Broadcast metrics in public API - Broadcast performance data is now available in the public API, including sends, deliveries, opens, clicks, unsubscribes, and per-run performance for recurring broadcasts.

• Search across broadcasts, journeys, and messages - You can now search across broadcasts, journeys, and their messages in Vero's MCP tools. Results are grouped by type and include short snippets to help find campaign content faster.

• Localised journey content through the API – New v2 endpoints let you write localised content for journey messages, so translations can be created and updated from your own systems instead of being maintained by hand in the journey builder. This brings journey messages in line with how localised content is already handled elsewhere in Vero.

Improved

• Faster segments and reporting – Segment refreshes, timeline charts and usage counts all run noticeably quicker. The difference is most obvious on larger accounts, where segment counts and reporting views previously took the longest to load.

• Unverified channel warnings – Vero now flags an unverified sending channel while you're setting up a campaign, rather than at send time. You can sort out verification before scheduling, instead of finding out about it when the campaign is due to go out.

• Improved MCP validation for broadcast content - AI clients now get clearer guidance on supported content formats for email, SMS, and push messages, with earlier and more helpful validation errors for invalid requests.

• Journey message lists are paginated in MCP – Large journeys now return in pages instead of one oversized response.

• Removing From and To email addresses – Before you delete an email address, Vero now shows which campaigns use it in a From or To field, so you can see exactly what will be affected and how.

Fixes

• Faster email event reporting – Email activity reporting is now more reliable. We fixed an issue that could delay delivery, open, and click events from appearing in campaign reporting. New email events will now show up more promptly across your campaign statistics.

• Correct verification status for Vero Managed channels – Vero Managed email channels would sometimes show an incorrect “unverified” warning when setting up a campaign with a Vero managed email provider.

• Webhook payloads restored – _comm_occ_id and message _variation_id are back in webhook payloads after being dropped in a recent release. If you use these fields to match webhook events to a specific send or variation, no changes are needed on your side.

• Archiving campaigns with broken conditions – In some cases a campaign with corrupt conditions couldn't be archived, leaving it sitting in your campaign list with no way to tidy it away. These campaigns can now be archived as normal.

• Audience update dialog – In some cases the confirm button in the audience update dialog did nothing, so the change wasn't applied. Confirming now saves the update as expected.

• Import progress – Progress didn't update for imports sourced from a segment, which made a running import look like it had stalled. Progress now updates throughout the import.

For any questions don't hesitate to reach out to support@getvero.com