> 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/acoustic-ibm-silverpop-connector/setting-up-segmentation-for-the-acoustic-connector.md).
# Segmentation in Taxi
[Segment sets](https://docs.messagebird.com/taxi/Dynamic%20content,%20segmentation%20and%20personalisation/Segmentation/creating-and-managing-segment-sets) and [single segments](https://docs.messagebird.com/taxi/Dynamic%20content,%20segmentation%20and%20personalisation/Segmentation/creating-and-managing-single-segments) are defined in the segmentation section of your Taxi account. These allow you to set up rules to control which content is sent to the groups of people within this segmentation. They are then applied to any of the modules in your Email Design System to give you complete control of the specific content that’s sent to your customers.
This segmentation is mapped by the connector using dynamic content rules, and this is run when the email is sent. This ensures each recipient gets the content selected for them.
Once segments are defined it is possible to use them in the Taxi editor and to preview content for each segment.
To be able to export code through the connector, the code for segments must be added. The rules are set per connector. This means you can use different rules between environments, and you can work with different data structures and formats in your different environments.
Code for segments is entered through the segmentation settings.\
With the Acoustic connector, you are able to select the contact source you’d like to use. Contact sources are [databases](https://help.goacoustic.com/hc/en-us/articles/360042857094-Create-a-database#:~:text=A%20database%20is%20a%20starting,in%20Acoustic%3A%20flexible%20and%20restricted), [contact lists](https://help.goacoustic.com/hc/en-us/articles/360043345193-Contact-lists), and [queries](https://help.goacoustic.com/hc/en-us/articles/360042859134-Queries#:~:text=A%20query%20is%20a%20set,when%20executed%2C%20creates%20a%20list.\&text=The%20query%20functionality%20enables%20you,contacts%20based%20on%20targeting%20criteria).
Once you’ve selected this you can choose from different criteria within the contact source, for example, gender or location. You can then input the value (group of recipients) you want to map the content to. For example ‘gender = male’ or if ‘location = London’
The criteria is selected by a dropdown, which can make it much easier to set up your segment sets and match it to your data, as you won’t have to copy and paste in the rules and risk adding in the incorrect code.
\
With this connector, you can also control the type of rule you want to set up. You can set it up so the value matches the criteria, e.g. if gender = male. Or you can do the opposite if you want the value not to match the criteria e.g. if gender does not = male. If the values are numerical you can also have greater than or less than rules e.g. if age is greater than 25.
Here is a full list of operators you can use:
| Equals |
| ------------------- |
| Does not equal |
| Less than |
| Greater than |
| Greater than equals |
| Is empty |
| Is not empty |
| Is in list |
| Is not in list |
| Is between |
| contains |
| Does not contain |
| Starts with |
| Does not start with |
| Ends with |
| Does not end with |
\
You can also add multiple conditions to your segments using the rule builder when setting up Acoustic segmentation. You can use and/or to create more complex rules to get the most out of the data you have in Acoustic.
This can be used with both segment sets and single segments.
When you segment a module in Taxi, you can see multiple versions of the module within the editor depending on how many segments you’re sending to.
For example:
When you export out of Taxi, instead of the two modules with dynamic script around those modules like you get with some other connectors, you'll see a bit of code which is linked to a dynamic content rule in Acoustic.
For example:
This is what it looks like in Acoustic:
When you see this code in Acoustic you're able to edit it, and when you do that you can see the rule that's been applied.
In this example, you can see it's using the criteria if gender = female to control who sees the content.
---
# 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/acoustic-ibm-silverpop-connector/setting-up-segmentation-for-the-acoustic-connector.md?ask=
```
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.