Email Delivery & Klaviyo Setup
How Tryvo sends emails to your customers through Klaviyo, which events you can trigger flows on, and which variables you can use in your templates.
Tryvo does not send emails directly. Instead, Tryvo pushes events into your Klaviyo account, and Klaviyo runs the flows you've configured to deliver the email or SMS to your customer.
This guide is for the brand operator setting up Klaviyo for the first time. It covers:
- Why Tryvo uses Klaviyo (and not its own mailer)
- The three events Tryvo will push
- How to connect Klaviyo and build a flow per event
- Every variable you can use in your email templates
You only need a Klaviyo account with admin access. Any active plan works for getting started — the free tier is enough to test the integration end-to-end.
Klaviyo is required: a campaign can't go live until Klaviyo is connected, because every invitation is delivered by your Klaviyo flow.
Why Klaviyo?
Klaviyo's published partner pattern is that integrations like Tryvo push events, and the merchant builds the flow that turns events into emails. We use this pattern on purpose because it keeps the parts of email marketing that you care about in your hands:
- You own the templates. Design, copy, layout, language — all in Klaviyo's editor.
- You own the audience. Tryvo can't see, change or message anyone outside the customers who triggered an event.
- You own deliverability. Email is sent from your verified Klaviyo sender, against your established sender reputation — not from a shared Tryvo mailer.
- One place for marketing. Flows, segments, A/B tests and analytics for Tryvo events live alongside the rest of your lifecycle email.
In short: Tryvo handles when something interesting happens, Klaviyo handles what the customer actually sees.
The three events
Tryvo will push one of three events into Klaviyo. Each event becomes a Klaviyo metric you can build a flow on.
| Event (metric name) | When Tryvo pushes it |
|---|---|
submission_invited | A buyer is invited — right after their order is fulfilled, for a live campaign, if they agreed to email marketing |
submission_approved | You approved their video in the review (passing the AI quality gate alone doesn't trigger it) |
reward_delivered | The reward has been created in Shopify (discount code, cashback refund or free product) |
You decide which of these you want to act on. A common setup is:
submission_invited→ the invitation email with the buyer's personal link (without this flow, nobody receives an invitation)submission_approved→ a short thank-you email letting the creator know their video was acceptedreward_delivered→ an email with their discount code, or confirming the cashback or free product
Connecting Klaviyo
Click Connect Klaviyo
You'll be redirected to Klaviyo, asked to sign in (if you aren't already) and then to Allow the connection.
Tryvo only requests two scopes:
events:write— to push the three events into your accountprofiles:write— to attach each event to the customer's profile (by email)
Tryvo does not get access to your lists, segments, templates or campaigns.
Confirm the green badge
After approval Klaviyo sends you back to Tryvo. You should see a green Connected badge on the integration page. That's it — the connection is live.
Letting the metrics appear
A metric only shows up in Klaviyo after it has been seen at least once. Tryvo now
registers all three metrics automatically every time you connect, so
submission_invited, submission_approved and reward_delivered should be available
right after connecting — you'll find them in Klaviyo under Analytics → Metrics.
If you want to see a metric with realistic data before building on it, you can also send a test push from Tryvo:
- Open any Campaign in the Tryvo dashboard
- Go to the Email tab
- Enter a test recipient and click Send test for each of the three events
Test events use sample data (for example the code TRYVO-TEST-15) and arrive in Klaviyo
right away.

Both the test pushes and the automatic registration events are marked with
is_test: true so you can filter them out of your real flows (see below).
Building a flow per event
Repeat this for each metric you want to send email on.
Create the flow
In Klaviyo go to Flows → Create Flow → Build your own.
Set the trigger
Choose Metric as the trigger type. You'll now see submission_invited,
submission_approved and reward_delivered in the list — pick the one this flow is
for.
Filter out test events (recommended)
Add a trigger filter:
is_testequalsfalse
This prevents test pushes and the automatic registration events (sent on every connect) from triggering real emails to customers.
Filter by language (optional)
If you run campaigns in multiple languages, add a second filter:
campaign_languageequalsde(oren)
Then build one flow per language so each customer gets the email in the right one.
Add the email step
Click Add Action → Email and design your template using the variables below. The most important ones:
{{ event.customer_first_name }},{{ event.brand_name }},{{ event.campaign_callout }}(works well as subject line / hero copy),{{ event.product_title }},{{ event.product_image_url }}{{ event.submission_url }}as the button link — this is the customer's personal invitation link{{ event.reward_summary }}(e.g.10% off) and, in thereward_deliveredflow,{{ event.reward_code }}(the actual redeemable code)
Turn the flow on
Switch the flow status to Live — not Draft or Manual. This is the most common stumbling block: until the flow is Live, Klaviyo collects the events but sends nothing. Once it's Live, the next matching event from Tryvo will trigger the email.
Until each flow is set to Live, Klaviyo will collect the events but won't send any email. If customers are getting invited in Tryvo but not receiving emails, this is the first thing to check.
Variables you can use in templates
Every event Tryvo pushes carries a set of event properties — all of them are listed
below. You can drop any of them into a Klaviyo template using the standard
{{ event.<name> }} syntax.
Use {{ event.X|default:'Fallback' }} to set a fallback for variables that can be
null (first name, discount code, etc.).
Customer
| Variable | Description | Example |
|---|---|---|
{{ event.customer_email }} | Recipient email address | lisa@example.com |
{{ event.customer_first_name }} | Recipient first name (when known) | Lisa |
{{ event.customer_last_name }} | Recipient last name (when known) | Müller |
{{ event.customer_orders_count }} | Number of orders the customer has placed with the brand | 3 |
{{ event.customer_lifetime_value_cents }} | Customer's lifetime spend, in minor units | 24500 |
Invitation
| Variable | Description | Example |
|---|---|---|
{{ event.submission_url }} | The customer's personal invitation link — use it as the CTA / button link | https://tryvo.io/en/submission/brand/…/… |
Campaign
| Variable | Description | Example |
|---|---|---|
{{ event.campaign_name }} | Internal campaign name | Summer 2026 Hero |
{{ event.campaign_callout }} | Your custom callout (Email tab), otherwise an automatic text: "Film a quick video of you with {product} and get {reward}." | Film a quick video of you with Shampoo Bar and get 15% off. |
{{ event.campaign_description }} | Your custom description (Email tab), otherwise the campaign description, otherwise empty | Tell us how this product fits into your morning. |
{{ event.campaign_type }} | ugc-video or b-roll | ugc-video |
{{ event.campaign_language }} | Content language locked at creation (de / en) | en |
{{ event.campaign_id }} | Internal campaign UUID |
Product
| Variable | Description | Example |
|---|---|---|
{{ event.product_title }} | Product the campaign targets | Shampoo Bar |
{{ event.product_image_url }} | Hero product image (use inside <img src="…">) | https://cdn.shopify.com/.../shampoo.jpg |
{{ event.product_price_cents }} | Product price in minor units | 1490 |
{{ event.product_currency }} | ISO currency | EUR |
{{ event.product_id }} | Internal product UUID |
Brand
| Variable | Description | Example |
|---|---|---|
{{ event.brand_name }} | Brand name (use in the from-line or signature) | GlowSkin |
{{ event.brand_logo_url }} | Brand logo URL (when set) | https://…/logo.png |
{{ event.brand_id }} | Internal brand UUID |
Order
| Variable | Description | Example |
|---|---|---|
{{ event.shopify_order_id }} | ID of the triggering Shopify order | 5871234567890 |
{{ event.shopify_customer_id }} | Shopify customer ID (submission_invited only) | 8123456789012 |
{{ event.order_value_cents }} | Total of the triggering order in minor units (submission_invited only) | 4990 |
{{ event.order_currency }} | ISO currency of the order (submission_invited only) | EUR |
Reward
| Variable | Description | Example |
|---|---|---|
{{ event.reward_summary }} | Human-readable reward in English — e.g. 15% off, €10.00, 10% cashback, Free product (coupon) | 15% off |
{{ event.reward_kind }} | discount / cashback / free-product | discount |
{{ event.reward_amount_cents }} | Fixed reward amount (null for percent rewards) | 1500 |
{{ event.reward_code }} | The redeemable code — only on reward_delivered, and only for discounts and free-product coupons (null for cashback and shipped products) | TRYVO-7K2Q9X1M |
Meta
| Variable | Description | Example |
|---|---|---|
{{ event.is_test }} | true for test pushes from the Email tab and the automatic registration events. Add a filter is_test equals false to your live flows to skip these. | true / false |
{{ event.metric_registration }} | Only present (true) on the registration events Tryvo sends when you connect | true |
Variable names are stable. New ones may be added over time, but existing ones won't be renamed or removed without a deprecation notice — your templates won't silently break.
Starter HTML template
Copy this into Klaviyo's custom HTML block — all variables resolve live.
It's a minimal template that uses the most important variables. Paste it into a flow
email and switch to the HTML editor — the button already links to
{{ event.submission_url }}. The same template is available on every campaign's
Email tab.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width,initial-scale=1" />
<title>{{ event.campaign_name }}</title>
</head>
<body style="margin:0;padding:0;background:#f5f5f7;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Inter,sans-serif;color:#0f172a;">
<table role="presentation" cellpadding="0" cellspacing="0" width="100%" style="background:#f5f5f7;">
<tr>
<td align="center" style="padding:32px 16px;">
<table role="presentation" cellpadding="0" cellspacing="0" width="600" style="max-width:600px;background:#ffffff;border-radius:16px;overflow:hidden;">
<!-- Logo -->
{% if event.brand_logo_url %}
<tr>
<td align="left" style="padding:28px 32px 0;">
<img src="{{ event.brand_logo_url }}" alt="{{ event.brand_name }}" height="32" style="height:32px;display:block;" />
</td>
</tr>
{% endif %}
<!-- Headline -->
<tr>
<td style="padding:24px 32px 8px;">
<h1 style="margin:0;font-size:24px;line-height:1.25;font-weight:700;">
Hi {{ event.customer_first_name|default:'there' }},
</h1>
<p style="margin:12px 0 0;font-size:16px;line-height:1.5;color:#475569;">
{{ event.campaign_callout }}
</p>
</td>
</tr>
<!-- Product card -->
<tr>
<td style="padding:20px 32px;">
<table role="presentation" cellpadding="0" cellspacing="0" width="100%" style="background:#f8fafc;border-radius:12px;">
<tr>
{% if event.product_image_url %}
<td width="120" style="padding:16px;">
<img src="{{ event.product_image_url }}" alt="{{ event.product_title }}" width="100" style="width:100px;height:100px;object-fit:cover;border-radius:8px;display:block;" />
</td>
{% endif %}
<td style="padding:16px 16px 16px 0;vertical-align:middle;">
<div style="font-size:14px;font-weight:600;color:#0f172a;">{{ event.product_title }}</div>
<div style="margin-top:4px;font-size:13px;color:#64748b;">
Order #{{ event.shopify_order_id|default:'' }}
</div>
</td>
</tr>
</table>
</td>
</tr>
<!-- Campaign description (when set) -->
{% if event.campaign_description %}
<tr>
<td style="padding:0 32px 8px;font-size:15px;line-height:1.6;color:#334155;">
{{ event.campaign_description }}
</td>
</tr>
{% endif %}
<!-- Reward block (when present) -->
{% if event.reward_summary %}
<tr>
<td style="padding:16px 32px;">
<table role="presentation" cellpadding="0" cellspacing="0" width="100%" style="background:#ecfdf5;border:1px solid #a7f3d0;border-radius:12px;">
<tr>
<td style="padding:16px;">
<div style="font-size:12px;font-weight:600;text-transform:uppercase;letter-spacing:0.05em;color:#047857;">
Your reward
</div>
<div style="margin-top:6px;font-size:18px;font-weight:700;color:#065f46;">
{{ event.reward_summary }}
</div>
{% if event.reward_code %}
<div style="margin-top:10px;font-family:'SFMono-Regular',Menlo,Consolas,monospace;font-size:14px;background:#ffffff;padding:8px 12px;border-radius:8px;display:inline-block;border:1px dashed #a7f3d0;">
{{ event.reward_code }}
</div>
{% endif %}
</td>
</tr>
</table>
</td>
</tr>
{% endif %}
<!-- CTA -->
<tr>
<td align="center" style="padding:8px 32px 24px;">
<a href="{{ event.submission_url|default:'#' }}" style="display:inline-block;background:#0f172a;color:#ffffff;text-decoration:none;font-weight:600;font-size:15px;padding:14px 28px;border-radius:9999px;">
Submit your video
</a>
</td>
</tr>
<!-- Footer -->
<tr>
<td align="center" style="padding:20px 32px 32px;border-top:1px solid #e2e8f0;">
<p style="margin:0;font-size:12px;color:#94a3b8;line-height:1.5;">
{{ event.brand_name }} — Campaign: {{ event.campaign_name }}<br />
{% if event.is_test %}<strong style="color:#b45309;">This is a test event.</strong>{% endif %}
</p>
</td>
</tr>
</table>
</td>
</tr>
</table>
</body>
</html>Klaviyo strips most CSS classes — the template uses inline styles for maximum
mail-client compatibility. The {% if %} blocks automatically hide
the reward / product-image rows when those values are null.
Troubleshooting
The metric isn't showing up in Klaviyo. Send a test push from a Tryvo campaign — the metric only appears in Klaviyo after the first event arrives.
The flow is live but no email is being sent.
Check that your trigger filter on is_test equals false isn't accidentally filtering out
real events too. Also make sure the customer has a valid, subscribed profile in Klaviyo.
The email is sent but variables are empty.
Look at the Event detail view in Klaviyo for that specific event — every property Tryvo
pushed is listed there. If a value is missing, it usually means the campaign doesn't have
that field filled in yet (e.g. no description, no brand logo). Note that order fields are
only filled on submission_invited, and reward_code only on reward_delivered.
Nobody is being invited at all. Invitations are only created for live campaigns, after the order is fulfilled, and only for buyers who agreed to email marketing. Check the campaign's Reach tab to see which events were sent.
Customers are getting duplicate emails. In each flow, add a Smart Sending window (Klaviyo's setting) so the same customer isn't emailed for the same metric twice within a short period.
