📣 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.

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.

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

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.

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

Over the past few weeks, we have implemented significant infrastructure enhancements that yield impressive results. Importing an audience is now up to 10 times faster, while message delivery speed has also seen a notable improvement. At Vero Connect, we're dedicated to providing you with the fastest workflow to reach your customers. These enhancements are part of our long-term work to continually enhance Vero's underlying platform and improve your user experience.

For customers operating out of Europe, we have added support for Mailgun’s EU domain regions. To add your EU Mailgun domain, simply go to /settings/email-delivery and choose "Europe" in the "Region" dropdown when adding your Mailgun domain details.

Here's two bug fixes we recently pushed:

Here's a couple of fixes and improvements we've made to Vero in the last few weeks.

We have added the ability to send to unsubscribed customers for messages that are transactional in nature.

In situations where businesses need to facilitate a transaction or provide a product or service requested by the customer, there is now an option to ‘send to unsubscribed users’ as part of defining the campaign audience.

With new new automation features coming soon, we have made some changes to how campaigns are created, adding a new "trigger" section for defining when to send the campaign. The usual options to send “Immediately” or at a “Specific date & time” have been relocated to this section.

This new pattern of choosing when to send your campaign up front will be especially useful when we add automated triggers in the near future.

We have also implemented a review step to provide a clear overview before confirming the message. To streamline the user experience, we have also relocated the advanced settings to the content section.

These improvements aim to enhance the overall usability and are in line with our vision for a flexible and composable marketing platform, and make room for multiple different ways to trigger a campaign.

Underneath the surface, these changes are built on an entirely rebuilt API that we plan to make accessible in the near future.

It is now possible to download all activity and email logs for an individual customer via csv. There is a new ‘Download all activity’ button on every customer profile, which downloads a csv containing the full customer history, up to 5000 rows.

Downloading the customer activity can come in handy when diving into a customer’s interaction with your messages if you need to look beyond 30 days.

Vero administrators can now see the following for each user on their account via the Account > Teams page:

Both of these features make it easier to secure your account and tidy up inactive or insecure accounts.

Coming up: We are also working on adding support for viewing which users "Sign in with Google".

Here's some bugs and improvements we shipped this sprint.