How to send review requests through Klaviyo

Why send review requests from Klaviyo at all?

If your newsletters, abandoned-cart emails and order updates already go out from Klaviyo, a review request sent by another tool stands out. It looks different, it comes from a different address, and it has its own unsubscribe list. Moving it into Klaviyo puts every message to a customer in one place, with one design and one sending reputation.

The price is that two systems now share one job. Your reviews app knows the order, the products and whether the customer already reviewed them. Klaviyo knows how to send and when the customer last heard from you. The setup works when you are clear about which one decides what.

How does a Klaviyo review request flow work?

It runs in three steps. When an order is due a request, your reviews app sends Klaviyo an event under a fixed name, carrying the customer's email address and the order's data. In Klaviyo you build a flow whose trigger is that event, so every new event puts the customer into the flow. The flow then sends an email you design in Klaviyo's editor, filled in from the event's data.

Judge.me describes exactly this. Its article on Klaviyo review requests, updated on 2 July 2026, says it sends an event called “Eligible for Judge.me Review Requests” after fulfilment and that you build the flow on it. Loox's article, dated 1 June 2022, describes picking Klaviyo under “Send via” in its timing settings. Klaviyo also sells its own reviews product, and its help centre says Klaviyo Reviews is billed separately from its email and SMS plans.

Klaviyo's help page on flow triggers confirms the rule that makes this possible: any event that reaches Klaviyo through an integration or its API can trigger a flow, while performance metrics such as Opened Email and Clicked Email cannot.

Who decides when the review email goes out?

Decide this before you build anything, because it is where most flows go wrong. If your app records the event when the order is fulfilled and your flow also waits 14 days, the wait counts once. If your app already waits a week before recording the event and you add another 14 days in Klaviyo, the customer hears from you three weeks after delivery, long after the excitement has gone. Our article on when to send a review request covers which wait suits which product.

Pick one place for the delay and set the other to zero. Do the same for reminders: if the app records a separate reminder event, do not add a second email to the first flow, or a customer who never answers gets three messages instead of two.

Make sure the app stops sending its own email once Klaviyo takes over. A customer who gets the same request twice in a day, once from each system, is more likely to unsubscribe than to review.

What should the review request event carry?

Everything the email needs, so you never have to look anything up inside Klaviyo. At a minimum that is the store name, the order number, and for each product its name, its image and a link to the review form for that product. Star links are worth having as well: five links per product, each opening the form with that rating already picked, so the customer's first tap is the rating itself.

Add the link that stops review emails. If the only way out is the general unsubscribe link at the bottom of every Klaviyo email, a customer who is tired of review requests has to leave all your email to get rid of them. A separate “no more review emails” link lets them stop just this kind of message, and the app has to respect it on its side. For the wording of the email itself, our review request email templates work the same in Klaviyo's editor.

What should you test before the flow goes live?

Send one test event and follow it all the way. Check that the flow picks it up, that every variable fills in, that each star link opens the right product with the right rating, and that the opt-out link works. Then submit a review through the email and make sure it lands in your reviews dashboard, not only in Klaviyo's activity log.

Watch for two quiet failures. Klaviyo's Events API documentation describes a backfill flag that stops flows from firing for historical events, so a batch of past orders sent that way will never email anyone. And trigger filters read the event's data, so a filter on a property your app never sends can keep every customer out of the flow.

What does Formgong do with Klaviyo?

On the Sending tab of a review site you can pick Klaviyo as the sender. Formgong then sends nothing itself. For each email it would have sent, it records an event in your Klaviyo account, named Formgong Review Request, Formgong Review Reminder, Formgong Review Coupon or Formgong Review Edit Link, and your flow on that event sends it. Each event carries the store name, the order number, every product with its image, five star links and a review link, the link to a survey if you run one, and the link that stops review emails; the Sending tab lists the variables to paste. Formgong still decides when each event goes out: the delay and send hour you set, one reminder only for products not yet reviewed, a hold while the buyer is still waiting for your answer to a question, and the opt-outs and bounces it already knows about. This works on every Formgong plan. Loox's Klaviyo article from June 2022 put Klaviyo sending on its higher plans of that time, and its pricing page today lists the Klaviyo rows without saying in words which plans include them, so check before you pick an app for this.

What Formgong does not do with Klaviyo matters as much. It sends no event back when a review is written, which Judge.me's article says it does with “SubmittedReview”. It has no SMS. Shopify and Wix orders cannot reach it directly yet; orders come from the WooCommerce plugin, the API or a CSV. Separately, any Formgong form can add visitors who agree to a Klaviyo list, as the email lists docs explain, and our importer reads a Klaviyo Reviews export. No review site uses the Klaviyo sender yet: on 3 November 2026, 0 of 12 review sites had chosen it, and all 14 buyer emails logged in the last 30 days went through Formgong. Our demo shop Glyna sends the same way, and its store notice tells buyers that Formgong will email one review request and, if they do not reply, one reminder. The review emails docs describe the Sending tab.

Do you send review requests from Klaviyo?

If you have set up a review flow in Klaviyo, with Formgong or any other app, tell us what tripped you up at support@formgong.com. We would rather fix the hard parts than describe them.