> ## Documentation Index
> Fetch the complete documentation index at: https://storekit.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Review Events

> How storekit feedback requests and submitted reviews reach Klaviyo as Review Requested, Review Submitted, Positive/Negative Review Submitted and Reviewed Product events, and how to use them.

If you use storekit's built-in feedback requests, each step of the review is also sent to Klaviyo. That lets you send the review request from Klaviyo instead of storekit's email, thank happy customers, recover unhappy ones, and segment on how people rate specific dishes.

## Turn On Feedback

Review events depend on the store's feedback settings, which are separate from the Klaviyo page.

<Steps>
  <Step title="Open feedback settings">
    Go to **Stores** → your store → **Settings** → **Feedback**.
  </Step>

  <Step title="Enable feedback">
    Turn on **Enable feedback**. Set **Notification delay** to how long after the order's estimated ready time the request should go out (the default is 60 minutes).
  </Step>

  <Step title="Decide who is asked">
    Leave **Opt-in only** off to ask every customer with an email address, or turn it on to ask only customers who ticked the marketing opt-in at checkout.
  </Step>
</Steps>

<Note>
  storekit always sends its own review request email (and a push notification to app users) when feedback is enabled; there is no setting to turn that email off while keeping the Klaviyo event. If you also send a request from Klaviyo, the customer receives two — see [Send the review request from Klaviyo](#send-the-review-request-from-klaviyo) below.
</Note>

## The Review Lifecycle

| When | Klaviyo event | Sent to |
| - | - | - |
| storekit sends the feedback request (estimated ready time + **Notification delay**) | **Review Requested** | The customer's profile, with `ReviewUrl` |
| Customer submits the review form | **Review Submitted** | The customer's profile, with the overall rating and comments |
| At the same time | **Positive Review Submitted** (rating 4 or 5) **or** **Negative Review Submitted** (rating 1 to 3) | Same profile, same properties |
| At the same time, once per dish rated | **Reviewed Product** | Same profile, one event per dish with its own rating and comment |

The 4-star threshold for positive versus negative is fixed; it cannot be changed in the dashboard.

Every review event carries `ReviewId`, `OrderId`, `OrderCode`, `Currency`, `VenueName` and `VenueSlug`. Full property lists are in the [Event Reference](/docs/guides/integrations/marketing/klaviyo/event-reference#review-events).

### Profile properties

Alongside the events, storekit updates three custom properties on the customer's profile so you can segment without querying event history:

| Property | Set by |
| - | - |
| `StoreKit Last Request Sent Date` | **Review Requested** |
| `StoreKit Last Review Date` | **Review Submitted** |
| `StoreKit Last Review Rating` | **Review Submitted** |

Only customers who gave an email at checkout receive review events. A customer is asked at most once per store in any 24-hour period, so a second order the same day does not produce a second **Review Requested**. Partial or abandoned review forms are not sent; the review must be completed.

## Send the Review Request From Klaviyo

Build a flow triggered by **Review Requested** that sends your own email or SMS, and use `{{ event.ReviewUrl }}` as the button link. The link opens the storekit review form for that order, already tied to the customer, so the review still flows back into storekit and Klaviyo.

Because storekit's own request email cannot be switched off, use this for a **follow-up** rather than a duplicate: for example, a time delay of one day, then a conditional split on **Review Submitted** since the trigger, and send the Klaviyo reminder only to customers who have not reviewed.

## Flows Worth Building

* **Thank positive reviewers** — trigger on **Positive Review Submitted**, send a thank-you with a link to leave a public Google review or a reorder incentive.
* **Recover negative reviews** — trigger on **Negative Review Submitted**, notify your team (Klaviyo can send an internal notification) and send the customer an apology with a voucher. Include `{{ event.ReviewContent }}` in the internal email so the team sees the comment.
* **Dish-level follow-up** — trigger on **Reviewed Product** with a filter `Rating is less than 3`, and use `{{ event.ProductName }}` and `{{ event.Reasons }}` to act on a specific dish.
* **Segment lapsed reviewers** — a segment of profiles where `StoreKit Last Review Rating` is 5 and **Placed Order** count is at least 3 gives you your advocates.

Worked examples with property names are on [Flows to Build](/docs/guides/integrations/marketing/klaviyo/flows#review-flows).

## Related

<CardGroup cols={2}>
  <Card title="Customer Feedback" icon="star" href="/docs/guides/marketing/customer-feedback">
    How storekit's feedback requests and review form work
  </Card>

  <Card title="Event Reference" icon="table-list" href="/docs/guides/integrations/marketing/klaviyo/event-reference#review-events">
    Every property on the review events
  </Card>
</CardGroup>


## Related topics

- [Klaviyo Event Reference](/docs/guides/integrations/marketing/klaviyo/event-reference.md)
- [Troubleshooting Klaviyo](/docs/guides/integrations/marketing/klaviyo/troubleshooting.md)
- [Flows to Build](/docs/guides/integrations/marketing/klaviyo/flows.md)
- [Klaviyo](/docs/guides/integrations/marketing/klaviyo/overview.md)
- [Klaviyo for Native Apps](/docs/guides/integrations/marketing/klaviyo/native-apps.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.