> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/forms/multi-step-forms.md).
# Multi-Step Forms
**1st form:**
The first step needs to have a field to identify the user (such as 'email'). Add any other data fields you'd like to collect on the first step. Then, be sure to select the 'Redirect URL' option and paste in the link to the second step (you may need to save this form and come back and edit it once you've made the second form). **At the end of the URL, add** ?email={email} **to ensure the email address is passed along to the next step.**
### 2nd form:
Like the first step, add the 'email' field and any other data fields you'd like to collect on the second step. Then, be sure to select the 'Redirect URL' option and paste in the link to the third step (you may need to save this form and come back and edit it once you've made the third form). **At the end of the URL, add** ?email={email} **to ensure the email address is passed along to the next step.**
After you have saved your second form, click on the 'Customize Design' option for the form. On the screen that appears, we'll want to add some code to ensure that the 'email' field box becomes hidden and gets filled with the email address passed along from the first step.
**Additional CSS box:** .field-email{ display:none; }
**Tracking code (inside \) box:** const queryString = window\.location.search; const urlParams = new URLSearchParams(queryString); const email = urlParams.get('email'); window\.onload = function() { document.getElementById('email').value = email; }
### 3rd form:
Like before, add the 'email' field and any other data fields you'd like to collect on the third step. Since this is the final step, select the 'Confirmation Message' option.
After you have saved your third form, click on the 'Customize Design' option for the form. On the screen that appears, we'll want to add some code to ensure that the 'email' field box becomes hidden and gets filled with the email address passed along from the first step.
**Additional CSS box:** .field-email{ display:none; }
**Tracking code (inside \) box:** const queryString = window\.location.search; const urlParams = new URLSearchParams(queryString); const email = urlParams.get('email'); window\.onload = function() { document.getElementById('email').value = email; }
If you'd like the page to refresh after 7 seconds to the first step upon submission, add this additional piece of code - *be sure to replace INSERTURLHERE with the URL to the first form!!*
**Tracking code (on form submission) box:** setTimeout(() => { window\.location.href = 'INSERTURLHERE' }, "7000");
---
# 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://help.gleantap.com/forms/multi-step-forms.md?ask=&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.
