Changelog

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.

Fusion enables you to load data from any API at the time emails are being rendered to send to recipients.

You can now add multiple custom headers to API calls made using Fusion. A common use case for this feature is to add headers for secure authentication.

Read more on using Fusion in our help documentation, as well as specific notes on how headers can be used for authentication.

We've re-organised our help documentation to map to each feature in Vero. Articles are now organised under "Newsletters", "Workflows", "Templates", etc. to match each menu item in the Vero interface.

We've also ensured that relevant content—for example, on how to use the email content editor—appear in each section that feature is available. Newsletters and Workflows, in this example.

These changes makes our help documentation easier to navigate and more comprehensive.

There’s a common saying we’ll forgo here, because suffice to say small things CAN have a big effect. With that in mind, here’s our latest batch of tweaks and tinkerings that might float your boat.

Improvement

Format dates correctly in multi-language campaigns - We have added a with_locale filter that will format a date in the language of the locale passed to the filter. For example:

purchase_date = "2015-04-01 11:33"
{{ purchase_date | with_locale: '%Y %b %H:%M', 'es-MX' }} => 2024 abr 11:33

Read more about using with_locale in multi-language campaigns in our help documentation.

General Bug Fixes

Hidden on desktop and mobile fix

Added a fix to the drag and drop editor when selecting the ‘desktop’ or ‘mobile’ responsive options on a block. This makes sure blocks can never be unintentionally set to hidden on both desktop and mobile.

Invalid email address causing failed imports

Fixed an issue where an invalid email address in the results of an SQL query or in a CSV could prevent in some rare cases cause the import from completing successfully.

Cloud Specific Bug Fixes

Error when accessing team members page

We’ve fixed a bug that would sometimes prevent admins from accessing the team members page.

Exporter only exporting 50 campaigns

We’ve fixed an issue when exporting campaign results that only returned the first 50 campaigns no matter how many were selected.

“Service Unavailable” when making team changes

We’ve fixed an bug that would sometimes present a 503 Service Unavailable error when adding team members or changing their permissions.

Only able to access invoices/billing

We’ve fixed a bug that prevent you from accessing the billing or invoices page if you were not in the first project you created.

Log exports failing

Fixed a bug where attempts to export a person’s log history would fail if one of the event logs had been deleted from the system.

Customer merge failure

We've fixed an infrequent failure that would occur when a customer profile was attempting to merge in our backend system. This failure would sometimes occur when two profiles which had both engaged with the same email communication were merged.

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

We’re looking for private beta testers for SMS. If you:

• Are happy to configure and connect Vero to your own Twilio account.

• Are happy to test SMS in a separate project.

• Have one-to-many (newsletter) use cases for SMS.

• Can start using SMS to drive results straight away.

…and are keen to be an early user, please reply and let us know. We’re very, very excited for this feature and will have more announcements soon.

Track on our feedback board.

We’ll soon be releasing a brand new UI for all Vero users. Vero 2.0 is now in private beta and we’re inviting a handful of customers to test out the new UI before promoting to public beta, during which time all customers will have access.

When we release the new UI you will be able to switch back-and-forth between the new UI and the current UI. We know that big UI changes take time to learn and this will ensure the transition is smooth for all customers.

We’d love to show you what we’ve built and hear your feedback so please let us know if you’d like early access!

Contact us for early access