Changelog

We've completely rebuilt our help documentation with a fresh new look, improved structure, and powerful new features to help you find answers faster.

What's new

Modern documentation platform

Our help docs now run on a new platform that's faster, easier to navigate, and designed for a better reading experience. The updated interface makes it simple to browse topics, jump between sections, and find what you need.

AI-powered help chat

Get instant answers with our new AI help chat. Ask questions in natural language and receive relevant responses drawn from our documentation, helping you solve problems without having to search through multiple articles.

Improved search

Finding the right help article is now faster and more accurate. Our enhanced search understands your queries better and surfaces the most relevant results, so you spend less time hunting and more time getting answers.

Better organization and updated content

We've reorganized our documentation with clearer navigation and updated key articles to reflect the latest features and best practices. Whether you're learning about Segments 2.0, Journeys, or any other Vero feature, you'll find more comprehensive, easier-to-follow guidance.

👉 Visit the new help documentation

Today we're excited to share improvements to how campaigns are organized and named in Vero 2.0. These updates make it easier to understand the different types of campaigns you can create and help you find what you're looking for faster.

What's changed:

Single message campaigns are now called "Broadcasts" throughout Vero 2.0.

This new name better reflects their purpose: scheduled, one-to-many messages like newsletters and announcements. It distinguishes them from automated, event-driven campaigns (Journeys) and more accurately describes how these campaigns work, rather than focusing solely on their single-send nature.

Dedicated navigation for each type of campaign

Broadcasts and Journeys now have their own sections in the main sidebar navigation, with separate campaign lists at /broadcasts and /journeys. Previously, both campaign types were mixed together in a single list. Now, similar to Vero 1.0, each has its own dedicated page, making it easier to organize, find, and manage your campaigns based on type.

What hasn't changed

Vero 1.0 remains the same

These updates only affect Vero 2.0. If you're still using Vero 1.0, your campaigns, navigation, and terminology remain unchanged. These improvements are part of our ongoing work to make Vero 2.0 more intuitive and powerful as we prepare for the eventual migration from Vero 1.0 to Vero 2.0. We'll share more details about the migration timeline and process as we get closer.

Happy New Year everyone! Here's what we've shipped over the past few weeks to start 2026 strong.

Vero 2.0

New: Events in Vero 2.0 - We've rebuilt the events experience from Vero 1.0 for Vero 2.0. You can now view and search all events tracked in each project with a fully searchable table that makes it easy to find specific events. Click into any event to see detailed information including which campaigns use that event as a trigger, event properties from the last tracked event and a list of users who have recently performed the event.

New: Journey node duplication - You can now duplicate nodes in your Journeys with a single click making it faster to build complex Journey workflows.

Improved: Segment selection in audience imports - The segment dropdown when importing audiences now uses the same query system as the segment condition editor. This means newly created segments appear immediately in the dropdown without needing to refresh the page.

Fixed: Profile ID display errors - Fixed a bug where very large profile ID numbers caused broken links on log and event detail pages. All profile links now work correctly regardless of ID size.

Fixed: MySQL query compatibility - Resolved an issue where some queries with MySQL specific syntaxes are being rejected as invalid. These queries now work as expected.

Security & Infrastructure

Improved: Platform security - We've shipped several security enhancements to strengthen account protections and access controls across the platform.

Improved: Platform performance - We've made several behind-the-scenes improvements to enhance platform stability and performance, including optimized database query handling and enhanced service reliability with improved retry logic.

Here’s a round up of some of the fixes and minor releases we’ve made over the last few weeks. We’re currently running QA over our new Journeys feature in Vero 2.0 and will release this as soon as we’re comfortable it’s ready for production. Stay tuned!

Vero 2.0

• Fixed: Minor Segments UX issues. Fixed several small but noticeable UI and UX issues with the new Segments 2.0 release.

• New: Snowflake key-based authentication. Added key-based authentication for Snowflake connections.

• Improved: ETL speed. Improved performance of initial syncs for ETL transfers from Vero to BigQuery, Snowflake, and other data warehouses.

Both Vero 1.0 and Vero 2.0

• Improved: Webhook speed. Migrated several high-traffic data lookups to a faster, more scalable backend. This reduces latency in overall webhook processing (for webhooks sent from Vero to our customers, Twilio Segment, etc.)

• Fixed: Edge case regarding inaccurate merges. Improved “locking” to ensure reliability of person merges and prevent some (very) rare merge concurrency edge cases.

• Improved: Provider statistics integration. Configuring external sending providers like Sendgrid and Mailgun now runs through new infrastructure, improving reliability during setup and ensuring smoother delivery of message results (sent, delivered, opened, clicked, etc.)

Bonus extra
Our CEO, Chris, released a little tool that enables you to convert Markdown or MDX files to fully-rendered HTML emails.

Check out Chris’ LinkedIn post here.
Check out the code repository here: github.com/getvero/mdx-to-email.

Whilst not part of the core product, this is a powerful, fun internal tool we use have started using ourselves and hope it resonates with others (in which case we’ll build into Vero).

Last week we shipped Segments in Vero 2.0, a major update that improves the segmentation experience and unlocks new capabilities coming soon. In the meantime, here are a few smaller updates we've made since our last post:

Vero 2.0

• Improved: Journey node stats - Message nodes now display stats (Sent, Delivered, Opened, Clicked, Unsubscribed) directly in the canvas for live or stopped Journeys, no need to visit the reports page.

• Improved: Segment validation - Enhanced validation for timestamp and number values used with comparison operators in the segment condition builder, reducing errors and incorrect results.

Vero 1.0

• Improved: "All customers" safeguards - Based on feedback, we've made the ability to send to "All customers" less prominent when selecting newsletter audiences and added confirmation warnings for this action.

• Fixed: Tag name character limit - Tag names are now limited to 255 characters when importing user data. This also applies to Vero 2.0.

• Fixed: Segment refreshing - Resolved an issue causing segments with 'in segment' conditions to refresh slowly before campaign sends.

• Fixed: UI performance - Addressed platform issues causing UI slowdowns. We've increased resources and added monitoring to prevent future occurrences.

Today we’re excited to share that Segments 2.0 is now live in Vero 2.0. This update brings all of the segmentation power you know from Vero 1.0—now rebuilt with a cleaner interface, clearer wording, and a more intuitive segment building workflow. Segments 2.0 is a complete rebuild that builds on the best parts of Vero 1.0’s segmentation experience, refining the interface and structure to offer a smoother, more flexible way to create and manage your customer segments.

You’ll still find all the functionality you rely on from Vero 1.0, now with meaningful UX and UI improvements that make segment building clearer and faster. This release also lays the groundwork for future enhancements designed to enhance your control and flexibility, enabling capabilities that weren’t achievable with our previous segmentation system. Such as including expanded logic controls, multi-property filtering, and richer date-range options.

We’re looking forward to rolling out more updates to segments in the future, but in the meantime, here’s what’s new today.

Key updates include:

• Unified event conditions

  Event-based segmentation is now consolidated into a single event condition with optional filters for event properties, time and date, and frequency.

• Description field for segments

  Add helpful descriptions to keep your segments well-documented and easy for your team to identify.

• Improved search across all inputs

  Faster, smarter search ensures you can quickly find properties, events, and values while building conditions.

• Campaign browsing upgrades

  A refined browsing experience makes it easier to locate campaigns and messages, with a dedicated section for recently selected messages.

• Condition cloning

  Duplicate conditions with a single click to speed up segment creation and experimentation.

• A stronger foundation for what’s coming next

  Today’s release sets the stage for multiple property filters within a single condition, flexible AND/OR groups, and more interactive date-range options.

Backwards compatibility

All of your existing Vero 1.0 segments are fully compatible with Segments 2.0. They’re now visible and editable directly inside Vero 2.0, and any updates you make in either version will sync automatically.

That means there’s nothing you need to migrate or update. Your campaigns continue running seamlessly across both platforms until the full transition to Vero 2.0 is complete.

You can learn more about Segments in our help docs

Another week, another update! Here’s a few small updates we’ve made since our last update.

Vero 1.0

• Improved: Larger number of campaigns shown on events page - We’ve increased how many triggered campaigns are listed for each event in the event manager.

• Fixed: Workflows page loading performance – We’ve resolved a performance issue that was affecting page load times on the Workflows page. You should now see up to a 10× improvement when loading your list of workflows. We’ve also added additional monitoring to help prevent similar performance issues in the future.

• Fixed: Condition’s incorrectly showing “last 1 day” - A short-lived bug temporarily caused “ever” filters (e.g. “has not attempted to send [message] ever”) to appear as “has not attempted to send [message] in the last 1 day.” This did not affect how the condition was calculated, and was only a display issue. It has now been fixed. You don’t need to make any changes — your segment filters should display correctly again.

• Fixed: Unable to archive workflows - We fixed a bug that in some cases prevented workflows from being archived.

Vero 2.0

• New: Push configuration - We’ve shipped the first milestone toward full mobile push notification support in Vero 2.0. You can now configure and manage push channels via our new push configuration system. This feature isn’t yet visible in the UI — contact us if you’d like early access. Future stages, available soon, will add full push sending and campaign functionality.

• Improved: Snowflake authentication update - Due to Snowflake’s recent authentication requirement updates, we’ve updated the Snowflake data source configuration to support private key authentication. You can now upload a private key file directly in the UI, with built-in file validation, clearer error messages for failed connections, and links to setup documentation. This makes connecting Vero to your Snowflake account more secure and reliable.

We’ve updated the naming of several message-related conditions to make them more accurate and easier to understand.

What changed

• Conditions previously labeled “has received [message]” and “has not received [message]” have been renamed to “has attempted to send [message]” and “has not attempted to send [message]”.

• This change is naming-only, the underlying functionality of these filters has not changed.

• All users now have access to the full set of previously labeled “advanced” message conditions, which include filters for “attempted to send”, “sent”, and “delivered”.

Why we made this change

The old label “has received” could be misleading, as it suggested that Vero verified message delivery to a user’s inbox. In reality, this condition has always represented whether Vero attempted to send a message.

To make that clearer, we’ve renamed it to reflect what the system actually tracks:

• has attempted to send (previously labeled ‘received’) → Vero tried to send the message.

• has been sent → The message was successfully processed by Vero’s sending infrastructure.

• has been delivered → The destination mailbox confirmed receipt.