Alongside SMS journey nodes and our new help docs, here's what else was shipped across Vero 1.0 and 2.0 this cycle — featuring some new features, performance upgrades, and a few reliability fixes.

Vero 2.0

New: Conversion goals – You can now set conversion goals on campaigns in Vero 2.0 and track how your messages drive customer actions. When you assign an event as a conversion goal, Vero automatically tracks direct, indirect, and view-through conversions for that campaign. Conversion data appears on each campaign's insights page, giving you clear visibility into which messages are driving the outcomes that matter to your business. This brings the powerful conversion tracking functionality from Vero 1.0 into Vero 2.0's improved interface. Learn how to add a conversion goal

New: Drag-and-drop segment conditions – Building complex segments just got easier. You can now reorder conditions within a group or move conditions between groups using drag-and-drop, giving you more control and flexibility when organizing your segment logic.

Improved: Event occurrence performance – We've upgraded our event data infrastructure, significantly improving query performance and reliability when viewing user activity and building event-based segments. You'll notice faster load times when exploring event histories and creating event-based conditions.

Improved: A/B test summaries – A/B test results now display more comprehensive details alongside performance metrics, making it easier to understand exactly what was tested and compare variant settings at a glance.

Improved: Queued activity log – Activity logs now include a "queued" status, giving you better visibility into message processing stages and helping you understand where messages are in the delivery pipeline.

Fixed: Data feed validation errors – Resolved a bug that incorrectly flagged valid URLs when adding a data feed with variables, preventing you from saving legitimate configurations

Fixed: Segments stuck in refreshing state – Fixed a bug that caused segments to remain stuck in a refreshing state, preventing you from using them in campaigns.

Fixed: User property timestamps – Resolved an issue where user property timestamps could be lost during retry operations, ensuring accurate tracking of when properties were last updated.

Vero 1.0

Improved: Email attachment handling – Updated our managed sending infrastructure to prevent attachments from being incorrectly inlined in some cases, ensuring your email attachments display as intended.

Improved: Mandrill webhook compatibility – Updated the Mandrill webhook schema to handle edge cases more gracefully. The subject field is now optional, and tags and metadata fields can accept empty values. This prevents validation errors when processing legitimate webhook payloads from emails that don't have subjects, tags, or metadata, improving integration reliability.

Improved: Webhook validation – Fixed webhook validation to properly handle edge cases, reducing failed webhook deliveries and improving integration reliability.

Fixed: Segment export failures – Resolved an issue that was causing some segment exports to fail.