# PUSH Campaigns

#### Engage users at the right moment&#x20;

Our panel simplifies Push notification management, enabling the creation of engaging campaigns without involving IT resources for every send. This tool allows for intuitive setup, personalization, and real-time monitoring of your notifications.

### Key Campaign Features

* **Single Customer View**: Upload email addresses and phone numbers from your CRM to the panel. The system will automatically match them with new tokens collected by the SDK. You gain one complete customer profile, enabling precise cross-channel personalization.
* **Scheduling & Delivery Control**: Decide on the delivery time – send the campaign immediately or schedule it for later. The throttling feature allows you to manage the notification delivery rate and the traffic generated within the app, protecting your backend from sudden load spikes.
* **Audience Segmentation**:
  * Static Lists (Standard): Collection of contacts and tokens with the ability to create audience groups.
  * Dynamic Segments (Add-on): Advanced behavioral targeting available within the *MessageFlow Segments* add-on.
* **Content Management**: An easy-to-use builder that allows you to tailor notification content to user needs.
* **Analytics**: Real-time monitoring of delivery statuses and campaign effectiveness.

{% hint style="info" %}
**Technical Specification**

Detailed information regarding character limits (for titles and content) as well as requirements for graphics and file formats (Rich Push) can be found in the [**Overview** ](https://docs.messageflow.com/mobile-push/overview#technical-specification)tab.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.messageflow.com/mobile-push/push-campaigns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
