How to send tracked leads from Meta directly to SprintHub.
Creating and configuring the form
Inside the Meta Business Suite, look for the section “Instant Forms” to view the listing 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: tracking with UTM
During the process of creating or editing the form, go to the “Completion”.
At this stage, select the additional action “Go to website”, this is where you can insert your website link with the UTM tags already defined.
These tags allow you to identify the exact origin of leads that came from the instant form, making it easier to follow up on campaigns.
Make sure the site has the tracking script from Sprinthub installed.
Without it, the lead will not be automatically registered and tracked within the platform
Instant forms / Lead ad forms.
'Questions' step of form creation.
'Completion' step of form creation.
Configuring the external form in Sprinthub
In System Settings → External Forms, you will see the listing of forms available for mapping. Click the gear icon to configure the form, map the fields and define page tracking.
In the “Page Tracking”, enter the same URL used in the Instant Form, including the UTM tags.
Just fill out the form as if you were a real customer. And, upon completion and clicking to be redirected to the configured site, the lead will be created automatically in Sprinthub and your UTM tags will be added automatically, as will its source. Verification of this information will be shown in the next step of the tutorial.
Accessing 'Test Form'.
Filling in contact information.
Redirect button.
Verifying the created contact
When accessing the contact created within Sprinthub, you will be able to view:
All fields mapped in the External Forms settings;
The interaction event with the Meta form;
The fbclid and the Meta lead ID, available in “Third Party Data”;
And the UTM tags recorded on the “UTM Tags”.
This information confirms that tracking and mapping were configured correctly.