> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/add-ons/forms.md).

# Forms

The Forms add-on links Umbraco Forms submissions to visitors in Umbraco Engage and adds a form submission goal type.

The Forms add-on connects Umbraco Engage to [Umbraco Forms](https://docs.umbraco.com/umbraco-forms). Once installed, Umbraco Forms submissions are linked to individual visitors in Umbraco Engage. No extra configuration is needed.

## What it adds

* Tracking of Umbraco Forms submissions per visitor, stored with the visitor profile.
* An **Umbraco Forms submission** goal type, so a form submission can count as a conversion.
* An **Analytics - VisitorId** form field that links a submission to the visitor profile in Umbraco Engage.
* A **Form Submissions** overview on the visitor profile, showing the forms submitted by that visitor.
* Visitor identification: a visitor who submits a form becomes an [Identified Profile](/umbraco-engage/marketers-and-editors/profiling.md).

## Prerequisites

* Umbraco Engage is [installed](/umbraco-engage/installation/installation.md) and [licensed](/umbraco-engage/installation/licensing.md).
* Umbraco Forms is installed with a valid license.
* The [clientside tracking script](/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/additional-measurements-with-the-analytics-scripts.md) is added to your pages. Submissions are linked to visitors without it, but the **Umbraco Forms submission** goal only fires when the script is present.

## Install the package

Install the [Umbraco.Engage.Forms](https://www.nuget.org/packages/Umbraco.Engage.Forms) package via NuGet or using your preferred approach.

{% tabs %}
{% tab title="Visual Studio Package Manager" %}

```
PM> install-package Umbraco.Engage.Forms
```

{% endtab %}

{% tab title="Console" %}

```console
dotnet add package Umbraco.Engage.Forms
```

{% endtab %}
{% endtabs %}

Build or restart your website afterwards.

## Verify the installation

1. Edit a form and add a new question. The **Analytics - VisitorId** field type should be available.
2. Go to **Engage** > **Settings** > **Goals** and select **Create goal**. The **Umbraco Forms submission** option should be available in the **Trigger** dropdown.

![Umbraco Forms submission option in the goal trigger dropdown](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-a5e90c170ae06fad3853ef25fa52ec2c850664bb%2Fengage-forms-goal-trigger.png?alt=media)

If either option is missing, see [Verify your Engage installation](/umbraco-engage/installation/troubleshooting-installs.md).

## Next steps

{% content-ref url="/pages/e378TgEYfHVa4anbpBym" %}
[Forms](/umbraco-engage/marketers-and-editors/analytics/forms.md)
{% endcontent-ref %}

{% content-ref url="/pages/YNF3eWwG1QO8UsADA6kW" %}
[Extending forms](/umbraco-engage/developers/analytics/forms.md)
{% endcontent-ref %}


---

# 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.umbraco.com/umbraco-engage/add-ons/forms.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.