> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/notifications.md).

# Notifications

The Notifications category enables you to manage and send push notifications to engage with your app users effectively. Push notifications help drive user engagement, promote content, and enhance the overall app experience by delivering real-time updates directly to users' devices.

What you'll find in this category:

* Tutorials on setting up and managing push notifications – Learn how to configure and send notifications to your users.
* Automated and manual notifications – Understand how to schedule automated alerts or send manual updates to keep users informed.
* Personalization and targeting – Discover how to send notifications to specific user segments based on their behavior and preferences.
* Best practices for notification campaigns – Learn how to optimize your notifications to increase user engagement without overwhelming them.

{% hint style="warning" %}

#### Why it matters:

Push notifications help you stay connected with your users, boost retention, and enhance app usability by ensuring users receive important updates, promotions, and reminders at the right time.
{% 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://docs.appmysite.com/app/notifications.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.
