> For the complete documentation index, see [llms.txt](https://doc.appflow.ai/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.appflow.ai/docs/subscription-analytics/in-app-messages.md).

# In-app Messages

***

In-app messages are created to help you engage with your users even more. Imagine, you want to show a big message, not only [push notification](/docs/subscription-analytics/push-notifications.md).

<figure><img src="/files/Zxcqwog6RTSEdAMK0kUU" alt=""><figcaption></figcaption></figure>

The greatest advantage of this feature is that you can:

* show it exactly after triggering the event, i.e. refund OR
* schedule one event, i.e. congratulate your user with the holiday OR
* make a recurring campaign, i.e. remind your users to drink water every day.

One more advantage of using it with Appflow\.ai is that you can choose the exact users' segment to send your in-app message. For example, it could be released only for some language groups.

And the coolest thing is, as always, that you don't need your mobile developer to be involved as well as update the app version in the store. Everything is done with the Remote Configuration Control!


---

# 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://doc.appflow.ai/docs/subscription-analytics/in-app-messages.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.