# How to use the Yes/No Split feature?

Set up complex flows in your **Automations** and split users based on a new targeting rule throughout the journey! Let's go through the steps together :sparkles:

{% stepper %}
{% step %}

## Add a trigger event and a Yes/No Split  <a href="#h_7834f5c620" id="h_7834f5c620"></a>

Select your trigger event, then add a Yes/No Split at any step of the omnichannel trigger automation.

To do so, simply click on the **+** button and select **Yes/No Split:**

<figure><img src="/files/bhvEViI1GaugmG6b6iIK" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Select targeting rules

Click on the split you created, give it a title, and select the targeting rules of your choice.&#x20;

The Yes/No Split will leverage all Profiles data to split the workflow into 2 branches:

* Yes, people match the rules;
* No, they don’t.

<figure><img src="/files/3ylfapwQCysy82rVmzaH" alt=""><figcaption></figcaption></figure>

In your targeting rules, you can also use [Segments](https://doc.batch.com/guides-and-best-practices/profiles/how-to-create-and-use-a-segment), or [Audiences](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/audiences).

{% hint style="success" %}
💡 Be aware that entry event information cannot be used as split targeting rules.
{% endhint %}
{% endstep %}

{% step %}

## Filter on trigger events attributes

In addition to the profile targeting block, you can filter on trigger event attributes directly within the Yes/No split.&#x20;

It allows you to specify conditions on the attributes of the exact event occurrence that initiated the user's journey in the Trigger Automation:

<figure><img src="/files/GgP2ejHupuUt2q1Rf2KY" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
Currently, complex attributes like **arrays and objects are not supported** for filtering in the trigger event query block.
{% endhint %}

{% hint style="info" %}
The operator between the two query blocks (”Segmentation” ie profile targeting and trigger event filtering) is always `AND`. This means a user must match both the profile query and the trigger event query to follow the "Yes" branch.\
\
In addition to this, the operator between the different filtering conditions for the trigger event is always the same, either `AND` or `OR`.
{% endhint %}
{% endstep %}

{% step %}

## Add messages and/or more splits

By clicking on the **+** button again, you can add a message or another split:

<figure><img src="/files/Ck7xx2XjcwYeXaQ8Grgi" alt=""><figcaption></figcaption></figure>

🔍  With this feature, automations can get a lot bigger: to get a better overview, use the **mini-map** at the bottom-left corner of your screen to navigate and zoom in and out in the automation:

<figure><img src="/files/4SfyigNSKPTPL6KAiUTr" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

You are now ready to create your own journey using the Yes/No Split feature :rocket:


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.batch.com/guides-and-best-practices/orchestration/how-to-use-the-yes-no-split-feature.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.