# Deploying Your Form
### Finding Your Form URL
Each form has a live URL visible from the Form Dashboard.
The Form Dashboard showing the live form URL.
***
### Adding Your Form to a Website
If you are embedding your form on a website, use the Get Deployment Code function from the Form Dashboard. This gives you code to add the form as a standard link, a popup window, or an inline frame.
The Deploy Code screen showing the three embedding options — standard link, popup window, and inline frame — with the generated code displayed below.
Give this code to your web developer, or add it to your site yourself if you are comfortable doing so.
***
### Adding Your Form to a UbiQuity Email
If you are linking to a Subscribe Form from a UbiQuity email, use the Insert UbiQuity Link function when editing your email content. You can also copy and paste the URL directly.
Update and Opt Out forms should always be deployed via a UbiQuity email rather than placed on a public website. When a contact clicks the link from a UbiQuity email, the form loads pre-populated with their details.
***
### Adding Your Form to a Regular Email
If you are sending the link via a standard email client such as Outlook or Gmail, copy the URL from the Form Dashboard and paste it into your email as a plain link. Standard email clients do not support popup windows or inline frames.
***
### API
If your website or application needs to connect to a form programmatically, this can be done via the UbiQuity API. You will likely need a developer to set this up. Forms connected via the API can still trigger emails. See [API documentation](/documentation/data-and-integrations/api.md) for more detail.
---
# Agent Instructions: 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:
```
GET https://docs.ubiquity.co.nz/documentation/data-capture/forms/deploying-your-form.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.