> 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/mobile-push/create-mobile-push.md).

# Create mobile push

Create a mobile push campaign in five steps: set up the campaign, write the content, choose the audience, schedule delivery and test before sending.

{% hint style="info" %}

#### Quick path

**Messages** → **Campaigns** → **Create New Campaign**

1. Set the campaign name and push type in [**Setup**](/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/setup.md).
2. Add content and click actions in [**What**](/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/what.md).
3. Define the audience in [**Who**](/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/who.md).
4. Set timing, expiry, and delivery speed in [**When**](/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/when.md).
5. Review, test, and send in [**GO**](/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/go.md).
   {% endhint %}

Create Mobile Push is the guided flow for building a push campaign from start to send.

Use it to:

* create one-time campaigns,
* target specific users or broad audiences,
* schedule delivery now or later,
* and test the message before launch.

{% @arcade/embed url="<https://app.arcade.software/share/QAeYHw1QhqvvqBZysphE>" flowId="QAeYHw1QhqvvqBZysphE" %}

### Before you start

Before creating a campaign, make sure:

* your mobile push channel is already configured,
* the audience data you need already exists,
* and you know the campaign goal before choosing the format.

{% hint style="info" %}
If you plan to personalize the push, prepare the required [**Profile Attributes**](/netmera-user-guide/customer-data/profile-attributes.md) first.
{% endhint %}

### Campaign flow

<table data-view="cards"><thead><tr><th>Step</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Setup — choose the campaign name and push type</td><td><a href="/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/setup.md">Push step 1: Setup</a></td></tr><tr><td>What — define title, message, media, personalization, and click action</td><td><a href="/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/what.md">Push step 2: What</a></td></tr><tr><td>Who — select the audience and delivery limits</td><td><a href="/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/who.md">Push step 3: Who</a></td></tr><tr><td>When — decide when and how fast the push is sent</td><td><a href="/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/when.md">Push step 4: When</a></td></tr><tr><td>GO — review the setup, send a test, and launch</td><td><a href="/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/go.md">Push step 5: GO</a></td></tr></tbody></table>


---

# 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/mobile-push/create-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.