Send mobile push

A mobile push appears outside the app on a user’s device. The journey sends it when a user reaches this step and has an eligible device. Use it to bring users back to the app or notify them about a time-sensitive update.

Use Send Mobile Push to send a targeted notification to eligible mobile devices. You can personalize content, set a click destination, add media, and test delivery before launch.

Step 1: Add the action

1. In Journey Builder, select Add Step.

2. Under Action, select Send Mobile Push.

3. Enter a Push Name.

Use a descriptive internal name, such as Cart reminder — 24 hours. The name helps distinguish this push from other steps. Users do not see it.

Select Send Mobile Push from the Action section.

Step 2: Write the notification

Enter the notification content.

The title and message are the visible parts of the notification. Write the message before adding optional settings. This makes the intended outcome clear.

Field	Purpose
Push Name	Internal name. Users do not see it.
Push Title	Notification headline shown on the device.
Push Message	Notification body shown on the device.

For example, set Push Title to Exclusive offer for @{user.name}. The resolved user name appears in each recipient's title.

Keep the title focused on one outcome. Use the message to explain the offer or next action.

Enter Push Name first. This name helps you find the step later in Build and Analytics. Then enter the content that users see in Push Title and Push Message.

Enter the push name, title, and message.

Step 3: Add personalization

Insert supported profile attributes or journey variables in the title or message.

Personalization inserts a value when Netmera prepares the message for a user. It does not change the saved push template.

• Profile Attributes use information stored for each user.

• Journey Variables use values available in the current journey.

For example, use @{journey.BrandName} in the message. The notification displays the brand captured in that user's journey context.

Use a profile attribute when the value already belongs to the user. Use a journey variable when an earlier journey step supplies the value. For example, use a profile name for a greeting and a journey brand name for a cart reminder.

Use profile attributes and journey variables to personalize content.

Step 4: Configure the click action

Select the behavior for a notification tap.

Push Click Action	Result
Nothing	No follow-up action occurs.
Open App	Opens the application’s default screen.
Go to Deeplink	Opens an internal destination or external URL.

If you select Go to Deeplink, select the Deeplink Type. Add Additional Parameters when the destination needs extra context.

Choose Nothing when the push only provides information. Choose Open App when the app’s default screen is the right destination. Choose Go to Deeplink when users must open a specific screen or URL.

Deeplink Type determines whether the link opens an app destination or an external web URL. Additional Parameters pass information to that destination, such as a product ID or category.

For example, use app://home?category=@{user.favoriteCategory}. The app opens the matching category for each user.

Configure the click action and deeplink.

Step 5: Add rich media

Rich media is optional. Do not add it when a text-only notification communicates the message clearly.

Add Android- or iOS-specific media when required. Use media compatible with the recipient platform.

Configure the media for each platform where it should appear. A platform-specific setting lets Android and iOS users receive content suited to their device.

For example, add a promotional banner image for iOS. iOS recipients receive the configured rich-media content.

Add platform-specific rich media.

Step 6: Test and save

1. Send the notification to registered Test Devices.

2. Verify the content and deeplink behavior on each device.

3. Select Save.

Testing checks the visible text, media, and click destination before users enter the step. Test every configured platform when Android and iOS settings differ.

The push step appears in the journey flow. It sends when eligible users reach it.

Test the push on a registered device before launch.

Set up the test device before sending a test. See Test Devices.