> For the complete documentation index, see [llms.txt](https://docs.bird.com/taxi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/taxi/connectors/oracle-responsys-connector/setting-up-segmentation-for-responsys.md).

# Setting up segmentation for Responsys

The segmentation features in Taxi for Email allow modules within an email to be aimed at particular audiences from within our email editor. Filtering to see what recipients in different groups will receive, can be performed in real time while building the email.

[Segment sets](/taxi/dynamic-content-segmentation-and-personalisation/segmentation/creating-and-managing-segment-sets.md) and [single segments](/taxi/dynamic-content-segmentation-and-personalisation/segmentation/creating-and-managing-single-segments.md) are defined in the segmentation section of your Taxi account. These enable you to set up rules to control which content is sent to which groups of people in your data. They are then applied to any of the modules in your template to give you complete control of the specific content that’s sent to your customers.

This segmentation is mapped by the connector to Responsys conditional code snippets, and this code is run when the email is sent. This ensures each recipient gets the content selected for them.

Responsys uses liquid for their conditional logic. They use a lot of shopify’s standard of liquid but not all of it is supported. Have a look at their documentation to find out more:

[https://www.Responsys.com/docs/user\_guide/personalization\_and\_dynamic\_content/liquid/](https://www.braze.com/docs/user_guide/personalization_and_dynamic_content/liquid/)

Once segments are defined it is possible to use them in the Taxi editor and to preview content for each segment.

Finally, to be able to export code through the connector, the RPL for segments must be added. This RPL is set per connector. This means you can use different RPL between environments, and thus you can work with different data structures and formats if needed.

Code for segments is entered through the segmentation settings.

![](https://taxi-for-email.intercom-attachments-7.com/i/o/382993241/dc0a1a6f5d88d88afa92d434/JdqflI2aApG8NyTNtXHTa6ybxJILg0hZN1FnFEMy_OuB-RscOnIBRmmbPWsBeDXj8LNwxv7ASbJ57YvW5ECuEVcBC3GH7QlBogoG-v3EEgztih1JXknsRch67ljuMY441Ld5pEYj%3Ds0)![](https://taxi-for-email.intercom-attachments-7.com/i/o/382993253/dd3d47ab4cd39540a3b48fd9/2d_v3EP19cEFmgwH1QCoSBR0vly0lwzYLdyjsRQYu6mJncjnSMp9-ryV1au0110btmvnB2ceY2ZQRzqRIW_ZTYFmmORGQhezayquUi5-nYpx2HX5rp5rrw85jgvFLpDQ4zhVfvT9%3Ds0)


---

# 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 dynamically by asking a question.

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

```
GET https://docs.bird.com/taxi/connectors/oracle-responsys-connector/setting-up-segmentation-for-responsys.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.