> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/hubs-docs/creating-hubs/lead-forms-and-embeds.md).

# Lead Forms And Embeds

Options configuration to make the most of your Hubs

#### **1. Lead Forms**

Buyer Hub can be used to increase your lead pipeline. You can capture new leads and send them to your CRM or marketing platform.

* Toggle to enable lead forms.
* Click "Edit" to customize lead form settings.
* Select the **Lead Form Type**: Choose between native lead forms or custom embed forms.

**a. Storylane Native Lead Form**

This form provides four fields: `title` ,`email` , `name (optional)` , and `CTA` that are configurable. 

<div align="left"><figure><img src="https://977067722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2sKIxGF28KpCOEu2HGiB%2Fuploads%2FhEy78Kx0rzeR2SJ1FmBC%2FScreenshot%202025-12-17%20at%209.52.04%E2%80%AFPM.png?alt=media&amp;token=e93c52ef-6af3-47f5-b242-087dc113e029" alt="" width="375"><figcaption></figcaption></figure></div>

**b. Custom Embed Form**

You can build your own custom form, and copy and paste its embed code through the inbuilt lead form guide. Most commonly, we see forms built from [HubSpot](https://knowledge.hubspot.com/forms/create-forms) and [Marketo](https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/forms/creating-a-form/create-a-form.html).

* **Select when to show the lead form and set up integrations**
* Set when to display the lead form (on demo open, after 10 seconds, after 30 seconds, or after 60 seconds).
* Set up integrations and send new leads to your CRM or marketing platform.

***

#### **2. Add Custom Code**

You can add custom scripts for Google Analytics, chatbots, etc., in the header code and footer code.

<div align="left"><figure><img src="https://977067722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2sKIxGF28KpCOEu2HGiB%2Fuploads%2FHbTScwF4YNhhT6SbHlDB%2FScreenshot%202025-12-17%20at%209.53.03%E2%80%AFPM.png?alt=media&amp;token=d5c6a9c2-c870-410e-9c2e-cf89526184a7" alt="" width="375"><figcaption></figcaption></figure></div>


---

# 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://docs.storylane.io/hubs-docs/creating-hubs/lead-forms-and-embeds.md?ask=<question>&goal=<user_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.