> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/metaverse/build/editor/project-settings/lead-generation.md).

# Lead Generation

In case you want to collect any information from the viewer in your Metaverse. You can use this section to show a form to collect data from them.

This can be used for various purposes including training, registration, webinars, events etc. It allows viewers to enter a few details before entering your experience.

This can be set up from the “**Settings > Lead Generation**” page as shown below

<figure><img src="/files/9lU0i4l6b1zU4LAH2iE8" alt=""><figcaption><p>Setting up Lead Generation form</p></figcaption></figure>

The viewer is presented with a form like this when opening the deployment:

<figure><img src="/files/vqa1QpItRz4ZJfw2EHUb" alt=""><figcaption><p>Lead Generation form for the viewer</p></figcaption></figure>

### More Options

* Clicking on "Required" ensure that that question isn't skippable
* Clicking on Viewer Identifiers is useful if you want to store this response in the [v\_identifier\_var](/metaverse/build/variables.md#v_identifier_var) variable.


---

# 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.gmetri.com/metaverse/build/editor/project-settings/lead-generation.md?ask=<question>&goal=<endgoal>
```

`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.