> 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-in-app-message.md).

# Send in-app message

An in-app message appears while the user uses the application. The widget defines the message’s design and behavior. The journey step determines when users can receive that widget.

Use **Send In-App Message** to display a widget when users reach a journey step. Select an existing widget, review its device preview, test it, and save the action.

### Step 1: Create the widget

Create and configure the widget in the Netmera Panel before building the journey step.

Decide what users should see and do before creating the journey step. For example, create a welcome-offer modal when the goal is to guide new users to a promotion.

The widget stores the content, layout, and user interaction. This journey action does not create or edit that widget. It selects the prepared widget for the journey.

{% hint style="info" %}
The **Widget** list only shows widgets created before this step.
{% endhint %}

### Step 2: Add the action

1. In **Journey Builder**, select **Add Step**.
2. Under **Action**, select **Send In-App Message**.
3. Enter a **Step Name**.

Use a name that states the widget’s purpose, such as `Show welcome offer`. This name is only used inside the journey.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FdOBE1fFhjl0G0RkNjRA4%2FScreenshot%202024-10-02%20at%2015.33.24.png?alt=media&amp;token=ae4ce925-ca9d-48da-af8c-5e4b6f7dec33" alt="Send In-App Message action in the journey builder" width="290"><figcaption><p>Select <strong>Send In-App Message</strong> from the Action section.</p></figcaption></figure>

### Step 3: Select a widget

1. Select a widget in **Widget**.
2. Use **Search Widget** when needed.
3. Confirm the selected widget matches the intended message.

Widgets can include banners, modals, and pop-ups.

Select the widget that matches both the message and the intended user action. For example, use a banner for a lightweight announcement. Use a modal when users need to notice a focused message.

Use **Search Widget** when the list contains several widgets. Search by the widget name you used during setup. Confirm the selected name before continuing.

For example, search for `Welcome Offer` and select the matching modal. Users who reach this step can receive that configured welcome offer.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FUbQAIWxVSniALoNkZ5Cn%2FScreenshot%202024-10-02%20at%2015.33.03.png?alt=media&amp;token=74d72e22-51b1-4902-ad83-4a03ee24da95" alt="In-app message widget configuration and preview" width="563"><figcaption><p>Select a widget, preview it, and test it on a device.</p></figcaption></figure>

### Step 4: Preview and test

1. Review the widget preview for Android and iPhone.
2. Send a test to a registered **Test Device**.
3. Confirm the widget renders and behaves as expected.

The preview shows how the selected widget is expected to appear. A test device verifies the actual display and interaction on a supported device.

Check the message text, image, buttons, and destination during the test. If the widget includes an action, complete that action on the device before saving the step.

### Step 5: Save the action

Select **Save**.

The in-app message step appears in the journey flow. The selected widget can display when users reach this point.

Users who do not reach this step do not enter this in-app message flow.

The journey does not change the widget after saving. Edit the widget separately if its content or behavior needs to change.

{% hint style="info" %}
Register a device before testing. 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-components/action/send-in-app-message.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.