# Reading and watching

These recipes cover readers who already read and watch: news alerts about the topics they follow and a reminder about an episode they did not finish. Before you build them, read the [best practices for every journey](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/#best-practices-for-every-journey).

## News alerts

* **Use it when:** your newsroom publishes a story that readers of a topic should hear about now.
* **Starts when:** an editor sends the alert.
* **What it does:** sends one push to the readers who follow the topic, or to all readers, and keeps a copy in the App Inbox for readers who miss the push.
* **Content to prepare:** a push preset with the headline, a deep link to the article, and, if you like, the article's image.
* **Needs:** the [Topic followers](/tutorials/industry-playbooks/media-and-streaming/build-the-segments/#topic-followers) segment for an alert about one topic, which needs the `followed_topics` tag. For the copy in the App Inbox, the [Message Inbox](/product/messaging-channels/message-inbox/) in your app.

A news alert is a [one-time push](/product/messaging-channels/push-notifications/send-push-notifications/one-time-push/), not a journey, because it goes out once, at the moment the editor chooses:

1. Open the one-time push form. See [One-time push](/product/messaging-channels/push-notifications/send-push-notifications/one-time-push/).
2. Select the push preset with the headline, or click **Create new** and write it, for example: "Parliament passes the budget: what changes for you."
3. Choose the message type: **Marketing message** or **Transactional message**.

   The type decides whether the alert follows frequency capping, silent hours, and the control group. See [Choose how news alerts follow the delivery rules](/tutorials/industry-playbooks/media-and-streaming/prepare-for-communication/#choose-how-news-alerts-follow-the-delivery-rules).
4. Turn on **Save message to Inbox**, so readers who dismiss or miss the push, or who have not allowed notifications, find the story in the App Inbox. In **Remove from Inbox**, set 1 day.
5. Click **Next** to go to the **Audience** step.
6. Choose **Send to segment** and select the topic segment, for example Politics followers. For news that every reader needs, choose **Send to all subscribers**.
7. Click **Next** to go to the **Sending time** step.
8. In **Sending options**, set **Time to Live** to 1 hour or 3 hours. A reader whose phone is offline when you send then doesn't get the alert hours later, when the news is old.

   <img src="/industry-playbooks-media-and-streaming-8.webp" alt="Sending options of the one-time push form with Time to Live set to 1 hour"/>

9. Choose **Send immediately**.
10. Click **Next** and, on the **Review** step, check the segment, **Save to Inbox**, and **Time to live**.
11. Click **Send now**.

A news alert has no conversion goal. To see how readers respond, open its statistics in the list of one-time messages.

To send the same alert in several languages, add the languages to the preset. See [Personalize the content](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/#personalize-the-content).

## Continue watching

* **Use it when:** a reader starts an episode of a series and does not finish it.
* **Starts when:** a reader starts an episode (`Episode started`).
* **What it does:** waits 1 day for the reader to finish an episode. If none is finished, sends a push that names the series, or an in-app message to readers without push.
* **Content to prepare:** a push preset with a deep link to the episode screen and a placeholder for the series name, and an in-app template with a general reminder.
* **Needs:** the `Episode started` and `Episode completed` events, with `series_name` on the first one.

<img src="/industry-playbooks-media-and-streaming-4.webp" alt="Continue watching journey: Episode started entry, 1-day Wait for Trigger on Episode completed, Reachability check, push or in-app"/>

1. On the journey canvas, add a [Trigger-based entry](/product/customer-journey/journey-elements/entry-elements/trigger-based-entry/) on `Episode started`.
2. Add a [Wait for Trigger](/product/customer-journey/journey-elements/flow-controls/wait-for-trigger/) step on `Episode completed` and set the waiting period to 1 day. Leave the **Trigger group 1** branch empty, so readers who finished an episode leave the journey without a message.
3. On the **Not triggered** branch, add a [Reachability check](/product/customer-journey/journey-elements/flow-controls/reachability-check/).
4. For readers reachable by push, add a [push](/product/customer-journey/journey-elements/channels/push/) that names the series, for example: "The Long Road: pick up where you left off." To insert the name, turn on **Personalise message with event attributes** on the push step, and under **Overwrite personalization** map the preset placeholder to the `series_name` attribute of `Episode started`.
5. For the others, add an [In-app element](/product/customer-journey/journey-elements/channels/in-app/) with a general reminder, for example "Your episode is waiting for you.", and set **In-app expiration** to 1 day. The in-app element does not take event attributes, so it can't name the series.
6. On the canvas, click **Settings** and select [**Campaign Entry Limit**](/product/customer-journey/journey-settings/#campaign-entry-limit).
7. Choose **Custom period** and set **Once in** to **a week**, so a reader who starts episodes every day gets one reminder a week, not one a day.
8. On the canvas, click **Settings** and select [**Conversion goals**](/product/customer-journey/journey-settings/#conversion-goals).
9. In the goal, choose `Episode completed` and select **End journey after this event**.

A reader who finishes any episode during the day counts as done, even if it is not the one that started the journey. The reminder names the series from the episode that started the journey. The same journey works for podcasts and for long articles: replace the events with your own start and finish events.