# Media and streaming

This playbook shows how to set up Pushwoosh for the app of a news publisher, a magazine, or a video or audio streaming service, from identifying readers to launching [news alerts](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/reading-and-watching/#news-alerts) and journeys for topics, unfinished episodes, subscriptions, and win-back. In this playbook, a reader is anyone who reads, watches, or listens to your content.

Set up Pushwoosh in seven stages, in this order:

1. Set a [User ID](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#identify-readers-by-user-id) for each reader who logs in, so Pushwoosh recognizes the same reader on every device.
2. Choose the [events to track](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#set-up-the-events) to record what readers do in the app: read articles, follow topics, watch episodes, and hit the paywall.
3. Optional: store reader data, such as the topics a reader follows, in [tags](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#store-reader-data-in-tags).
4. Group readers who match your conditions in [segments](/tutorials/industry-playbooks/media-and-streaming/build-the-segments/), for example readers who follow a topic or readers who stopped reading.
5. Ask for push permission at the right moment, set delivery rules in **Settings** → **Message delivery settings**, and set up a control group. See [Prepare for communication](/tutorials/industry-playbooks/media-and-streaming/prepare-for-communication/).
6. Send news alerts to the readers who follow a topic, and send messages automatically with [journeys](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/) when a reader does something in the app or joins a segment.
7. [Test each journey](/tutorials/industry-playbooks/media-and-streaming/launch-and-measure/), then read its statistics and measure results.

To start with less, follow [Minimum setup to start messaging readers](#minimum-setup-to-start-messaging-readers).

## Prerequisites

<Aside type="caution" icon="setting" title="Developer assistance needed">
Some steps of this playbook are changes in your app's code. See [What your developers need to do](#what-your-developers-need-to-do).
</Aside>

* An [application in your Pushwoosh account](/product/first-steps/start-with-your-project/create-your-project/), with the [SDK integrated](/developer/first-steps/integrate-pushwoosh-sdk/) (the Pushwoosh code library inside your app) so devices register automatically.
* A [role](/product/account-management-and-security/multi-login-accounts/#available-permissions) in the Pushwoosh account with **Modify** for **Applications**, to create events, segments, and journeys and change settings, and **Send** for **Messages**. To look up test readers in **User explorer**, the role also needs **Personal data**.
* [Email](/product/messaging-channels/emails/) set up as a channel, only for the journeys that list email under **Needs**. Most journeys in this playbook use push and in-app messages.

<Aside type="note" title="Subscriptions sold through the App Store or Google Play?">
If readers subscribe in the app through the App Store or Google Play, Pushwoosh can receive the subscription status changes from the stores as events, such as a new subscription or a cancelled renewal. You use them in place of your own subscription events. See [Track subscriptions from the stores](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#track-subscriptions-from-the-stores).
</Aside>

This playbook is written for an app with the Pushwoosh SDK. If readers also come to your website with the [Web SDK](/developer/pushwoosh-sdk/web-push-notifications/web-push-sdk-30/), events, tags, User IDs, web push, journeys that start on an event, and the App Inbox work the same. Three things differ:

* Journey in-app messages reach only the app.
* The website does not send `PW_ApplicationOpen`, so filters on it count only app readers.
* Journeys that start from a segment take in only browsers where the reader allowed notifications.

## What your developers need to do

Hand your developers this list, so they can ship it in one release:

* [Set the User ID at login](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#identify-readers-by-user-id).
* [Send the events](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#send-the-events-from-the-app) your journeys need.
* If you sell subscriptions, [send them as an event with the amount and currency](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#track-revenue-from-subscriptions), and [pass the reader's ID with each store purchase](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#track-subscriptions-from-the-stores).
* If your app asks readers for consent to data processing, [start the SDK only after consent](/tutorials/industry-playbooks/media-and-streaming/prepare-for-communication/#start-the-sdk-after-the-reader-gives-consent).
* [Move the push permission request](/tutorials/industry-playbooks/media-and-streaming/prepare-for-communication/#ask-for-push-permission-at-the-right-moment) out of the first launch.
* Handle [deep links](/product/messaging-channels/push-notifications/advanced-push-features/deep-linking/) to the article, episode, topic, and subscription screens, which the alerts and journeys open from pushes.

## Minimum setup to start messaging readers

If you do not need all seven stages yet, this minimum setup covers two basic tasks: sending news alerts and winning back readers who stopped reading. Complete these steps:

1. Ask your developers to call `setUserId` on login. Readers who never log in still get messages on their device. See [Identify readers by User ID](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#identify-readers-by-user-id).
2. Ask your developers to send the `Content read` event. See [Set up the events](/tutorials/industry-playbooks/media-and-streaming/collect-reader-data/#set-up-the-events).
3. Ask your developers to move the push permission request to a later moment, for example after the reader opens the second article. On iOS, a reader who declines the prompt on the first launch can't be asked again. 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).
4. Set the [delivery rules](/tutorials/industry-playbooks/media-and-streaming/prepare-for-communication/#set-delivery-rules-before-you-message-readers), and decide which [message type](/tutorials/industry-playbooks/media-and-streaming/prepare-for-communication/#choose-how-news-alerts-follow-the-delivery-rules) your news alerts use.
5. Build the [At-risk readers](/tutorials/industry-playbooks/media-and-streaming/build-the-segments/#at-risk-readers) segment. It fills 14 days after `Content read` events start to arrive. To start sooner, use `PW_ApplicationOpen` instead of `Content read` in its filters.
6. Create the content for the news alerts and the win-back journey, as listed under **Content to prepare** in each recipe.
7. Send [News alerts](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/reading-and-watching/#news-alerts) to all readers, and launch [Win-back for inactive readers](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/subscriptions-and-win-back/#win-back-for-inactive-readers).

Add the other segments and journeys later, as their events start arriving.

## What next

To add more journeys, see these guides:

* [Set up a retention campaign](/tutorials/product-guides/lifecycle-marketing-campaigns/how-to-set-up-a-retention-campaign-in-pushwoosh/)
* [Set up a user engagement campaign](/tutorials/product-guides/lifecycle-marketing-campaigns/how-to-set-up-a-user-engagement-campaign-in-pushwoosh/)
* [Create a re-engagement campaign](/tutorials/product-guides/lifecycle-marketing-campaigns/how-to-create-a-re-engagement-campaign-in-pushwoosh/)
* [Run A/B/n tests in journeys](/tutorials/product-guides/how-to-create-campaigns-in-pushwoosh/how-to-abn-test-customer-journeys/)