বিষয়বস্তুতে যান

Launch and measure

এই বিষয়বস্তু এখনও আপনার ভাষায় উপলব্ধ নয়।

Test every journey on your own phone before real readers get its messages, then check whether it works.

Test each journey before you launch it

Anchor link to

A journey has no test mode, so once it is running, real readers who match its entry get its messages. Testing on your own phone first catches a missing event, an empty segment, or a wrong message before readers see it.

Run through this list for each journey:

  1. Install the version of your app that includes the Pushwoosh SDK on your phone. If you do not have one, ask your developers for a test version.

    The phone must register in the application where the journey runs. To send test messages from presets, also register it as a test device.

  2. Log in to the app with a test account.

  3. Use the app and do what the journey needs, for example start an episode. Then open Audience → User explorer, find the test device, and check Events history.

    The events must be there with the expected attributes, or the segment and the journey do not see them.

  4. If the journey starts from a segment, open it in Audience → Segments and refresh its size to see whether it counts any readers.

  5. Launch the journey for your test readers only. Build a test segment from your test User IDs with the User ID filter. If the journey starts from a segment, use the test segment as its entry. See How to test a journey with a test segment.

  6. On the test phone, do the action that the entry waits for.

  7. Check that the message arrives, and follow the test reader with Find user path.

  8. After a day, check how many readers entered the journey. See Read the journey statistics.

To test a news alert, send it to the test segment first, with the same message type and settings as the real alert.

Read the journey statistics

Anchor link to

Journey statistics show whether readers enter a journey, get its messages, and reach its goal. They count goal conversions, not revenue. To compare revenue, use Conversion events.

To see the journey statistics:

  1. Open the journey on the canvas. To read the numbers for the whole journey, use the statistics panel on the left.
  2. For numbers on each element, open Canvas settings (the gear icon in the bottom-right corner) and turn on Show metrics. See Journey element statistics.

For what each metric means, see Overall journey statistics.

Check the first-week signals

Anchor link to

In the first week after launch, look for these signals:

If you seeIt usually meansWhat to do
No entrancesThe entry segment is empty or the entry event does not arriveRepeat steps 3 and 4 of Test each journey before you launch it
Far fewer messages sent than entrancesMany readers can’t get push, or frequency capping and the silence period hold messages backOpen Communications on the statistics panel and check Suppressions in the Frequency capping card, add an in-app or email branch after a Reachability check, and check your delivery rules. News alerts also count toward frequency capping unless you send them as Transactional
Many drop-offsReaders left the journey because of a problem, such as a device that was not found or an invalid push presetExpand the Drop-offs block on the element to see the reasons
Messages are opened, but few readers reach the goalThe message works, but the content or the moment does notTest another text or offer with an A/B/n split

Measure results

Anchor link to

To measure whether a journey changes reader behavior, use the three tools below, from simplest to strongest.

  • Conversion goals: every journey in this playbook has one. News alerts are one-time pushes and have none. The goal can be reached within the period you set, up to 30 days after the reader leaves the journey. See Conversion goals.

  • Holdout Split: hold back 1% to 20% of the readers who reach a Holdout Split element and compare their goal rate with everyone else. The Goal uplift vs holdout report updates once a day.

  • Control group: by default, holds out a share of the readers from all marketing messages in the application. Compare them with everyone else to measure the combined effect of your messaging. Set it up before you launch. See Set up a control group before you launch. To read the results, see Analyze control group impact.

Cases to check before launch

Anchor link to

These cases decide whether your segments fill up and your journeys and news alerts reach readers. Check them before you launch.

General cases

Anchor link to

These cases are the same in every media app and in other industries.

CaseWhat happensWhat to do
iOS push permission promptiOS shows it only once, so a reader who declines on the first launch can’t be asked againAsk for push permission at the right moment
Repeating events such as Episode startedThey fire many times a day, and each one after the previous run of the journey ended starts it againSet a Campaign Entry Limit. See Best practices for every journey
Two paths to revenueIf the app sends PW_Conversion and Subscription started also carries __amount, Pushwoosh records each subscription twiceUse one path per subscription. See Track revenue from subscriptions
Readers without a push tokenAn Audience-based entry and segment filters with never take in only devices with a push token, so readers whose app has not asked for push permission yet are left outAsk for permission early enough for your journeys. See Build the segments

Media cases

Anchor link to

These cases are specific to media apps: news alerts, reader tracking, and subscriptions.

CaseWhat happensWhat to do
News alerts of the Marketing typeThey count toward frequency capping, wait for silent hours, and skip readers in the control group, so on a busy news day some readers don’t get an alert or get it lateDecide the message type before the first alert. See Choose how news alerts follow the delivery rules
A news alert to an offline phoneWith the default Time to Live of 1 week, a phone that comes online later gets an alert about old newsSet Time to Live to a few hours for each alert. See News alerts
A reader who has not given consentThe SDK sends nothing to Pushwoosh until the app turns communication on, so the reader is not in segments and gets no messagesCheck that the app turns communication on after consent. See Start the SDK after the reader gives consent
Store purchases without the reader’s HWIDPushwoosh receives the store notification but records no subscription event, so the Cancelled subscription journey never startsAsk your developers to pass the HWID with each purchase. See Track subscriptions from the stores
Readers who don’t log inWithout your own User ID, Pushwoosh counts each device as a separate reader, so what a reader does on one device does not count on another, and an episode started on a phone and finished on a tablet starts the Continue watching reminderSet your account ID as the User ID for readers who log in. See Identify readers by User ID
A subscription bought on your websiteThe app does not know about it, so the paywall offer can still reach a reader who just subscribedSend Subscription started from your server with the reader’s userId. See Send the events from the app and your server
Inactivity segments right after launchAt-risk and Lapsed readers are empty until Content read has been recorded for 14 and 60 daysUse PW_ApplicationOpen in the same filters at first. See Build the segments