# FAQ

<details>

<summary>My campaign has low deliverability</summary>

If the percentage of delivered campaigns is at the level of 50-60%, nothing terrible is happening. Subscribers often sign up on several browsers, when in practice they use only one. Then such a recipient is pending until he or she turns on the browser he or she signed up for.

Lower deliverability may be due to:

a) blocking notifications within the operating system - this applies to both desktop and mobile devices. In this case, the subscriber does not unsubscribe from notifications, but cannot receive them until they are unblocked

b) the expiration date of the notification - the shorter, the less chance that all subscribers will receive the notification

However, if the percentage of delivered campaigns oscillates between 0-20%, and the situation described in point B does not occur, then it is worth analyzing the integration once again, if it was done correctly.

To do so, check that:

a) the exact same script that was generated for this project was pasted into the page,

b) the exact same sw\.js that was generated for this project was pasted into the server root path,

c) the website does not contain additional scripts or service workers (service worker.js, sw\.js etc.) belonging to another provider.

</details>

<details>

<summary>Why did my last campaign cause so many unsubscribes?</summary>

This is due to the limitations of the web push technology itself. Recipients can unsubscribe at any time. However, we are able to report that someone has unsubscribed from them and how many total unsubscribes there were since the last such notification only at the time of dispatch.

</details>


---

# 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.pushpushgo.company/campaigns/faq.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.