> For the complete documentation index, see [llms.txt](https://docs.supademo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.supademo.com/customize/chapters/email-lead-capture.md).

# Email lead capture

You can capture email leads throughout your Supademo by adding a mandatory or optional email form to a Supademo Chapter. 

**Here's a step-by-step guide:**

{% @supademo/embed demoId="cmacgq7ss05jlz20idezs07t4" url="<https://app.supademo.com/demo/cmacgq7ss05jlz20idezs07t4>" %}

As viewers fill in your lead form, you'll receive email notifications each time they enter in their email. In addition, they will show up under the Lead data section for that specific Supademo's analytics page:

![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/65cd1b060e92bd4055f3b684/images/66563d871f3fa9421e2873f7/file-A1BHZzp2RV.png)

If you have the any integrations (Hubspot, Zapier, Marketo, etc.) enabled, views and engagement from that lead will also be synced to the respective integration.

Email leads can be captured by creating a Chapter and choosing Form. From there, you can easily add a single email input (alongside other fields) and set it as an optional or required field.

Data is saved natively within your Supademo analytics or synced with your CRM (like HubSpot or Salesforce, if the integration is set up correctly).

{% hint style="info" %}
Please note that **Email Lead Capture** is a feature on Scale and Enterprise plans.
{% endhint %}


---

# 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.supademo.com/customize/chapters/email-lead-capture.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.