> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/forms/embedding-on-your-website.md).

# Embedding on your website

If you want vendors to fill out your form without leaving your own website, you can embed it directly using a simple code snippet. The form loads inside your page and works seamlessly -- no redirects, no extra steps for vendors.

## Standalone Forms vs. Event Forms

When you share or embed a form using the methods below, the form works as a **standalone lead capture tool**. Vendors fill out the form and their submission is saved as a lead in Vendor Space -- it is not tied to any specific event.

If you want vendors to apply for a specific event (including product selection and booth checkout), link the form to an event and share the **public event page** instead. When vendors access a form through an event page, they see the event context and can select products after submitting.

> **In short:** Embed codes and direct links create leads. Event pages create event-specific applications.

## Embed Methods

Vendor Space offers three ways to share your form. Open the embed panel by navigating to **Forms** in the sidebar and clicking **Embed Code** on the form you want to share.

### Direct Link

A standalone URL that opens the form in its own page. Best for sharing via email, social media, or messaging. Copy the link and share it anywhere. Submissions are saved as leads without an event association.

### Iframe Embed

Paste this snippet into your website's HTML to embed the form directly on a page:

```html
<iframe src="https://..." width="100%" height="800" frameborder="0"></iframe>
```

The form renders inside your page. Vendors fill it out without leaving your site.

### Script Embed

A JavaScript snippet that loads the form dynamically on your page. This method adapts to your page's styling more naturally than an iframe:

```html
<script src="https://..." data-form-id="..." async></script>
```

> **Tip:** Place embed code inside a container element (such as a `<div>`) to control its width and positioning using your own site's styles.

## Customizing the Embed

* **Width:** The embed is set to 100% width by default, so it stretches to fit its container. Adjust the container's width on your site to control the form's width.
* **Height:** You may need to adjust the height attribute depending on the length of your form. A taller value prevents scrollbars within the iframe.

## Where to Use Embedded Forms

Embedded forms work well in a variety of places:

* A dedicated "Become a Vendor" or "Apply Here" page on your website
* Blog posts or announcements about upcoming events
* Partner or sponsor websites that want to help drive applications
* Social media bios or link-in-bio pages

For event-specific landing pages, use the public event page link instead so vendors see the event details and product selection.

## Things to Keep in Mind

* Submissions from embedded forms appear in Vendor Space just like any other submission. You review them the same way.
* Standalone form submissions create leads that are not assigned to an event. You can assign them to events later from the vendor's profile.
* If you update the form in Vendor Space (add fields, change questions), the embedded version updates automatically. There is no need to change the embed code.
* The form requires an active internet connection to load and submit.

> **Tip:** Test the embedded form on your website before sharing it publicly. Open it in a few different browsers and on a mobile device to make sure it looks and works the way you expect.


---

# 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://vendorspace.gitbook.io/docs/forms/embedding-on-your-website.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.