Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.getvero.com/llms.txt

Use this file to discover all available pages before exploring further.

The push node sends an iOS or Android push notification to a user as they progress through a Journey. You can use it on its own to trigger a single push from an event, or combine it with email, SMS, delay, and branch nodes to build multi-channel sequences.

​
Prerequisites

  1. Configure a push channel – Add an Amazon SNS or Twilio Notify provider on the Channels page before adding a push node. Learn how to configure a push channel.
  2. Register device tokens against your user profiles – Vero needs an iOS or Android device_token on each user’s profile to deliver a push message. Device tokens are added via the Vero API. See the mobile push integration guide.
  3. Track an event to trigger your Journey – Journeys are event-triggered, so you’ll need a tracked event to enter users into the flow. Learn about event triggers.

​
Adding a push node

  1. Open your Journey on the campaign canvas.
  2. Click the ”+” button to open the add node menu.
  3. Select Push.
  4. The push node is added to the canvas. Click the node to open the side panel and configure it.
Adding a push node to a Journey

​
Choose your push channel and platform

In the side panel, select the Provider Vero should use to send, or stick with the default. Push node side panel

​
Add your push content

First, choose which device platform the message should target: iOS, Android, or both.
Vero only sends to users with a device_token matching the selected platform. If you select iOS, users with only an Android token won’t receive the message at this step.
You can then write your push content using the basic or advanced editor. Both support Liquid personalization. For full content guidance, see Creating a push message.
  • Basic editor — Add a title, body, optional image, and iOS/Android tap-through links. Basic push content editor
  • Advanced editor — Write the raw iOS (aps) and Android (notification) payloads directly in a code editor for finer control. Advanced push content editor

​
Reporting on a push node

Once your Journey is live or stopped, the push node displays Sent, Opened and Converted (indirect) stats directly on the canvas, so you can see how the step is performing without leaving the journey view. Opened stats require your app to be tracking push opens.

​
Limitations

  • Push is supported for event-triggered Journeys only.
  • A user must have a device_token on their profile matching the selected platform to receive the push.
  • Reporting is limited to Sent and Opened interaction stats. Clicked stats are not supported.

​
Next steps

​
Need Help?

If you have any questions, reach out to us at support@getvero.com.