> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/~/changes/B87CND5z8x8BAzJwmSVQ/products/crm-automation/communication-channels/how-to-create-a-push-resource.md).

# Push notifications

Push notifications are one of the very few offline but successful communication channels that could bring you very good conversion rates in no time. As a great channel, it is also a special one, since it is requiring special permission prior to being able to use it within campaigns.

## **How do push notifications work?**

In order to be able to send push notifications to the end user, we first need to get permission to do so. The permissions are requested in the web browser and as soon as the user gave them, Smartico will mark the user as reachable for the push notifications.

Every user could control the Push allowance from the user's browser. The push status could have 3 possible options:

* **Ask** - the user wasn’t asked yet to give permissions (default status)
* **Allowed** - in this case, the push message could be sent, the user gave permissions
* **Blocked** - in this case, the push messages are not allowed, the user blocked permissions.

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FWMsbc9annT3Mg6Bf9B4f%2Fpush4.gif?alt=media&amp;token=fd941853-4f3d-4de2-a396-8924237a158f" alt=""><figcaption></figcaption></figure>

## Request permissions to send pushes

In order to start using our push services, you will have to build a Journey campaign that is asking a user to give push permissions.

This campaign should address only users who have “Push status of the last session” set to “Ask”, this means that the browser is supporting push permissions and we didn’t ask this user yet. This way we are excluding those who already gave permissions and those who blocked them.

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FPWedBDwAOncWJc0UKQkU%2FPush1.gif?alt=media&amp;token=40bb9640-c46c-4d13-b756-bee08a22a399" alt=""><figcaption><p>Setting campaign to request push permissions</p></figcaption></figure>

In the campaign, you need to show a popup to the end user giving the proposition to subscribe to push notifications. This is usually called “soft” onboarding.

If the user clicks “No” at this point, you will have the possibility to ask him later again.

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FXZNiJYTqiv9QQp2xf3M1%2Fpush2.gif?alt=media&amp;token=d51907a3-1af2-4620-98b8-791e7888466d" alt=""><figcaption><p>Building a "soft" onboarding popup</p></figcaption></figure>

As soon as the user clicked “Yes” in the popup, we will trigger browser functionality that is asking for the permissions. From this point, most of the users will do a choice that will lead either to “Allowed” or “Blocked”

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fbu7vOboXdIEzfODKEfsE%2Fpush3.gif?alt=media&amp;token=c8f5cb37-e8ae-45b4-ad3e-7f1f02a5e71b" alt=""><figcaption><p>Full flow of the campaign, sending 1st push message as soon as user gives permission</p></figcaption></figure>

When the push permission has been granted, you can try to execute a push as part of the flow.

## How to segment users that can be addressed with Push notifications

In order to execute any push to users you will have to segment users. Create a segment with Core: push enabled, user has at least one device = true.

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FtQ2oTwxbXtV4h9ARUjGn%2Fimage.png?alt=media&amp;token=1b092b0d-daf3-4b05-8310-85a6a7cd523b" alt=""><figcaption></figcaption></figure>

Following that, the creation of a flow should be handled regularly. In case you have any further questions regarding this topic, please don\`t hesitate to contact your account manager.

## **Managing push notification resources**

1. **Navigate to** the Marketing tab -> Assets -> Push
2. **Click** on the Create button

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FXLV3d8yO47lXI2T9zro5%2Fimage.png?alt=media&amp;token=b673bc18-d80c-4ad0-8821-6e1162851b68" alt=""><figcaption></figcaption></figure>

1. Firstly choose the Resource name (recommended to reflect the most possible usage).
2. Add Title, Message optionally icon, attached image, or even buttons

{% hint style="warning" %}
**IMPORTANT:** Not all clients are supporting all of the given fields. For further information please check the provider.
{% endhint %}

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FAeLdkuQ3tLzMMXDkI31h%2Fimage.png?alt=media&amp;token=1eb24188-d491-4b28-af41-79be53081315" alt=""><figcaption></figcaption></figure>

Use popup for communication of:

1. Promotions
2. Invitations
3. Announcements
4. Alerts

and many more!

{% hint style="info" %}
**As dynamic as possible**, within all resources, also Pushes supporting content variations, labels, and state tags. For more information check out our article [Content Variations](/welcome/~/changes/B87CND5z8x8BAzJwmSVQ/products/crm-automation/communication-channels/content-variations.md)
{% 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 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://help.smartico.ai/welcome/~/changes/B87CND5z8x8BAzJwmSVQ/products/crm-automation/communication-channels/how-to-create-a-push-resource.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.