> For the complete documentation index, see [llms.txt](https://docs.pushpushgo.company/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pushpushgo.company/web-push/integration-script/subscription-form.md).
# Subscription form
The subscription form appears after you successfully integrate your page.
\
Users can agree to receive notifications with one click on a default browser pop-up in the upper left corner of a browser or double opt-in through a subscription form.
It's impossible to change the default browser form's appearance, but you can customize if and when the default form will appear after the user visits your website.
The subscription form can be fully customized. Bear in mind that it's only visible during the two-step subscription - the user has to agree to receive notifications through the subscription form, then through the default browser form.
The first option is available only for project integrated with own domain strategy since service worker is placed on the same domain as the integration script.
In basic integration, when a user agrees to receive notifications through the subscription form, a window opens where they have to agree to receive notifications default browser pop-up from PushPushGo subdomain since this is where the service worker will be registered.
---
# 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://docs.pushpushgo.company/web-push/integration-script/subscription-form.md?ask=&goal=
```
`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.