Changelog

Follow new updates and improvements to Vero.

March 20th 2024

New

Vero Connect

We're thrilled to announce that all Vero Connect accounts now have the power to define audiences using Google BigQuery data warehouses. With this latest release, we've added BigQuery to our growing list of data sources, empowering you to effortlessly run queries directly against your Google-powered external datasets.

For more information on how to use the Google BigQuery data source integration, read our help doc: https://help.getvero.com/connect/articles/how-to-connect-to-google-bigquery/

March 20th 2024

Improved

Vero Cloud

  • Optimizations to reduce initial UI boot time in Vero Cloud (by up to 14 seconds for some customers).

  • Updates to transactional email processing to improve (reduce) the time between "event received" and "message sent.

March 20th 2024

Fixed

Improved

Vero Cloud

Vero Connect

  • Fixed a bug where events tracked with the same created_at timestamp as the person.created_at timestamp would not be included in "has event with property equal to X" conditions.

  • Fixed an issue preventing thumbnails showing for older, “cloned” templates.

  • Updated MySQL connections to prefer TLS rather than require TLS in Vero Connect.

  • Add bounce_status and bounce_message to webhooks sent by Vero.

  • Fixed a bug with “Recurring Newsletters” that prevented old campaigns (three+ years old) from successfully sending.

March 20th 2024

New

Vero Cloud

In Vero Cloud, administrators can now give users a new role. This new role enables a user to create and edit campaigns, templates and other resources in Vero but, importantly, limits their access so that they:

  • Cannot view any customer data via the customers, segments or other menu items.

  • Cannot launch, publish, unpublish or otherwise update the status of any newsletter or workflow campaign.

March 20th 2024

Improved

Vero Connect

In Vero Connect, project owners can now see the following details for each of the users with access to the project:

  • “Last seen”, representing the time the user last visited the UI.

  • 2FA status, representing whether users have 2FA enabled or disabled.

  • “Login with Google” status, representing whether users use the “Login with Google” feature. Note that users who “Login with Google” cannot enable 2FA as Google accounts can use Google’s included 2FA functionality.

November 27th 2023

New

Vero Cloud

Vero Connect

We're excited to introduce the custom HTML block in the Drag and Drop email editor!

Vero’s Drag and Drop email editor is an easy to use WYSIWYG email template designer that can help you achieve a lot of layouts and styles. However, sometimes you need something custom that goes beyond what is possible with the supplied design controls.

To help give you the flexibility to add additional design elements to your template, Vero now supports adding custom markup and styles using the HTML block. Using the HTML block is the same as any other content block, simply Drag an HTML block into your template, add your custom code and see the results in the live preview.

Learn more in the help docs.

November 27th 2023

Fixed

Improved

Here's a few fixes and improvements we've made to Connect since our last update.

Improved:

  • Newsletters are now known as Campaigns. After the recent introduction of automations into Vero Connect we have renamed the Newsletters section (where you create, edit and send messages) to Campaigns. This change reflects the increasing amount of messaging use cases that Connect supports and sets it up well for the additional triggers, channel types and content that will be added in the near future.

  • TikTok and X social icons. To help keep up with the latest in social media platforms we have added TikTok and X (formerly Twitter) icons to the social content block in the drag and drop editor. 

  • Batches time description. Alongside some other small UI improvements we added a label that describes how long it will take to send a campaign that is sending in batches, to make it easier to tell how sending in batches will impact how long your campaign will take to fully send.

  • Snippets improvements. We’ve made significant improvements to how Drag and Drop Snippets are processed, these updates have increased the reliability of the snippets feature in areas such as generating preview thumbnail images, propagating changes from locked snippets to the templates they are used in, and displaying fonts correctly. 

Fixed:

  • Only allowing lowercase “email” column. Fixed an issue that would prevent an audience being imported due to the the “email” column not in being in lowercase. 

  • Crontab formatting issue. Fixed an issue with validation logic on the custom crontab option in the Recurring Trigger option that may not nave properly validated when a unit of the crontab string uses a combination of dashes and commas.

  • Cloning campaigns with expired audiences. Fixed an error that occurred when trying to duplicate a campaign that included an imported audience which had expired (imported more than 30 days ago).

November 27th 2023

New

Vero Cloud

We’ve added an additional team member role that has access to view and edit Campaigns but had no access to any customer data. This role has access to build and create campaigns and content, but no access to areas of Vero that may include personal identifiable information.

November 27th 2023

Fixed

Vero Cloud

Here's some bugs we've squashed in Vero Cloud since our last update:

  • Downcased ID not matching newly created profiles. We’ve fixed an issue that occurred when a project has the downcase-id’s and ‘email-as-master setting on where newly created profiles would not be matched.

  • Deleted user error. Fixed an issue that made it appear that a customer had not been deleted when manually selecting the Delete option on the profile. 

  • Pick a winner send time inconsistency. Fixed an issue that made it appear that the winning variation on an AB test campaign would be sent at the incorrect time if the Pick a winner functionality was selected. The time shown in the UI showed the incorrect timezone but the actual send time was correct.

  • Live AB Tests not showing results. We fixed an issue that prevented the results from an AB test from showing until the test had completed.

  • Tagging recently created customers. Fixed an issue that would occur when two api requests were sent in rapid succession, the first to create the user and the second to tag them, the tag request could sometimes get processed before the user is created, causing the tag request to fail.

  • Automatic log out. We’ve have fixed an issue was causing some users to be automatically logged out on more frequent schedule when authenticated using Google.

  • No default in timezone sends. An issue has been fixed that in some cases would prevent users who had no timezone property from receiving a message when the deliver in the customers timezone option was selected. This issue occurred if the if the project timezone was currently observing daylight savings and in countries that recently updated their usage of daylight savings.

  • Negative import counts. We have fixed an issue that would in some cases show a negative count on the failed records column on the import page. 

  • Webhook signing key. It's now possible to add a separate webhook signing key in the UI for Mailgun providers if it doesn't match your main API key. This ensures delivery stats from your Mailgun provider are collected and shown in the Vero UI.

  • Large numbers in customer properties rounding up. We have fixed an issue that caused very large numbers in customer properties to appear to be rounded up. This was due to a limitation in javascript and only affected presentation of the number and did not affect the underlying data.

September 19th 2023

New

Vero Connect

📣 Today we are excited to announce the ability to send a message on a recurring schedule, the first automated trigger in Connect.

The brand new recurring trigger option is available alongside the existing one off triggers and adds the ability to configure a campaign to automatically send on a recurring cycle e.g. every hour, day, week or month.

What is a recurring trigger?

The recurring schedule trigger is a new way to send automated messages with Vero connect. Once your set a recurring schedule (e.g. every day at 12pm), every time the recurring trigger runs, the SQL used to define the campaign audience is re-queried and sends to the latest list of recipients returned by the query.

Recurring triggers in Vero Connect give you the ability to run automated campaigns against your most accurate data sets and help you make the most of the data you already store, without the need to constantly sync or import data to your email platform.

Why use a recurring schedule?

Recurring triggers can be used to automate a number of messaging use cases:

  • Scenario 1: Imagine you want to send weekly customer satisfaction surveys to a targeted group of users who have recently interacted with your support team. With a recurring schedule trigger you can define a SQL query to identify these users based on their support ticket history or specific criteria. Set the frequency to 'weekly' and send a message pointing them to your survey. Once enabled, the system will automatically send the survey to the identified users every week, ensuring consistent feedback collection without manual effort.

  • Scenario 2: Imagine you want to send a message to every user who signed up in the last hour. Simply set your campaign to send on a recurring schedule every hour and then write a SQL query that finds users who signed up within the last hour. With direct access to your data warehouse and the ability to run a query on a recurring schedule, you can simplify your onboarding campaigns and trust that the data powering them is always on point.We’re excited for you to try this feature out and we look forward to seeing all the ways you use it to send campaigns using data accessed directly from your data warehouses and data stores.

Note: We have released this feature in public beta, available on all accounts. Some changes may occur in the next few weeks while we respond to feedback and optimise the feature.

Read all about recurring schedule trigger on the help docs.

If you have any questions, feedback or thoughts, don’t hesitate to get in contact at support@getvero.com.