# Build the journeys

Each recipe on the pages of this section is one journey or one news alert. The journeys and their message texts are examples. Build the ones you need and replace the texts with your tone and content.

* To open the canvas, see [Start creating your first journey](/product/customer-journey/getting-started/#start-creating-your-first-journey).
* For the canvas basics, see the [Customer Journey overview](/product/customer-journey/pushwoosh-journey-overview/).

<Aside type="tip" title="Let AI Assistant create the journeys">
[AI Assistant](/product/pushwoosh-ai/ai-assistant/) can create the journeys from these recipes in your application. Send it the link to the recipe page and name the journey you need. It creates the journey right away, as a draft that doesn't affect readers until you launch it. Check the draft before you launch it.
</Aside>

## Choose the journeys to build

Readers move through similar stages. Use this table to pick the journeys for the stage where you lose them.

| Stage | What is happening | Journeys |
| --- | --- | --- |
| New | The reader created an account and follows no topics yet | <ul><li>[Welcome and topic choice](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/new-readers/#welcome-and-topic-choice)</li></ul> |
| Reading and watching | The reader follows topics, reads articles, and watches episodes | <ul><li>[News alerts](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/reading-and-watching/#news-alerts)</li><li>[Continue watching](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/reading-and-watching/#continue-watching)</li></ul> |
| Subscribing | The reader reached the paywall or has a subscription | <ul><li>[Paywall follow-up](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/subscriptions-and-win-back/#paywall-follow-up)</li><li>[Cancelled subscription](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/subscriptions-and-win-back/#cancelled-subscription)</li></ul> |
| Leaving | The reader stopped reading | <ul><li>[Win-back for inactive readers](/tutorials/industry-playbooks/media-and-streaming/build-the-journeys/subscriptions-and-win-back/#win-back-for-inactive-readers)</li></ul> |

Start with News alerts and Win-back for inactive readers. Add the others when their events start to arrive: Continue watching needs the episode events, and Paywall follow-up and Cancelled subscription need the subscription events.

## Prepare the content for the journeys

Every message element in a journey uses ready content, so create the content before you build the journey. Each recipe lists what it needs under **Content to prepare**. Create the content in **Content**:

* **Push:** [push presets](/product/content/push-presets/). A preset can also open an article or an episode in your app with a [deep link](/product/messaging-channels/push-notifications/advanced-push-features/deep-linking/), and show an image, such as the cover of the article, in the notification.
* **In-app:** [in-app templates](/product/content/in-apps/).
* **Email:** [email content](/product/content/email-content/).

### Personalize the content

You can put three kinds of data into a message: data from the event, data stored on the reader, and the reader's language.

#### Put event data into a message

Use it for a value from the event that started the journey, such as the series name:

1. Add a placeholder to the preset.
2. On the push or email step, turn on **Personalise message with event attributes**.
3. Under **Overwrite personalization**, map the placeholder to the event attribute.

In-app elements do not take event attributes. You can also insert the value with a Liquid placeholder. See [Dynamic Content and Liquid Templates in journeys](/product/customer-journey/journey-elements/dynamic-content-and-liquid-templates-in-journeys/).

#### Put reader data into a push

To put a value stored on the reader into a push, such as a tag, add a [Dynamic content](/product/personalization/dynamic-content/) placeholder to the text.

#### Send each reader the message in their own language

Add the languages to the push or in-app content. Pushwoosh picks the version by the device's Language tag, which the SDK sets from the OS locale, so you do not need a custom language tag. To write the other languages, you can [translate the push content with AI](/product/content/push-presets/translate-push-content-with-ai/). See [Multi-language messaging](/product/personalization/multi-language/).

## Best practices for every journey

Apply these to every journey in this playbook:

| Practice | Why |
| --- | --- |
| Set a silence period | A push should not reach a reader in the middle of the night. The period blocks messages in each reader's device timezone, for example 22:00 to 08:00. Learn more: [Silence period](/product/customer-journey/journey-settings/#silence-period) |
| Limit how often a reader enters | A reader who is in a journey does not enter it again, but once the journey ends, the next `Episode started` or the next segment check starts it again, so one reader could get the same reminder again and again. Learn more: [Campaign entry limit](/product/customer-journey/journey-settings/#campaign-entry-limit) |
| Choose the message type on every message element | A journey that starts on an event does not preselect the type, and the element shows **Message type not selected** until you choose one. Learn more: [No preselected message type](/product/messaging-channels/marketing-vs-transactional/#no-preselected-message-type) |
| Use Marketing message for reminders, offers, and win-back | A marketing message follows the limits you set: [frequency capping](/tutorials/industry-playbooks/media-and-streaming/prepare-for-communication/#set-delivery-rules-before-you-message-readers), silence periods, and [control groups](/tutorials/industry-playbooks/media-and-streaming/prepare-for-communication/#set-up-a-control-group-before-you-launch). Transactional messages skip frequency capping and control groups, but not silence periods. Learn more: [Choosing the right message type](/product/messaging-channels/marketing-vs-transactional/#choosing-the-right-message-type) |
| Add a conversion goal | To see how many readers did the action you chose, such as reading an article or subscribing, check the conversion rate of the goal in **Performance**. Learn more: [Conversion goals](/product/customer-journey/journey-settings/#conversion-goals), [Measure results](/tutorials/industry-playbooks/media-and-streaming/launch-and-measure/#measure-results) |
| Stop the journey when the reader does the action | A reminder that arrives after the reader subscribed or came back annoys the reader. In the conversion goal, choose the event and select **End journey after this event**. To end the journey on an event that is not a conversion, add it under **Settings** → **Cancel events** |
| Plan for readers without push | A reader who has not allowed notifications gets no push. Add a Reachability check and send an in-app message or an email instead. In-app messages reach only readers who use the app, not your website. Learn more: [Reachability check](/product/customer-journey/journey-elements/flow-controls/reachability-check/), [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) |
| Check who a segment journey takes in | A journey that starts from a segment takes in only devices with a push token. The token arrives when the app asks for push permission, even if the reader declines, so these readers enter and get the in-app message. Readers the app has not asked yet do not enter |
| Set an expiration on in-app messages | A journey in-app appears the next time the reader opens or returns to the app, as **Show in-app** is set to **On next app launch** by default. Set **In-app expiration**, for example 1 day, to keep old messages from appearing days later. To reach readers outside the app, use a push. Learn more: [In-app expiration](/product/customer-journey/journey-elements/channels/in-app/#select-template-and-set-expiration) |
| Test every journey before you launch it | A journey has no test mode, so once it is running, real readers who match its entry get its messages. Learn more: [Test each journey before you launch it](/tutorials/industry-playbooks/media-and-streaming/launch-and-measure/#test-each-journey-before-you-launch-it) |
| Set delivery rules before you launch | They limit how often a reader hears from you across all journeys and news alerts. Learn more: [Set delivery rules before you message readers](/tutorials/industry-playbooks/media-and-streaming/prepare-for-communication/#set-delivery-rules-before-you-message-readers) |