Saltar al contenido

Media and streaming

Este contenido aún no está disponible en su idioma.

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 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 for each reader who logs in, so Pushwoosh recognizes the same reader on every device.
  2. Choose the events to track 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.
  4. Group readers who match your conditions in 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.
  6. Send news alerts to the readers who follow a topic, and send messages automatically with journeys when a reader does something in the app or joins a segment.
  7. Test each journey, then read its statistics and measure results.

To start with less, follow Minimum setup to start messaging readers.

Prerequisites

Anchor link to
  • An application in your Pushwoosh account, with the SDK integrated (the Pushwoosh code library inside your app) so devices register automatically.
  • A role 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 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.

This playbook is written for an app with the Pushwoosh SDK. If readers also come to your website with the Web SDK, 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

Anchor link to

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

Minimum setup to start messaging readers

Anchor link to

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.
  2. Ask your developers to send the Content read event. See 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.
  4. Set the delivery rules, and decide which message type your news alerts use.
  5. Build the 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 to all readers, and launch Win-back for inactive readers.

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

To add more journeys, see these guides: