Skip to main content

​
The future of Vero

You can now switch to a preview of the new Vero 2.0 interface from any existing Vero 1.0 (née Vero Cloud) project. This release is not just a glimpse into the future but a fully functional interface, allowing you to send messages right away. New Vero 2.0 UI One of the big benefits of the new UI is that it is compatible with all of the unique features available in Vero Connect. The result is a faster, cleaner, and more organized experience for all customers as Vero 2.0 has features from both Vero Cloud and Vero Connect, combined. On top of this, Vero 2.0 is designed with multi-channel capabilities at it’s foundation. Starting in early 2024, we’ll be releasing SMS and more channels, made possible thanks to the thoughtful design decisions leading up to this release.

​
How to switch to and from Vero 2.0

Switching between the Vero Cloud UI you’re familiar with and the new Vero 2.0 interface is easy. Open your Vero Cloud account, go to the “Project” menu, and select “Open in Vero 2.0 Preview.” Open in Vero 2.0 preview You can seamlessly switch back using the “Return to Cloud UI” button in the project menu. Return to Vero Cloud

​
What you can do in Vero 2.0

The new experience is deliberately familiar in lots of ways. We are taking the best of Vero and improving upon it. On top of this, the new UI brings several powerful new features, including:

​
Load audiences from your data warehouse

Import external audience Additionally, as Vero 2.0 inherits all functionality from Vero Connect, you are able to send single message campaigns to audiences loaded directly from external data warehouses. This means you can send single message campaigns to audiences loaded directly from Snowflake, Amazon Redshift or another data warehouse directly, without syncing and storing the data in Vero. Upon sending a campaign to an external audience, delivery, open, click, and other data seamlessly integrates with customer profiles in your Vero Cloud (Vero 1.0) account. This centralizes unsubscribes, enabling experimentation with direct data warehouse connections without setting up a new Vero Connect project. Read on to learn morea bout how this customer profile stitching works.

​
Directly import CSV audiences

Import CSV Another feature of Vero 2.0 allows you to send one-to-many campaigns by dragging in a CSV directly, eliminating the need for tagging users and creating segments. Direct import from a Google Sheet is also supported.

​
SMS (beta)

Campaigns in the new Vero 2.0 UI now support SMS. This feature is currently in private beta. Please reach out if you’d like access. We’ve partnered with CPaaS platforms like Twilio to deliver a robust SMS platform to our global customer-base. We’ll be sharing more about SMS soon. …and there’s a lot more to come!

​
Feature comparison

We’re adding new features all-the-time and our goal is that, in the not-too-distant future, all customers will spend all of their time in the Vero 2.0 UI. In the interim, here’s a breakdown of each core Vero Cloud (Vero 1.0) feature and what is currently support in the new Vero 2.0 UI.
  • Home. New in Vero 2.0.
  • Campaigns.
    • One-off and scheduled triggers. Replaces “Newsletters” in Vero Cloud.
    • Recurring triggers.
    • Event triggers. Not supported in Vero 2.0 at this time. Coming soon.
  • Templates. Fully backwards compatible except for vero-editable templates.
    • Drag-and-drop, HTML, plain text templates. Can be in Vero 2.0 or Vero Cloud can be edited in either UI.
    • vero -editable templates. Not supported in Vero 2.0. Editing a vero-editable template in Vero 2.0 will convert it to a HTML template.
  • Activity. Previously known as “Logs”.
    • Message-related activity. Vero 2.0 supports all message-related activity, e.g. sent, delivered, opened, clicked logs.
    • Event-related activity. Vero 2.0 does not yet support event-related activity, i.e. customer events you’re tracking.
  • Audiences. Not supported in Vero 2.0 at this time. Coming soon.
  • Data Sources. New in Vero 2.0.
  • Channels. Replaces the “Email Providers” and “Push Providers” menus in the Vero Cloud “Settings” UI.
  • Subscriptions. Replaces the “Customers” menu.
    • Customer profiles. Fully backwards compatible. All customer records visible in Vero Cloud are visible in Vero Connect.
    • Customer “properties”. Not supported in Vero 2.0 at this time.
    • Customer “events”. Not supported in Vero 2.0 at this time.
  • Settings. Backwards compatible. Settings that are available in Vero 2.0 are all backwards compatible. More settings are being added.

​
Understanding customer profile stitching

​
How Vero Cloud stores customer data

In Vero Cloud, customer records are stored in Vero’s internal database. Whenever you add a customer record you can also add:
  • Properties. Attributes such as first_name, last_name, etc. added to the customer profile.
  • Events. Data tracking what users did and when they did it as Signed up, Attended webinar, etc.
Whether added via the API or via CSV, you must define an email and/or id field. The id must be a unique value representing that customer and can be the email value. When adding data about a customer in the future, using this id or email enables you to append data without creating new, duplicate customer records. This is called “identity stitching”. Vero will also use this id and email to correctly “stitch” together all message delivery logs (sent, delivered, opened, clicked, etc.)

​
Vero 2.0 external audiences feature

The Vero 2.0 UI includes several new features. An exciting new feature is the ability to connect to external data sources such as AWS Redshift, Google BigQuery, Snowflake and beyond. When loading an audience from any of these external data sources, you manually import the fields you want. You must import both an id and an email field when importing an audience (the UI will not let you import and audience without these). When using external audiences customer attributes are not stored in Vero’s internal database. The only data stored in Vero’s internal database is:
  • The id and email values.
  • Message delivery logs (sent, delivered, opened, clicked, etc.)

​
How data is stitched between the two UIs

Whilst the new Vero 2.0 UI doesn’t (yet) support viewing or updating customer properties and events (via the API or CSV) it does support viewing:
  • Subscription status (subscribed/unsubscribed). The Vero 2.0 UI will show these for all customer records , regardless of whether they were created in Vero 2.0 or Vero Cloud.
  • Message send logs (sent, delivered, opened, clicked, etc.). The Vero 2.0 UI will show these logs for campaigns sent with the Vero 2.0 UI (at this time).
As a result, it’s important that any audiences imported from an external data source can be stitched together with any customer records you have previously uploaded in the Vero Cloud UI. When building an external audience, you must provide an id field. This id field is used to find and stitch records based on

​
An example, for clarity

Imagine you’ve previously added two customer records using the Vero Cloud UI (added via API or CSV):
  1. id: a@yourdomain.com, email: a@yourdomain.com
  2. id: 1234, email: b@yourdomain.com
  3. id: 5678, email: c@yourdomain.com
You switch to the new Vero 2.0 UI and import an external audience from Snowflake. In your audience you have customer rows as follows:
  1. id: 1234, email: d@yourdomain.com
  2. id: 9012, email: a@yourdomain.com
  3. id: c@yourdomain.com, email: c@yourdomain.com
Based on this data, Vero will do the following:
  • #4 will be stitched to #2. The email is not updated and will remain as b@yourdomain.com.
  • #5 will create a new record.
  • #6 will create a new record. It will not stitch to #3, even though the email values are the same.

​
The future

We are rolling out more features to simplify customer profile stitching in the new Vero 2.0 UI. This will make it easier to work with external data sources and with data stored in the internal Vero database. We can’t wait to release them!