> ## Documentation Index
> Fetch the complete documentation index at: https://docs.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Populations (Segments)
Populations represent customer segments. The segmentation of your customer base into distinct groups based on common traits, demographics, transaction activity, behaviors, or needs allows for more precise marketing efforts. By curating content, products, and offers that cater to each segment's specific interests, you can boost conversion rates and encourage repeat purchases.
Other uses of populations can include targeting test accounts within dedicated segments or performing A/B testing.
This feature applies to logged in users.
Within **Home** > **Populations**, you can:
* [Create and edit populations](managePopulations)
* [View populations](managePopulations)
* [Delete populations](managePopulations)
## How This Feature Works
Customer segments can be imported from the API of your integrated BSS, CRM, or Subscriber Management system. You can also create populations in Editorial Management Interface (EMI).
**Note:** You can add recommendations for users based on their login status or active subscriptions by configuring [business rules](businessRulesAbout).
After you import or add populations, they can be applied to page programming. While creating or editing page programming, you can select one or more populations in the publication parameters.
**Use Case Example**
A Reseller wants to market content to a variety of users in addition to sports fans specifically.
The Reseller does the following:
1. Adds a population of sports fans
2. Creates **Discovery** page programming
1. Adds a zone that features various streaming products
* Applies a business rule linked to users who aren't logged in
2. Adds a zone that features sports products
* Applies a business rule linked to users who are logged in
3. Applies the population to the programming
## Population Flow
This flow outlines the process of integrating population data from the Reseller's API to display personalized content to storefront users:
1. The MarketONE extension layer gets the population ID from the Reseller's API.
The population ID becomes available in the MarketONE extension layer.
2. Storefront Gateway gets the population ID from the MarketONE extension layer and provides it to the Storefront UI.
3. The Storefront UI uses the population ID and the Editorial Management Interface (EMI) mapping to present personalized content to the user.
* **[Manage Populations (Segments)](managePopulations)**
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.