Skip to main content
If you’re currently using Vero 1.0 (Vero Cloud), you can start using Vero 2.0 right away with your existing project. Vero 2.0 is a faster, cleaner interface that combines the best features from both Vero Cloud and Vero Connect, with multi-channel messaging built into its foundation.

​
How to switch between Vero 1.0 and 2.0

Switching is easy, and you can move back and forth anytime:

​
Switch to Vero 2.0

  1. Open your Vero 1.0 (Cloud) account
  2. Click the Project menu
  3. Select Open in Vero 2.0

​
Return to Vero 1.0

  1. In Vero 2.0, click the Project menu
  2. Select Return to Vero 1.0
Your data and settings work seamlessly across both interfaces—changes you make in one will be reflected in the other.

​
What’s available in Vero 2.0

Vero 2.0 brings powerful new features while maintaining compatibility with your existing Vero 1.0 setup:

​
New capabilities

  • Data warehouse audiences — Send campaigns to audiences loaded directly from Snowflake, BigQuery, Redshift, PostgreSQL, MySQL, or SQL Server without storing data in Vero
  • CSV and Google Sheets import — Drag and drop CSV files or connect Google Sheets to create campaign audiences without tagging users or building segments
  • SMS messaging — Send SMS campaigns via Twilio (currently available)
  • Improved navigation — Cleaner interface with better organization of campaigns, templates, and user profiles
  • Activity view — Consolidated view of all message interactions and events (formerly “Logs” in Vero 1.0)

​
What works the same

Your existing Vero 1.0 setup continues to work in Vero 2.0:
  • User profiles — All customer records from Vero 1.0 are visible and editable in Vero 2.0
  • Segments — Vero 1.0 segments work in Vero 2.0 with full bidirectional sync. Edit them in either interface.
  • Templates — Drag-and-drop, HTML, and plain text templates work in both interfaces
  • Channels — Your configured email providers carry over (Vero Mailer, custom domains, SendGrid, Mailgun, etc.)
  • Campaign delivery data — Message interactions (opens, clicks, bounces) are tracked and visible in both UIs
  • Subscription status — Unsubscribes are centralized across both interfaces

​
Feature differences

Some Vero 1.0 features work differently in Vero 2.0:

​
Campaigns

Vero 2.0 uses new campaign types with some feature differences:
  • Vero 1.0 “Newsletters” → Vero 2.0 “Single Message campaigns”
    • A/B testing is supported
    • Languages are not yet supported
  • Vero 1.0 “Workflows” → Vero 2.0 “Journeys”
    • A/B testing is not yet supported
    • Languages are not yet supported
Note: Only campaigns created in Vero 2.0 appear in the Vero 2.0 campaigns list. Your Vero 1.0 campaigns continue to run but are only visible in the Vero 1.0 interface.

​
Templates

  • Drag-and-drop, HTML, plain text — Fully compatible
  • vero-editable templates — Not supported in Vero 2.0. If you edit a vero-editable template in Vero 2.0, it converts to an HTML template.

​
User data management

  • Viewing profiles — All Vero 1.0 customer records are visible in Vero 2.0
  • Adding/updating via UI — Currently done through Vero 1.0 interface
  • Adding/updating via API — Works the same in both versions using the Track API

​
Activity logs

  • Message activity — Sent, delivered, opened, clicked, bounced, unsubscribed events are visible in both UIs
  • Event activity — User events tracked via API are currently only visible in Vero 1.0

​
Data compatibility

​
How data syncs between versions

Your Vero 1.0 and 2.0 projects share the same underlying data:
  • User profiles automatically sync. Any profile in Vero 1.0 is available in Vero 2.0.
  • Subscription status is centralized. Unsubscribes in either version apply to both.
  • Campaign delivery data from Vero 2.0 campaigns appears on user profiles in both UIs.
  • Segments sync bidirectionally. Changes made in either version update in the other.

​
Using data warehouse audiences

One of Vero 2.0’s key features is loading audiences from external data warehouses. When you use this feature:
  • Audience data is not stored in Vero’s database
  • Only id, email (or phone_number), and message delivery logs are stored
  • External audience members are automatically matched to existing Vero 1.0 profiles by id
  • Unsubscribe status from Vero 1.0 is respected—unsubscribed users won’t receive campaigns
Learn more about using SQL data sources

​
Getting help

If you have questions about switching or need help with Vero 2.0 features: