> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/reviews/integrations/klaviyo-review-integration/creating-conditional-split-using-loyalty-and-review-properties.md).

# Creating conditional split using loyalty & review properties

This walkthrough shows how to create a Klaviyo flow that starts when a customer submits a Roadmap review, then routes people down different branches based on:

* whether they have a Roadmap Loyalty account (`roadmap_has_account`)
* their latest Roadmap review rating (`roadmap_latest_review_rating`)

The steps below follow the same order as the screencast: create a flow, confirm the trigger, then configure a Conditional split with loyalty + rating conditions.

{% stepper %}
{% step %}

#### Create the flow and name it

In Klaviyo, create or open the flow you want to update. In the screencast, the flow is named with today’s date and time so it’s easy to find later.
{% endstep %}

{% step %}

#### Set the trigger to “Roadmap: Review Submitted”

Open your flow’s Trigger

Click the **Trigger** card at the top of the flow canvas to open the trigger details panel.

![Klaviyo flow trigger panel showing the Roadmap: Review Submitted metric](https://content.gitbook.com/content/J8asLD4FVCFagK40xEr4/blobs/SF3mUJUJIWUDHR7kV4fs/frame_002.jpg)

### Choose the metric

Under **Trigger** → **Metric**, select **Roadmap: Review Submitted**.

This means **anyone who leaves a review** can enter the flow—whether they have a loyalty membership or not.

Review filters (optional)

If needed, use **Trigger filters** or **Profile filters** to narrow who enters the flow. In the screencast, the trigger is left broad so the segmentation happens in the split step.

In the trigger panel you can also set **Re-entry criteria**. Choose the option that fits your program (for example, whether someone should re-enter on every new review).
{% endstep %}

{% step %}

#### Add a Conditional split under the trigger

Insert a Conditional split

Click the **+** under the trigger card and add a **Conditional split**.

Then click the **Conditional split** card to open **Conditional split details**.

![Conditional split details panel open in Klaviyo with flow diagram and split settings](https://content.gitbook.com/content/J8asLD4FVCFagK40xEr4/blobs/cB19Tz93ne5pCgRTArHL/frame_001.jpg)
{% endstep %}

{% step %}

#### Configure the loyalty condition (has a loyalty account)

In the **Conditional split details** settings panel, build your first condition using the Roadmap loyalty property:

* **Properties about someone** → `roadmap_has_account`
* Operator: **is true**

What this means: If `roadmap_has_account` is **true**, the person has a Roadmap Loyalty account and will go down the **Yes** branch. If it’s **false**, they’ll go down the **No** branch.

Optional: Split by loyalty tier (instead of just “has an account”)

If you want to split by loyalty level (for example, Gold vs Silver), use the Roadmap loyalty tier property in your split rules. In Roadmap’s Klaviyo property list, the tier is available as:

* **Current tier name** → `person.roadmap_loyalty_current_tier_name`

![Roadmap Klaviyo properties table showing loyalty fields including Current tier name and Has Membership account](https://content.gitbook.com/content/J8asLD4FVCFagK40xEr4/blobs/nieobc9n3MNlkLfV85NJ/Screenshot_2026%2003%2010_at_12.17.21_PM.png)
{% endstep %}

{% step %}

#### Add the latest review rating condition

Now add a second rule so the split only routes people to **Yes** when they both have a loyalty account and left a strong rating.

Add an AND condition

Click **+ AND** to add another condition row.

Select the latest review rating property

Choose **Properties about someone** → `roadmap_latest_review_rating`.

![Conditional split settings in Klaviyo configuring roadmap\_latest\_review\_rating](https://content.gitbook.com/content/J8asLD4FVCFagK40xEr4/blobs/5Uw1HJxswiEtuvPCM7xZ/frame_004.jpg)

Set the comparison

Set the operator to **is greater than** and enter **3** (so ratings 4–5 go to **Yes**).

![Conditional split configured with roadmap\_latest\_review\_rating is greater than 3](https://content.gitbook.com/content/J8asLD4FVCFagK40xEr4/blobs/IsRAsCERGQukt65XAH9z/frame_005.jpg)

Roadmap updates **Latest review rating** as customers leave new reviews. Your flow will evaluate the split conditions at the time the person reaches the split step.

![Roadmap Klaviyo properties table showing Reviews tab and Latest review rating property](https://content.gitbook.com/content/J8asLD4FVCFagK40xEr4/blobs/ZhvLpjuoxmcuFhdzTfXK/Screenshot_2026%2003%2010_at_12.17.26_PM.png)
{% endstep %}

{% step %}

#### Save and use the Yes/No branches

Save your split

Click **Save** in the **Conditional split details** panel.

Add actions to each path

Use the **Yes** branch for customers who have a loyalty account and left a rating greater than 3 (for example, send a thank-you email or VIP offer).

Use the **No** branch for everyone else (for example, route to a different message or end the flow).

If you prefer more granular routing (e.g., “Has account?” first, then “Rating > 3?”), create **two Conditional split** steps in sequence instead of combining rules in a single split.

If your flow is live, changes to the trigger or split rules can immediately affect who receives messages. Consider testing in **Draft** first and using **Preview** where available.
{% endstep %}
{% endstepper %}

\\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.roadmap.so/reviews/integrations/klaviyo-review-integration/creating-conditional-split-using-loyalty-and-review-properties.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.