January 8th, 2026
New
Improved
Vero 1.0
Vero 2.0
Happy New Year everyone! Here's what we've shipped over the past few weeks to start 2026 strong.
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.
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.