Product Update – February 2025
-
News and UpdatesUpdatedPosted:
On this page
Hi folks 👋
It’s been a productive start to the year, we’ve been making strong progress toward our Q1 goals—including the release of A/B testing in Vero 2.0—and moving steadily toward our first major milestone for Workflows 2.0, an exciting rebuild of one of our most used and loved features. Stay tuned for more news on those features soon!
Along the way, we’ve been rolling out updates that not only enhance the experience today but also lay the groundwork for making Vero 2.0 as powerful and seamless as possible. So buckle up for a jam packed update and enjoy everything we’ve shipped since the start of the year.
Until next time, Rory 🇦🇺 Product Manager
<img class="brandmark" src="https://veroheadless.wpengine.com/wp-content/uploads/2024/09/vero2.0.png" alt="Vero 2.0 logo" width="109"/>
<h2><span style="color:#17DA88">New</span> Data Destinations</h2>
We’ve rolled out an ETL data export feature in Vero 2.0 that makes it simple to sync both historical and real-time message, campaign and profile data directly to major data warehouses. Instead of grappling with webhooks or complex ETL tools, you can now convert your existing data source credentials into a data destination. This integration leverages Prequel to backfill data, streamlining your reporting and reducing support friction while ensuring you have the comprehensive insights you need.
Read the help doc to learn more or contact support@getvero.com for early access.
<h2><span style="color:#17DA88">New</span> Data Feeds</h2>
We’ve introduced Data Feeds in Vero 2.0, giving you the ability to use external API endpoints to insert personalized data into your campaign content.
Formerly known as Fusion endpoints and External Attributes, after careful consideration we renamed the feature in Vero 2.0 to “data feeds” to better fits today’s marketing landscape.
Additionally, this update lets you define multiple API endpoints at the project level in your settings, making it easier for you to add personalized data to your campaigns without needing technical expertise or per-campaign configuration.
Once your commonly used endpoints are setup in the project settings, you can now simply select which data feeds to use in your campaigns during content creation, eliminating the need to configure the same endpoints in every campaign. This also adds the ability to use multiple external APIs in one campaign.
Read more about setting up data feeds
<h2><span style="color:#17DA88">New</span> Event Triggers</h2>
Event-triggered campaigns are now here in Vero 2.0, empowering you to send user triggered single-message campaigns in real time in our newest platform. Until now Vero 2.0 has only supported one-off or recurring message sends, the addition of event tracking is a big step towards our new and improved Workflows in Vero 2.0 (listen out for more news soon).
You can easily select an event (tracked via our track API or Segment integration) to trigger real-time, personalized messages during campaign setup. As with any campaign, you can use Liquid to insert event data into your message content for dynamic personalization.
We’ve also added the comprehensive logging and reporting you’d expect, so you can monitor performance and ensure your campaigns are engaging the right audience.
Learn more about using event triggers in Vero 2.0
<h2><span style="color:#17DA88">New</span> Tracking API key management</h2>
We’ve launched a new and improved API key management UI in Vero 2.0 that lets you securely generate, label, and expire publishable keys for the Track API. This upgrade ensures that your tracking integrations remain secure while giving you full control over your tracking tokens.
If you’re setting up event triggers in Vero 2.0, use this UI to get the tracking API keys you need.
To support API keys management in Vero two we’ve also rebuilt our Javascript Tracking Library from scratch and published it on NPM, making it even easier to include in your codebase.
<h2><span style="color:#17DA88">New</span> ‘Real’ and ‘bot’ engagement report summary</h2>
We’ve enhanced campaign reporting in Vero 2.0 to provide clear insights into the growing trend of bot opens and clicks. Recognizing that bot activity is on the rise and can skew your engagement metrics, our updated reports now include a breakdown of real versus bot interactions in your CSV exports and dashboard. With a new dropdown filter allowing you to toggle between “All,” “Real,” and “Bots,” and conditions that now only count genuine interactions for “has opened” and “has clicked,” you can better gauge the true performance of your campaigns and make more informed marketing decisions.
<h2><span style="color:#17DA88">New</span> SMS Quiet Hours</h2>
We’ve updated our SMS Quiet Hours Compliance in Vero 2.0 to help you meet regulatory requirements for sending non-transactional marketing messages. By using recipient region codes or phone number area codes to determine local timezones, Vero automatically prevents messages from being sent during restricted hours—ensuring compliance with global and country-specific quiet hours while still delivering transactional messages as needed.
Read more about SMS Quiet Hours Compliance
Improved
- User experience refinements – Driven by our relentless appetite for a better user experience, we’ve refined the Vero 2.0 UI to boost consistency, usability, and overall clarity. These updates streamline navigation and simplify campaign setup—reorganizing key sections, enhancing error handling, and prompting you to adjust settings when switching trigger types—so you can work more efficiently and confidently across the platform. You might not notice a dramatic overhaul, but these subtle improvements are our way of continually making Vero better for you.
<img class="brandmark" src="https://veroheadless.wpengine.com/wp-content/uploads/2024/09/vero1.0.png" alt="Vero 1.0 logo" width="109"/>
<h2><span style="color:#17DA88">New</span> Real and bot opens and clicks in engagement report exports</h2>
We’ve updated CSV exports to include separate counts for real versus bot opens and clicks, providing a clearer picture of your campaign performance alongside the enhanced UI reporting in Vero 2.0 (mentioned above).
Improved
- Format dates correctly in multi-language campaigns. We’ve introduced a new failed webhook in Vero 2.0 to keep you informed when Fusion endpoints or email validations run into errors. This behind-the-scenes update is designed to give you real-time visibility into issues so you can address them promptly, and we’re already planning to expand its coverage in the future. Our updated documentation reflects these changes, ensuring you have all the details at your fingertips.
Fixed
- Fixed bug with timezone newsletters where a person with timezone inside the range of allowed timezones but not equal to one of those timezones would get skipped. Now the email will send in the next previous timezone (eg. 9.5 will send in 10.)
- Fixed a bug with the workflow builder that would in rare occasions make the workflow appear blank.
- Fixed an issue in chrome where the content preview panel would not render the content
- Fixed an issue with fusion urls using basic_auth, with certain special characters in the username:password.
- Patched an issue where unsuppressing a user did not always unsuppress them from the relevant domain in Mailgun.
- Improved Fusion related errors/discards, so that it’s clear in the UI whether there was a bad response, the endpoint returned a 204 No Content response, or the response body was empty.
- Previews will now honor global and individual level click tracking settings.
Latest articles and important information
The Rise of Bots: The Uninvited +1s
You may have seen a lot of discussion around these "gosh darn bots" impacting email metrics lately. If you’ve seen emails marked as opened or links clicked within seconds of delivery, often at the exact same minute, you’re likely witnessing the handiwork of bots.
Vero DNS Updates 2025
Over the last several months, we’ve been working hard to implement fantastic new infrastructure improvements at Vero. One of these involves an upgrade to our email delivery infrastructure. To ensure seamless performance and the full impact of these improvements, you may be required to update the DNS records for your sending domain(s).
