> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-components/action/send-mobile-push.md).

# Send mobile push

Send a mobile push from a journey step with title, message, personalization, click action and rich media, then test it on a device before saving.

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.

### 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.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FMvLlLduHog4h5mztol8a%2FEkran%20Resmi%202026-09-28%2013.29.04.png?alt=media&amp;token=695bf614-92fb-4286-879e-45be69a37ac0" alt="" width="563"><figcaption></figcaption></figure>

<table><thead><tr><th width="179.13671875">Field</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Push Name</strong></td><td>Internal name. Users do not see it.</td></tr><tr><td><strong>Push Title</strong></td><td>Notification headline shown on the device.</td></tr><tr><td><strong>Push Message</strong></td><td>Notification body shown on the device.</td></tr></tbody></table>

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**.

### 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.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FfYswWfRryPxUMRkYCC72%2FEkran%20Resmi%202026-09-28%2013.29.44.png?alt=media&amp;token=be1c6348-895f-4564-9aba-8979ec96f07f" alt="" width="563"><figcaption></figcaption></figure>

### Step 4: Configure the click action

Select the behavior for a notification tap.

<table data-header-hidden><thead><tr><th width="211.57421875"></th><th></th></tr></thead><tbody><tr><td><strong>Push Click Action</strong></td><td>Result</td></tr><tr><td><strong>Nothing</strong></td><td>No follow-up action occurs.</td></tr><tr><td><strong>Open App</strong></td><td>Opens the application’s default screen.</td></tr><tr><td><strong>Go to Deeplink</strong></td><td>Opens an internal destination or external URL.</td></tr></tbody></table>

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.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F77IYu11kTtya436eauCQ%2Fimage.png?alt=media&amp;token=2ccad1db-741b-4f65-b079-9d96b0fc4d7e" alt="" width="563"><figcaption></figcaption></figure>

### 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.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FdphU8x9V42NJ5OXhdzrr%2FEkran%20Resmi%202026-09-28%2013.41.25.png?alt=media&amp;token=aba3814f-bae0-423f-9458-12fde22f8e89" alt="" width="563"><figcaption></figcaption></figure>

### 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.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FzjlnwQoyhcY2QuaJZCPA%2FEkran%20Resmi%202026-09-28%2013.42.15.png?alt=media&amp;token=23d06b16-12f0-456a-9f0a-064e1c02c1ec" alt="" width="361"><figcaption></figcaption></figure>

{% hint style="info" %}
Set up the test device before sending a test. See [Test Devices](/netmera-user-guide/panel-settings/settings/administration/test-devices.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-components/action/send-mobile-push.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.