> For the complete documentation index, see [llms.txt](https://tutorials.kuasa.io/getting-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tutorials.kuasa.io/getting-started/kuasa-landing-page/landing-page/how-to-set-tagging-in-landing-page.md).
# How To Set Tagging in Landing Page
1. Log in to your Kuasa account via .
2. Click on **Landing Page**.
3. Select any landing page for which you want to set the tagging.
4. Follow the steps below based on the type of landing page.
**Single Page**
1. Click the **Settings** button at the top of the page.
2. Set the tagging under the **Tagging** field, then click **Save Changes**.
**Sales Funnel**
1. Choose the step where you want to set the tagging, and then click the **Settings** button.
2. Under the **Step** section, set the tagging in the **Tagging** field, then click **Save Changes**.
**Opt-in Form**
1. Set the tagging under the **Tagging** field, then click **Save Changes**.
**Order Form**
1. Scroll down and click on **Advanced Settings**.
2. Set the tagging under the **Tagging** field.
3. You can set the tagging based on the order status.
4. Click **Update & Publish**.
---
# 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://tutorials.kuasa.io/getting-started/kuasa-landing-page/landing-page/how-to-set-tagging-in-landing-page.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.