Klaviyo

Set up in Settings → Integrations

Connect Klaviyo and Evident stops sending review request emails itself. Instead it fires an Evident Review Request event into Klaviyo at the moment the email would have gone out, and your flow does the sending.

That is usually what you want if you already run lifecycle email: one set of templates, one suppression list, one sending reputation.

How it works

1. Order placed. Evident detects it and waits for your configured delay — seven days after shipping, say.
2. The event fires after the delay, carrying order, product and review-link data.
3. Your flow sends immediately. The timing is already baked in.

1. Connect

Settings → Integrations → Klaviyo → Connect. You are redirected to Klaviyo to authorise, and returned with a Connected status.

Once connected, all review request emails for that store route through Klaviyo. Evident’s sequence steps still supply the timing; Klaviyo does the sending.

2. Create the flow

In Klaviyo: Flows → Create Flow → Build your own. Name it something like “Review Request — Evident”.

Setting	Value
Trigger type	Metric
Metric name	Evident Review Request
Flow filter	None required — Evident handles eligibility

3. Add the email, with no delay

Add a Send Email action immediately after the trigger. Do not add a time delay.

Evident already held the event until your configured delay elapsed. A delay in Klaviyo stacks on top and doubles the wait. When the event arrives, send.

Event properties

Property	Contents
{{ event.order_id }}	The order ID from your store
{{ event.product_names }}	Comma-separated list of product names
{{ event.products }}	Array of products — each has name, imageUrl, reviewUrl
{{ event.review_url }}	The first product’s review URL
{{ person.email }}	Set by Evident on profile upsert

Loop over the products

Use {% for %} rather than event.review_url, so multi-product orders work. A single-product order renders one item naturally — no special-casing.

{% for product in event.products %}
<table role="presentation" cellpadding="0" cellspacing="0"
       style="margin: 0 0 16px; width: 100%;">
  <tr>
    <td width="96">
      <img src="{{ product.imageUrl }}" alt="{{ product.name }}"
           width="80" height="80"
           style="border-radius: 8px; object-fit: cover;" />
    </td>
    <td>
      <p style="margin: 0 0 8px;">{{ product.name }}</p>
      <a href="{{ product.reviewUrl }}"
         style="display: inline-block; padding: 10px 24px;
                background: #111827; color: #fff;
                border-radius: 6px; font-size: 14px;
                text-decoration: none;">
        Write a Review
      </a>
    </td>
  </tr>
</table>
{% endfor %}

4. A reminder, optionally

After the first email, add a Time Delay of 5–7 days, then a second email.

Put a Conditional Split before the reminder checking whether the customer has fired Evident Review Submitted since entering the flow. Route Yes to Exit, No to the reminder — so you do not chase someone who already reviewed.

Other events

Beyond the review request, Evident fires metrics you can build flows on:

Evident Review Submitted · Evident Review Approved · Evident Review With Photo Submitted · Evident Review Reminder · Evident Low Rating Review Alert · Evident Review Incentive Earned · Evident Review Coupon Generated · Evident Loyalty Points Earned · Evident Loyalty Points Redeemed · Evident Loyalty Tier Upgrade · Evident Referral Invited · Evident Referral Converted · Evident Referral Reward Earned · Evident Birthday Soon

Evident Low Rating Review Alert is the one to wire up first, and not as a customer email — send it to yourself. A one-star review reaching a human the same day is worth more than any flow you will build.

Notes

• Evident upserts the Klaviyo profile, so person.email and profile properties are populated before your flow runs.
• Deliverability and suppression are Klaviyo’s once connected. Evident’s own suppression list stops applying to these sends.
• Disconnecting reverts to Evident sending directly, using whatever sequence steps and templates are configured.

Deferred: historical backfill, list synchronisation, and SMS-specific profile properties.