> 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/subscription-form-delay.md).
# Subscription form delay
### Time after which the form will appear
You can set up the time (in seconds) between the users' entrance on the website and the subscription form apperance.
### Reopen time
In Basic Integration, it is possible to display the form again after the initial rejection. For example, the user will be offered another sign-up form for notifications every 60 days.
This option is not available for integration with own domain. A default browser subscription form gives users the option of clicking the Block button, which means that the form will never be displayed again on this page and in this browser.
---
# 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/subscription-form-delay.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.