# Build the segments

A [segment](/product/audience-data-and-segmentation/segmentation/) is a saved group of readers who match your conditions, for example readers who follow a topic or readers who stopped reading. You can send a news alert, an in-app message, or an email to a segment, or use it in a journey to decide who enters and which message each reader gets. Build the segments before the journeys.

## How to create segments

Create each segment in **Audience** → **Segments** with the filters from the tables below.

There are several ways to build a segment. This page covers segments by events and by tags. You can also build segments from:

* [Existing segments](/product/audience-data-and-segmentation/segmentation/create-segments/by-existing-segments/)
* [Anniversary dates](/product/audience-data-and-segmentation/segmentation/create-segments/anniversary-segments/)
* [User ID](/product/audience-data-and-segmentation/segmentation/create-segments/by-user-id/)
* [An imported file](/product/audience-data-and-segmentation/segmentation/create-segments/by-import/)
* [Geolocation](/product/audience-data-and-segmentation/segmentation/create-segments/by-geo/)
* [A description in plain words, with AI](/product/audience-data-and-segmentation/segmentation/create-segments/build-segments-with-ai/)

For all the ways, see [How to create segments](/product/audience-data-and-segmentation/segmentation/create-segments/).

<Aside type="tip" title="Let AI Assistant create the segments">
[AI Assistant](/product/pushwoosh-ai/ai-assistant/) can create the segments from this page in your application. Send it the link to the page and ask it to create them. It creates them right away. When it is done, open **Audience** → **Segments** and check the result.
</Aside>

## Segments by events

These segments are built from the main events that readers trigger in the app. They are examples: change the days or build your own segments.

Choose the days to match how often your readers come back. A daily news app needs shorter windows than a streaming service that releases a new episode every week.

To set the filters, see [Build segments by events](/product/audience-data-and-segmentation/segmentation/create-segments/by-events/). At-risk readers and Lapsed readers start the win-back journeys from [Build the journeys](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/). Use Active readers and Paywall hitters for one-time campaigns or to leave readers out of a journey.

<span id="active-readers" />
<span id="paywall-hitters" />
<span id="at-risk-readers" />
<span id="lapsed-readers" />

| Segment | Filters | Use it to |
| --- | --- | --- |
| Active readers | <ul><li>`Content read` exactly or more, 3 times, during the last 7 days</li></ul> | Tell regular readers apart, for example to offer them a subscription or to leave them out of a win-back campaign |
| Paywall hitters | <ul><li>`Paywall viewed` exactly or more, 1 time, during the last 7 days</li><li>AND `Subscription started` never, during the last 7 days</li></ul> | Send a subscription offer to readers who reached the paywall and did not subscribe. The journey for this case starts on the event, so use the segment for a one-time campaign, for example a weekend offer. See [Paywall follow-up](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/subscriptions-and-win-back/#paywall-follow-up) |
| At-risk readers | <ul><li>`Content read` never, during the last 14 days</li><li>AND `Content read` exactly or more, 1 time, during the last 90 days</li></ul> | Win back readers who read before and have been away for two weeks. Feeds the [Win-back for inactive readers](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/subscriptions-and-win-back/#win-back-for-inactive-readers) journey |
| Lapsed readers | <ul><li>`Content read` never, during the last 60 days</li><li>AND `Content read` exactly or more, 1 time, during the last 365 days</li></ul> | Win back readers who have been away for two months, with a stronger reason to return than for At-risk readers. The second filter leaves out readers with nothing read on record. Feeds a copy of the [Win-back for inactive readers](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/subscriptions-and-win-back/#win-back-for-inactive-readers) journey |

If readers subscribe through the App Store or Google Play, use `PW_SubscriptionStart` in Paywall hitters instead of `Subscription started`, or both with OR.

### Segments that start empty

The At-risk readers and Lapsed readers segments find readers who read before and then stopped, so they need reading history. Right after you set up the `Content read` event, they are empty:

* At-risk readers start to fill 14 days after the first events arrive.
* Lapsed readers start to fill after 60 days.

To fill these two segments sooner, use the `PW_ApplicationOpen` event instead of `Content read` in their filters. The segments then count app opens, so they also take in readers who opened the app but read nothing.

<span id="filters-with-never" />

### Why segments with never miss some readers

A filter with **never** takes in only devices that have a push token. A device gets the token when the app asks for push permission, whatever the reader answers. Until the app asks, the reader is not in such segments as Paywall hitters, At-risk readers, and Lapsed readers.

To include readers earlier, ask your developers to show the push permission request earlier. See [Ask for push permission at the right moment](/tutorials/industry-playbooks/media-and-streaming/prepare-for-communication/#ask-for-push-permission-at-the-right-moment).

## Segments by tags

These segments are built from reader tags. They are examples: change the values or build your own segments. To set the filters, see [Build segments by tags](/product/audience-data-and-segmentation/segmentation/create-segments/by-tags/).

Most of them need the tags from [Store reader data in tags](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#store-reader-data-in-tags).

<span id="readers-without-push" />
<span id="topic-followers" />
<span id="subscribers" />

| Segment | Filter | Use it to |
| --- | --- | --- |
| Readers without push | `Push Alerts Enabled` is false | Find readers who declined or never allowed notifications, for example to ask them again with an in-app message or to reach them by email |
| Topic followers, for example Politics followers | `followed_topics` in `politics` | Send a news alert only to the readers who follow the topic. Build one segment for each topic you send alerts about. Feeds [News alerts](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/reading-and-watching/#news-alerts) |
| Subscribers | `is_subscriber` is true | Leave subscribers out of subscription offers, or send them news about content for subscribers |

A reader who follows several topics is in each of their segments. To send one alert about two topics, choose both values in the **in** filter, and a reader who follows both gets the alert once.