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.