Push

Push element indicates a point to communicate to a customer with a push notification.

To send a push message at the right moment in the journey, add the Push element after the event or condition that should trigger the message. Then, select a preset from your Pushwoosh account.

For greater relevance of your messages to journey travelers, you can add personalized content based on users’ behavior. For example, sending an Abandoned Cart push, add the product name for better conversion – remind users of what exactly they wanted to purchase, that’ll make your message more convincing.

Learn more about personalization of journey messages

You can personalize push notifications by attaching a voucher code from a predefined pool. This is useful for promotions, discounts, and loyalty incentives.
For this, create a push preset that includes the placeholder {{voucher}} in advance.

To include a voucher:

1. Toggle Vouchers to ON.
2. In the Voucher Pool field, select the pool containing your available voucher codes. Make sure to add the pool of vouchers in advance.
3. (Optional) Use the Assign Tag field to apply a tag to users who receive a voucher. This tag can be used for segmentation or reporting.Learn more about vouchers

The Save to Inbox option lets you store push notifications in the app’s inbox, so users can access and review messages whenever it’s convenient for them. This helps ensure that important notifications aren’t missed and can be checked later, making it easier for users to stay engaged.

To save a message to the inbox, simply toggle the Save to Inbox option and set it up.

1. Choose how long the message stays in the inbox.
2. Customize the message icon, if needed. You can choose a different icon for the message to help it stand out in the inbox.
3. Define what happens when the user clicks the message.

Learn more about setting up the inbox

Use Frequency capping to limit how often users receive push messages, preventing over-messaging and reducing churn. In the Push element settings, choose one of the following options:

• Use Global frequency capping settings

  Apply the project-wide limits configured in your Global frequency capping settings.

  For example, if the global limit is set to 3 messages in 9 days, additional messages exceeding this limit will be skipped.

• Ignore Global frequency capping

  The user will receive this message even if they’ve exceeded the channel’s message limits. Use this option with caution to avoid over-messaging.

• Use custom frequency capping

  Set a custom message limit for this message. If the user exceeds this custom cap, the message will be skipped, and the user will proceed to the next step.

  Important: Custom frequency capping does not isolate the message from Global frequency capping. All messages sent on the same channel, including those from other journeys or campaigns, are still counted toward the global cap. If the user has already received 3 push messages this week from other sources, this message may still be blocked, even if the custom capping would allow it. Learn more

If you want each user to receive a push notification when they are most likely to interact with pushes, enable the Best time to send option. The time for sending the message to each user will be calculated based on their behavior and previously sent messages’ performance.

The accuracy of calculating the best time for each user depends on how many pushes you sent to this user earlier.

If there is not enough data on the user, they will receive a push at the Default time you specify according to their timezone.

You can split the remaining journey flow based on whether this push notification is opened or ignored. For example, it might be helpful to send emails to those who don’t open pushes or send one more push to those who have read the first one.

Check the checkbox and set the period to wait after the push is sent – after that period, all users who open the push will go to the Opened journey branch, and others will pass through the Not opened branch.

Waiting period can be set to up to 7 days.

When enabled, the message will be sent to all the devices associated with an ID of a user who reaches this journey element. Thus, if a user has several devices, all associated with a single userID, that user will receive several messages, one per device.

When everything’s set, press Apply.