|
| 1 | +--- |
| 2 | +title: Push Notification Campaigns |
| 3 | +plan: engage-premier |
| 4 | +--- |
| 5 | + |
| 6 | +With Twilio Engage, you can send campaigns to users who have opted in to receive your marketing materials. On this page, you’ll learn how to create and send a mobile push campaign. |
| 7 | + |
| 8 | +Some knowledge of the Journeys product will benefit you as you read through this guide. If you’re new to Journeys, the [Journeys documentation](/docs/personas/journeys/) will bring you up to speed. |
| 9 | + |
| 10 | +## How Engage campaigns work |
| 11 | + |
| 12 | +Twilio Engage uses Journeys to campaigns. With Journeys, you add conditions and steps that trigger actions like sending an email, an SMS, or a push notification. |
| 13 | + |
| 14 | +You’ll build and then send your campaign in three stages: |
| 15 | + |
| 16 | +1. Create a journey. |
| 17 | +2. Add a journey condition. |
| 18 | +3. Create, test, and publish your mobile push campaign. |
| 19 | + |
| 20 | +### Create a journey |
| 21 | + |
| 22 | +Because Engage campaigns exist within Journeys, begin by creating a journey: |
| 23 | + |
| 24 | +1. In Engage, select **Journeys**, then click **New Journey**. |
| 25 | +2. Name your journey and select its entry settings. |
| 26 | +3. Click **Build Journey** to create the Journey. |
| 27 | + |
| 28 | +### Add a Journey condition |
| 29 | + |
| 30 | +With your Journey created, you’ll now create a [condition](/docs/engage/journeys/step-types/) that will trigger your campaign: |
| 31 | + |
| 32 | +1. Within the Journey builder, click **+ Add Entry Condition**. |
| 33 | +2. In the Add Entry Condition pane, give the step a name. |
| 34 | +3. Click **+ Add Condition**, select your desired condition, then click **Save**. |
| 35 | + |
| 36 | +With your entry condition added, you’re now ready to create your mobile push campaign. |
| 37 | + |
| 38 | +### Create, test, and publish your mobile push campaign |
| 39 | + |
| 40 | +Follow these steps to create a mobile push campaign: |
| 41 | + |
| 42 | +1. Within the Journey builder, click the **+** node below your new condition. |
| 43 | +2. From the **Add step** window, click **Send a Push**. |
| 44 | +3. In the **Send a Push** window, select the mobile push template you want to use, or click **Create new template** to [build a new template](/docs/engage/content/mobile-push/). |
| 45 | +4. Review your template's content and click behavior, then click [Test](#test-your-mobile-push-template) or **Continue**. |
| 46 | +5. In the **Send a Push** modal, give the step a name, choose a messaging service, add any conversion goals, then click **Save**. |
| 47 | +6. In the Journey builder, click **Publish**. |
| 48 | + |
| 49 | +Your mobile push campaign is now live. Users who trigger the mobile push step’s parent Journey condition will receive your campaign. |
| 50 | + |
| 51 | +## Test your mobile push template |
| 52 | + |
| 53 | +> info "Push tokens" |
| 54 | +> Push tokens are unique identifiers Segment associates with each profile. For push notifications, you'll need to configure identity resolution settings for the push tokens `ios.push_token` and `android.push_token`. Using the Profile explorer, you can find a profile's push tokens by opening a profile and then selecting the Identities tab. You can only send push notifications to profiles with push tokens enabled. |
| 55 | +
|
| 56 | +Follow these steps to test your push notification: |
| 57 | + |
| 58 | +1. Choose a template to test: |
| 59 | + - For new templates, select **Test** once you've finished building a template. |
| 60 | + - For existing templates, navigate to **Engage > Content > Push**, select the template you want to test, then click **Test**. |
| 61 | +2. Choose a messaging service and add a recipient. |
| 62 | + - You can add recipients using an email address or user ID. |
| 63 | +3. Click **Send test push**. |
| 64 | + |
| 65 | +Segment verifies that the the profile you're sending a test to has push tokens enabled, then sends the test. If the test push notification doesn't work as expected, confirm that the profile you're sending to has enabled push tokens. |
0 commit comments