Changelog

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

We’ve launched a new API key management feature 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.

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.

Real and bot open and click data is also available in all report exports in both Vero 1.0 and Vero 2.0.

Hot on the heels of our latest release, we’ve got one more update to wrap up the summer (or winter for folks south of the equator)

In our last release, we introduced the all-new Vero 2.0 interface, and the ability to switch between the new and existing interfaces at will. Today, we’re thrilled to bring you a feature that will significantly enhance your ability to send campaigns in Vero 2.0 to your existing customer base—the ability to select and use your existing segments, which we’re now calling “Cloud Segments,” in Vero 2.0.

This means you can continue to edit and create segments in the Vero 1.0 interface and seamlessly use them in your Vero 2.0 campaigns. It’s now easier than ever to leverage your existing customer segments and data in Vero 2.0, paving the way for even more of your campaigns to be managed in this new interface.

You might be wondering, “Why can’t I create segments in Vero 2.0 yet?” The good news is we’re working on it. In the meantime, this new feature allows you to start sending more campaigns in Vero 2.0 right away.

Learn more about using Cloud segments in Vero 2.0

SMS is one of our most requested features and something we’re delighted to finally roll out! To build this feature we’ve had to re-architect several components of our platform to make it more flexible and to increase sending speed. 

SMS is now available in Vero 2.0 for all currently supported Vero 2.0 features.  As of today you can:

• Import phone numbers as part of audiences in Vero 2.0.

• Send one-to-many and recurring scheduled campaigns.

• Personalize SMS messages using audience data.

Read more on setting up Vero with Twilio and sending an SMS campaign. If you would like to work with our team to register and manage your phone numbers for you (rather than bringing your own Twilio account) please email us at support@getvero.com and let us know. We'd be delighted to help.

As of today, you can switch to the new Vero 2.0 interface from any existing Vero Cloud project. Vero 2.0 is a glimpse into the future and a fully functional product, allowing you to send messages right away.

Vero 2.0 is built from the ground up on top of a new API, which we’ll be releasing publicly. It's also built on a brand new frontend, resulting in a faster, cleaner, and more organized experience.

Even more exciting, Vero 2.0 is designed to be truly multi-channel thanks to several large architectural changes. We’re currently rolling out SMS and, thanks to the thoughtful design decisions we’ve made, look forward to releasing WhatsApp, in-app messaging and more as soon as we can.

Here's some improvements over Vero 1.0

• Faster and more responsive UI.

• Improved campaign creation flow.

• Ad-hoc CSV and SQL audiences.

• Connect directly to data warehouses and Google Sheets.

The quality of Vero 2.0 is much higher than anything we’ve released before and we're proud for it to be platform that future Vero features will be built on. We hope you’ll notice the difference. Stay tuned for more releases in Vero 2.0 throughout the remainder of 2024.

Read more on our blog or learn how to switch to Vero 2.0

We have seen a large rise in the number of automated clicks from “bots”, often run by the receiving mail server.

Whilst these “bots” provide value to recipients they also result in unintended consequences, one of which is unintentionally unsubscribing users when the “bots” automatically click the “unsubscribe” link in emails.

Historically Vero has automatically unsubscribed users as soon as they reach the unsubscribe page, i.e. as soon as they click the link. We have made a change so that users now have to land on the unsubscribe page and manually click the “Unsubscribe” button.

This will ensure only recipients who genuinely wish to unsubscribe will be unsubscribed.

Starting today, any time someone submits a HTML form created in Vero, Vero will automatically detect if the submission is from a real person or a bot.

To do this we are leveraging Cloudflare Turnstile, an alternative to Google’s reCAPTCHA that does not require interaction. Cloudflare Turnstile is build on the Cloudflare Challenge platform and uses several heuristics to determine if the traffic is from a human or a bot. These include IP addresses, browser fingerprinting, etc. 

We chose Turnstile so as not to introduce an extra step requiring manual interaction when forms are submitted, as every step matters for conversions.

Users will be presented with an intermediate page, as per the screenshot in this update, which will automatically forward the user on if they’re determined to be a human and will deliver a failure message if the traffic is considered to be from a bot.

This new feature is automatically enabled across all accounts and is in response to a growing number of requests to automatically filter bot traffic for our customers. Cloudflare is a leader in network protection and, based on our testing, we are confident in this solution as striking the right balance between protection and efficiency.