> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.quortex.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Build your audience tree

The **Quortex Switch audience tree** determines which CDN each defined audience segment is routed to. To build this tree, you need to add **sub-segments** that refine your audience definitions.
You can create these sub-segments using either the **UI** or the **API**.
---

### **Available Segment Types**
Quortex Switch supports four types of audience segmentation:
* 🌍 **Geolocation**
* 🌐 **Network (ASN)**
* 📱 **Device Type**
* 🔁 **Streaming Protocol (HLS or DASH)**
![Segments choice](https://storage.crisp.chat/users/helpdesk/website/-/9/8/4/5/9845223dbfb4e800/segments_ca95ir.png =714xauto)
Each segment can have its own **CDN prioritization and balancing strategy**.
---

### **Geolocation-Based Segment**
This segment defines the audience based on user location, using a list of **regions** (e.g., Europe, Asia-Pacific) and/or **countries**.
✅ **Recommended use**: when CDN performance or pricing varies by region.

![Regions/Countries selection](https://storage.crisp.chat/users/helpdesk/website/-/9/8/4/5/9845223dbfb4e800/geo-segment_50usmq.png =490xauto)
📌 **Notes**:
* Multiple geo segments can be **chained** or **parallelized** to refine targeting.
* Geo segments must be added **before all other segment types**.
---

### **Network-Based Segment (ASN)**
This segment targets users based on the **network** they are connected to, identified by their **ASN**.
✅ **Recommended use**: to optimize CDN delivery for specific ISPs or network providers.
![Network segment](https://storage.crisp.chat/users/helpdesk/website/-/9/8/4/5/9845223dbfb4e800/network-segment_srwac5.png =653xauto)
📌 **Notes**:
* You can add multiple ASNs to a segment.
* A network segment can be added in a **parallel branch**, but **not as a sub-segment** of another network segment.
* If added **under a geo segment**, the available ASNs will be **filtered** based on the selected region.
---

### Device Type Segment
This segment targets users based on the **device** they are using (e.g., desktop, mobile, smart TV, Android).
✅ **Recommended use**: when a CDN is optimized for specific devices (e.g., 4K delivery to TVs) or has limitations with certain platforms.
### ![Device type segment](https://storage.crisp.chat/users/helpdesk/website/-/9/8/4/5/9845223dbfb4e800/device-type-segment_7g2cu9.png =403xauto)

📌 **Notes**:
* Device segments can be added in **parallel branches**, but **not as sub-segments** of other device segments.
---

### **Protocol-Based Segment**
This segment splits the audience based on the **streaming protocol** used: **HLS** or **DASH**.
✅ **Recommended use**: when a CDN supports only one protocol or performs better with a specific one.
![Protocol segment](https://storage.crisp.chat/users/helpdesk/website/-/9/8/4/5/9845223dbfb4e800/protocol-segment_lh571l.png =220xauto)
📌 **Notes**:
* Since there are only two protocols, **both branches are automatically created** to split the audience accordingly.