> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/segments/combining-segments.md).
# Combining Segments
Advanced customer segments can be created by combining two existing segments. This enables a more specific way of targeting by merging, intersecting, or comparing different customer groups.
1. In the [**Admin Portal**](https://admin.gobossit.com/), go to the **group level.**
2. Click on **Marketing.**
3. Navigate to **Segments**.
4. Click **New from Combine.**
5. Select **Segment A** and **Segment B** from your existing segments.
6. Choose the required operation to combine them.
7. Click **Continue** to generate the combined segment.
## Operation Types
### Union (A ∪ B)
Combines both segments. Includes customers who appear in Segment A, Segment B, or both.
> **Example:**
>
> **Campaign:** Brunch Menu Product Launch Campaign
>
> **Segment A:** Breakfast Customers - Customers who have ordered during breakfast time ranges.
>
> **Segment B:** Lunch Customers - Customers who have ordered during lunch time ranges.
>
> \
> Combining the segments through a union will give a list of customers who have ordered during either breakfast or lunch (or both). This combined segment can then be used to promote the brunch menu.
### Intersection (A ∩ B)
Finds common customers. Includes only customers who appear in both Segment A and Segment B.
> **Example:**
>
> **Campaign:** Lapsed VIP Customer Re-engagement Campaign
>
> **Segment A:** High Points - Customers with 1000+ loyalty points
>
> **Segment B:** Inactive Customers - Customers who haven't ordered in 30 days
>
> Getting the intersection of these segments would result to a list of customers who have high points but have stopped ordering. This combined segment can then be used in the campaign.
### Difference (A \ B)
Excludes Segment B from Segment A. Includes customers who appear in Segment A but not in Segment B.
> **Example:**
>
> **Campaign:** "We Miss You" Win-Back Campaign
>
> **Segment A:** Regulars - Customers with 5+ orders
>
> **Segment B:** Recently Active - Customers whose last order was in the past 60+ days
>
> Combining the segments by getting the difference of the segments will result to a list of customers who ordered frequently but haven't ordered recently. This combined segment can then be used to in the campaign.
### Difference (B \ A)
Excludes Segment A from Segment B. Includes customers who appear in Segment B but not in Segment A.
> **Example:**
>
> **Campaign:** Product Cross-Sell
>
> **Segment A:** Pizza Buyers - Customers who have ordered pizza products
>
> **Segment B:** Recently Active - Customers whose last order was in the past 30 days
>
> Combining these segment by getting the difference of the segments will result to a list of recently active customers who have never ordered pizza. This combined segment can then be used to promote the pizza menu.
---
# 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.bossithq.com/segments/combining-segments.md?ask=&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.
