Vero is an email marketing tool that lets you set up automated emails to your users that get sent after they’ve completed certain actions. Visit Website
Take your company’s email analysis to the next level by adding Vero as a Source to Segment. We’ll automatically collect email events like
Email Delivered and
Email Opened, forward them to your destinations, and load them into your data warehouse.
In your favorite BI or analytics tool, you’ll be able to analyze your email campaigns in SQL or through drag-and-drop reports. And, you’ll be able to join your Vero data with the event data you’re already sending through Segment to analyze the down-funnel effects of your emails.
If you have previously enabled sending email events via the Vero destination during our beta (using a project write key), you do not need to create new Vero source. Your email data will continue to flow as normal.
From your workspace’s
segment.com/<your-workspace>/sources page, click
Give the Source a nickname and a schema name. The nickname will be used to designate the Source in the Segment interface, and the schema name is the namespace you’ll be querying against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like
Verofor nickname and
verofor the schema name.
The next page (“Overview”) will surface your Segment write key for Vero. Copy this write key.
To finish the setup, you’ll have to go into your Vero account and enter this Segment write key in their integrations settings. Find the right place in Vero by clicking Integrations > Segment.
In Segment, click into your Vero Source in
segment.com/<your-workspace>/sources. From there you’ll be able to add Destinations where you want to see email events.
That’s it! As you send emails, events will now be sent to your destinations and automatically loaded into any warehouses you have enabled.
Vero uses our stream Source component to send Segment email events. It uses a server-side
track method to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query via SQL.
The default behavior is for Vero to pass the
userId associated with the email recipient as the
userId. There are cases in which Vero does not have an associated
userId, in which case the email address will be passed in as the
Collections are the groupings of data we pull from your Source. In your warehouse, each collection gets its own table, as well as a
tracks table that aggregates all the events into a single table.
|Email Sent||Event||Message has been sent from the Vero servers|
|Email Delivered||Event||Message has been successfully delivered to the receiving server|
|Email Opened||Event||Recipient has opened the HTML message. You need to enable Open Tracking for getting this type of event|
|Email Link Clicked||Event||Recipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event|
|Email Unsubscribed||Event||Recipient clicked on message’s subscription management link|
|Email Bounced||Event||Receiving server could not or would not accept message|
|Email Marked as Spam||Event||Recipient marked message as spam|
Send data to Vero
The Vero Source works better when you also connect Vero as an destination. With the Vero Destination, you can use Segment to send Vero user and event data from which you trigger email campaigns. Want to start sending website or mobile data to Vero? Head on over to our Vero destination docs.
If you have any questions, or see anywhere we can improve our documentation, please let us know!