Pular para o conteúdo

Build the journeys

Este conteúdo ainda não está disponível no seu idioma.

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.

Choose the journeys to build

Anchor link to

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

StageWhat is happeningJourneys
NewThe reader created an account and follows no topics yet
Reading and watchingThe reader follows topics, reads articles, and watches episodes
SubscribingThe reader reached the paywall or has a subscription
LeavingThe reader stopped reading

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

Anchor link to

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:

Personalize the content

Anchor link to

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

Anchor link to

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.

Put reader data into a push

Anchor link to

To put a value stored on the reader into a push, such as a tag, add a Dynamic content placeholder to the text.

Send each reader the message in their own language

Anchor link to

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. See Multi-language messaging.

Best practices for every journey

Anchor link to

Apply these to every journey in this playbook:

PracticeWhy
Set a silence periodA 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
Limit how often a reader entersA 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
Choose the message type on every message elementA 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
Use Marketing message for reminders, offers, and win-backA marketing message follows the limits you set: frequency capping, silence periods, and control groups. Transactional messages skip frequency capping and control groups, but not silence periods. Learn more: Choosing the right message type
Add a conversion goalTo 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, Measure results
Stop the journey when the reader does the actionA 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 pushA 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, Ask for push permission at the right moment
Check who a segment journey takes inA 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 messagesA 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
Test every journey before you launch itA 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
Set delivery rules before you launchThey limit how often a reader hears from you across all journeys and news alerts. Learn more: Set delivery rules before you message readers