> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/strategies/meta-business/how-to-capture-utm-tags-using-meta-instant-forms.md). # How to capture UTM tags using Meta Instant Forms How to send tracked leads from Meta directly to Sprinthub. ## Creating and configuring the form Within **Meta Business Suite**, look for the section **“Instant Forms”** to view the list of all your existing forms. From there, create a new one and define which fields should be filled out by the customer (name, email, phone, etc.). #### **Important step: UTM tracking** During the form creation or editing process, go to the step **“Closing”**.\ At this stage, select the additional action **“Go to website,”** this is where you can enter your website link with the [UTM tags](/en/topics/system-settings/tracking/tracking-utm-tag.md) already defined. An example of a complete link would be: ``` http://seu-site.com/?utm_source=facebook&utm_medium=lead_form&utm_campaign=cadastro_clientes&utm_content=form_instantaneo ``` These tags make it possible to identify the exact source of leads that came from the instant form, making it easier to track campaigns. {% hint style="warning" %} Make sure the website has the [tracking script](/en/getting-started/tracking-script.md) Sprinthub installed.\ Without it, the lead will not be recorded and tracked automatically within the platform {% endhint %}

## Configuring the external form in Sprinthub In System Settings → External Forms, you will see the list of forms available for mapping. Click the gear icon to configure the form, map the fields, and set up page tracking. In the **“Page Tracking”**, enter the same URL used in the Instant Form, including the UTM tags. {% hint style="info" %} You need to have a [Meta account connected to Sprinthub](/en/topics/system-settings/account-settings/meta-accounts.md) to configure a form mapping. {% endhint %}

## Testing form submission You can perform a test submission directly through the option **“Test Forms”** within the **Meta Business Suite**, or by accessing Meta's test link:\ 👉 Just fill out the form as if you were a real customer. And when you finish and click to be redirected to the configured website, the lead will be created automatically in Sprinthub and its UTM tags will be added automatically, as well as its source. The verification of this information will be shown in the next step of the tutorial.

## Verifying the created contact When accessing the contact created within Sprinthub, you will be able to see: * All fields mapped in the External Forms settings; * The interaction event with the Meta form; * The fbclid and Meta lead ID, available in “**Third-Party Data**”; * And the UTM tags recorded in the “**UTM Tags**”. This information confirms that tracking and mapping were configured correctly.

--- # 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.sprinthub.com/en/strategies/meta-business/how-to-capture-utm-tags-using-meta-instant-forms.md?ask=&goal= ``` `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.