Mobile Push campaign creation: step-by-step

Name

(required)

Name of mobile push notification that will be visible in the list on the Channel / Mobile Push tab. 

Remember: If performance reporting is set up for Mobile Push, frequently changing the campaign name may render the report difficult to understand. After the Mobile Push campaign is live and activated, we suggest changing the name as little as possible.

Select application

(required)

Select one application from the list of applications that are set under the Mobile push channel configurations.

If the selected mobile app supports both operating systems (Android and iOS), then both checkboxes are initially pre-checked. You can uncheck one operating system if needed, but keeping at least one checked for a valid selection is essential. 

If the app supports only one operating system, the corresponding OS checkbox is automatically selected and cannot be changed.

Title template

(required)

The title of the Mobile Push that will be sent to the user's device is delivered in bold type to grab customers’ attention. CreatingIt is possible to generate a personalizedcustomized title by usingutilizing attributes andalong with the LiquidJS templating language is supported. language.

Body template

(required)

A message that the user wants to render as a notification to the customers’ mobile phones.

You can create a personalized body of Mobile Push content using attributes and LiquidJS templating language.

Image

(optional)

Provide a valid URL or directly upload an image file.

Supported formats include jpg, jpeg, png, and gif, with an advised aspect ratio of 2:1 (landscape).

Uploaded images shouldn't exceed 500KB in size.

Learn how to tailor your content with personalized images in this article.

Remember: GIF animations are not supported on Android devices. The recommended format is JPG.

TTL

(required)

TTL, or Time-to-Live, guarantees the delivery of notifications, even when a user's device is offline or out of network coverage. 

The default and maximum TTL period is set to 4 weeks. This means notifications will be stored and delivered within this timeframe, ensuring users receive relevant information.

However, you can shorten the TTL if the push notification's content becomes outdated sooner than the default period. Possible to choose from 1 min, 2 mins, 3 mins, 5 mins, 10 mins, 30 mins, 1 hour, 2 hours, 4 hours, 1 day, 2 days, 3 days, 1 week, 2 weeks, 3 weeks, 4 weeks. 

Interaction

Interaction type

(required)

Select one of the options:

• Open app (default): launches the mobile application associated with the notification when the user interacts with it, typically opening the app's main screen.
• Open browser: opens a web browser, directing the user to a specific URL or web page. You need to define the url for redirection.
• Open deep link: navigates the user to a particular location in a mobile app. You need to define the url for redirection.
  

URL

(optional)

If one of the open browser or open deeplink was selected, you should populate the URL field.

For example, /home/booking/:bookingUri/transport/:transportUri. 

Use an attribute picker to personalize the deep links of your notification. You may want to use multiple attribute placeholders, e.g. 

/home/booking/{{bookingUri}}/transport/{{transportUri}}

Send test to

Read more here.