Skip to content

Commit 2b63a2b

Browse files
committed
Clean up template page
1 parent 72a7c96 commit 2b63a2b

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

src/engage/content/mobile-push.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ You can choose between two push notification template types:
1515
## Build a push notification message template
1616

1717
> info ""
18-
> To build a push notification template in Engage, you must first [configure Engage for push notifications](/docs/engage/campaigns/push-notifications/).
18+
> To build push notification templates in Engage, first [configure Engage for push notifications](/docs/engage/campaigns/push-notifications/).
1919
20-
Follow these steps to build an push notification template:
20+
Follow these steps to build a push notification template:
2121

2222
1. Navigate to **Engage > Content** and click **Create template**.
2323
2. Select **Push**, then click **Configure**.
@@ -33,11 +33,11 @@ Follow these steps to build an push notification template:
3333

3434
When you build a push notification template, you can choose between three click behaviors, which determine what happens when a user taps on the mobile push:
3535

36-
| Click behavior | Description |
37-
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
38-
| Open app | Opens an app. You can specify a URL with or without merge tags to take the user to a specific screen with your app. If you don't enter a URL, this behavior will take the user to the app's home screen. |
39-
| Open URL | Opens the specified URL. |
40-
| Custom action | Takes any value as text input. Your app determines how to handle the value. For example, you could enter a custom action of `open_settings`, and then instruct your application to open the settings application when a user taps the notification and the notification arrives with `click behavior = open_settings`. |
36+
| Behavior | Description |
37+
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
38+
| Open app | Opens an app. You can specify a URL with or without merge tags to take the user to a specific screen with your app. If you don't enter a URL, this behavior will take the user to the app's home screen. |
39+
| Open URL | Opens the specified URL. |
40+
| Custom action | Takes any value as text input. Your app determines how to handle the value. For example, you could enter a custom action of `open_settings`, and then instruct your application to open the settings application when a user taps the notification and the notification arrives with `click behavior = open_settings`. |
4141

4242
## Test your mobile push template
4343

@@ -51,7 +51,7 @@ Follow these steps to test your push notification:
5151
- For new templates, select **Test** once you've finished building a template.
5252
- For existing templates, navigate to **Engage > Content > Push**, select the template you want to test, then click **Test**.
5353
2. Choose a messaging service and add a recipient.
54-
- You can add recipients either by either their email address or user ID.
54+
- You can add recipients using an email address or user ID.
5555
3. Click **Send test push**.
5656

5757
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

Comments
 (0)