> For the complete documentation index, see [llms.txt](https://docs-en.shoppy.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.shoppy.is/shoppy-dashboard/engage/notification-settings.md).

# Notification Settings

### **Push Notification Prompt-In**

{% embed url="<https://cdn.mburger.cloud/347629/Don_t-miss-any-notification.png?data=eyJtZWRpYV9pZCI6MzQ3NjI5LCJieXRlcyI6MjI3MDk4LCJwcm9qZWN0X2lkIjoyNzg3LCJoYXNfaW1naXgiOjB9>" %}

To improve the activation rate of your notifications, we have added the ability to **customize** the content of the prompt-in that the users must consent to upon downloading your app. This way, you can choose the right words and phrases based on your target audience.

In order to customize this in your app, on your Shoppy Dashboard go to **Settings > App Settings > Push notification prompt-it and click 'Customize'.**&#x20;

You can change the title and text description of the push notification. You can insert text content here for different language settings of the app if you have Multi Country activated (Bloom plan only). Click 'Save' to register your changes.

### Video tutorial

{% embed url="<https://cdn.mburger.cloud/353789/Pushnotifsettngs_2_Q124.mp4?data=eyJtZWRpYV9pZCI6MzUzNzg5LCJieXRlcyI6NTY2MjMxLCJwcm9qZWN0X2lkIjoyNzg3LCJoYXNfaW1naXgiOjB9>" %}


---

# 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-en.shoppy.is/shoppy-dashboard/engage/notification-settings.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.
