> 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/setup.md).
# Push step 1: Setup
Start a mobile push campaign by naming it, choosing the campaign type and push notification type, and checking the estimated reach of the audience.
Use **Setup** to define the campaign's general information and initial configuration.
Set a recognizable name, select a delivery channel, and review the potential audience. These choices establish the campaign before you create its content.
{% hint style="info" %}
Use a consistent naming pattern. It makes dashboards and reports easier to scan.
{% endhint %}
### Campaign name
Enter a unique, descriptive **Campaign Name** to identify this campaign internally.
This name appears in dashboards and reports. Choose one your team can recognize later.
Include details that distinguish similar campaigns. For example, include the channel, audience, purpose, or launch date.
### Campaign type
Select the channel that matches where you want to reach your audience:
* **Push Notification** — mobile apps
* Web Push — web browsers
* SMS
* Email
Each channel has its own content and delivery configuration. Your selection determines the next campaign steps.
{% hint style="info" %}
For mobile apps, select **Push Notification**. You can then configure iOS and Android delivery.
{% endhint %}
Enter the campaign name and select a channel.
### Mobile push notification types
Select the push notification format that fits your message and audience. The selected format determines how the notification appears and behaves in the mobile app.
Select the push format for your campaign.
### Estimated reach
The **Estimated Reach** panel appears beside **Campaign Type**. It provides a real-time view of devices that can receive this campaign.
Use this panel to understand the campaign's potential scale before you continue.
#### Reach breakdown
* **Total Devices** — combined reach across iOS and Android
* **iOS Devices** — eligible iOS users and devices
* **Android Devices** — eligible Android users and devices
Review reach by platform before sending.
#### Use estimated reach
* Confirm the campaign scale before creating its content.
* Compare platform reach before tailoring content or visuals.
* Consider platform-specific adjustments when one audience is larger.
* Use the total reach to plan delivery timing or an A/B test.
---
# 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/setup.md?ask=&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.
