So you want to send emails from Vero that actually respond to what your users do—not just blast the same message to everyone. Even better, you want those emails to use custom data about your users. Good news: it’s doable, and you don’t need to be a developer genius to get started.
This guide is for anyone running a SaaS, app, or online store who’s tired of dumb, one-size-fits-all emails. If you want to trigger emails based on real actions (like abandoning a cart, hitting a milestone, or just doing something cool) and include details specific to each user, you’re in the right place.
Let’s get straight to it.
1. What Vero Does (and Doesn’t) Do
Vero is an email automation tool that’s all about behavioral emails. You track what your users do, fire off events to Vero, and it sends emails based on those events. You can also send along custom user data that can be used in your emails.
What Vero does well: - Sends emails based on real user actions, not just time-based drips. - Handles complex logic with segments, rules, and custom properties. - Lets you use custom data in your email content—if you set it up right.
What Vero doesn’t: - It won’t magically guess what your events should be. Garbage in, garbage out. - It’s not a full CRM or a magic AI that “knows” your users. You have to send it the right data.
If you’re hoping for a tool that auto-magically knows when your user is “engaged,” look elsewhere. But if you’re ready to set up real triggers and pass in custom data, you’ll get a lot out of it.
2. The Big Picture: How Event-Based Emails with Custom Data Work
Here’s the basic flow: 1. Your app or website tracks a user action (like “Signed Up” or “Upgraded Plan”). 2. You send an event to Vero’s API. This event can include any custom data you want. 3. Vero receives the event, matches it to the right user, and can trigger an email. 4. Your email template uses the custom data you sent, like the user’s name, plan, cart items, etc.
Key Point:
You have to send both the event and the data to Vero. Vero only knows what you tell it.
3. Step-by-Step: Triggering Event-Based Emails with Custom Data in Vero
Let’s break this down into actual steps you can follow.
Step 1: Decide What Events (and Data) Matter
Don’t overthink it. Start by writing down: - What user actions should trigger an email? (e.g., trial started, cart abandoned, feedback submitted) - What details do you want to include in the email? (e.g., user’s first name, the item they left behind, discount code)
Pro Tip:
Start simple. You can always add more events and data later. Avoid the urge to track everything.
Step 2: Make Sure Your User Data Is In Vero
Before you can trigger an email, Vero needs to know who your users are. Each event you send must be tied to a user (usually with an email address or user ID).
- If you already sync users to Vero, great.
- If not, you’ll need to send a “Create or Update User” call to Vero’s API first, or use their JavaScript snippet for web apps.
Example API call:
json POST /users/track { "id": "12345", "email": "sarah@example.com", "first_name": "Sarah", "plan": "Pro" }
You can do this when a user signs up, logs in, or at any key point.
Gotcha:
If you don’t send user data first, your event will just vanish into the void. Always make sure the user exists in Vero.
Step 3: Send the Custom Event (With Data) to Vero
Here’s the fun part. When a user does something, send an event to Vero’s API, including any data you want to use in your email.
Example: User abandons cart
json POST /events/track { "identity": { "email": "sarah@example.com" }, "event_name": "Abandoned Cart", "data": { "cart_items": [ {"name": "Blue Hoodie", "price": 49.99}, {"name": "Sneakers", "price": 89.99} ], "abandoned_at": "2024-06-25T14:30:00Z" } }
- The
event_namecan be anything you want (keep it consistent). - The
dataobject is where you put all your custom info.
How to send it: - Use the Vero REST API, or - Use their JavaScript SDK if you’re running in-browser.
Pro Tip:
Don’t send sensitive info (like passwords or credit cards). Stick to stuff you actually need for the email.
Step 4: Build Your Event-Triggered Campaign in Vero
Now, log in to Vero and set up a campaign that listens for your event.
- Create a new workflow or broadcast.
- Choose “Event Triggered” as the campaign type.
- Set the trigger event name to match exactly what you’re sending (e.g., “Abandoned Cart”).
- (Optional) Add filters or conditions — for example, only email users with more than $50 in their cart.
What works:
- Use segments to avoid spamming users who already bought.
- Test with real data—Vero lets you preview emails using sample events.
What to ignore:
- Don’t get lost in Vero’s advanced logic right away. Focus on making one event work end-to-end.
Step 5: Use Custom Data in Your Email Template
Here’s where the magic happens. In your email template, use Vero’s templating language (liquid syntax) to insert the data you sent.
Example:
Hi {{ user.first_name }},
We noticed you left these items in your cart:
{% for item in event.cart_items %} - {{ item.name }} (${{ item.price }}) {% endfor %}
Want to finish your purchase?
user.first_namepulls from user data.event.cart_itemsloops through the array you sent in your event.
Testing tip:
Use Vero’s preview tools and send test emails to yourself. It’s easy to make typos in the template, and nothing kills trust faster than a broken email.
Step 6: Test the Whole Flow
Don’t just hope it works. - Trigger the event yourself (use a staging environment if you have one). - Check: Did the email send? Did the custom data show up? - Look for edge cases—empty data, wrong event names, users with missing info.
Debugging tips: - Use Vero’s logs to see received events and users. - Double-check spelling: event names and data keys must match exactly. Vero won’t warn you about typos.
Step 7: Monitor, Iterate, and Don’t Overcomplicate
Once you’ve got your first event-based email working, pay attention to: - Open rates and clicks (obviously). - Whether users reply or actually do what you want. - If you’re getting a bunch of errors, revisit your data structure or event naming.
Don’t:
- Try to “personalize” every single thing from the start. Get the basics right first.
- Set up 20 event triggers on day one. Start with your highest-impact email.
Honest Pros and Cons
What works: - Vero’s event-based flows are powerful if you send clean, consistent data. - Using custom data makes your emails way more relevant—users notice. - You can iterate fast once you get the hang of the basics.
What doesn’t: - If your data is messy or inconsistent, expect confusion and silent failures. - Vero’s docs are decent, but not always beginner-friendly. You may need to poke around or ask support. - Over-complicating things early is a recipe for frustration.
Wrapping Up
Getting event-based emails working in Vero with custom user data isn’t rocket science, but it does take a little planning. Decide what matters, send clean events, and keep your templates simple at first. Don’t try to automate your entire business in one go—get one flow working, then improve from there.
Keep it simple, watch what works, and iterate. That’s how you get smarter emails (and happier users) without burning a week on setup.