Skip to content

Capture Facebook Ads Data in Fluent Forms

If you run Facebook or Instagram ads, the form submission is where ad data usually disappears. Fluent Forms can store the campaign, ad set and ad a visitor clicked, but only if those values reach the form. This guide shows the four-step setup: tag the ad URLs, install the attribution script, add hidden fields, and confirm the values arrive with each submission. It also covers what to do with the captured data and how to tell a broken setup from a working one.

What you are trying to capture

Each Fluent Forms submission should carry the marketing context of the visit that produced it: the channel (for example, Paid Social), the network (Facebook or Instagram), the campaign, the ad set and the specific ad. When those values sit next to the lead's name and email, you can count leads by source instead of guessing from platform dashboards.

The setup has two moving parts. First, the ad URL must carry UTM parameters. Second, the form must have hidden fields whose names match the values the attribution script writes. If either part is missing, the submission arrives with empty attribution fields.

Step 1: Tag every active Facebook ad with UTM parameters

UTM parameters are extra text appended to the destination URL. They tell the attribution script what the visitor clicked. A tagged URL might look like this:

https://roipaths.com/integrations/fluent-forms?utm_medium=paidsocial&utm_source=facebook&utm_campaign=brand-campaign

A consistent mapping keeps reports readable. The table below shows the convention used in this guide; you can choose different values, but keep them consistent across campaigns.

UTM parameterWhat it should describeExample
utm_mediumThe channel typePaid social
utm_sourceThe networkFacebook, Instagram
utm_campaignThe campaign namebrand-campaign
utm_termThe ad set nameretargeting-30d
utm_contentThe specific adcarousel-v2

Free UTM builders are available if you prefer not to type the parameters by hand. The important rule is that every active ad points to a tagged URL, not an untagged one.

Step 2: Install the attribution script on your site

The attribution script is a small piece of code added to the website. In this guide the product is Attribution Analytics; the setup below describes how that script behaves once installed. When a visitor arrives, it reads the technical signals about how they got there and works out the origin, including Facebook Ads. When the visitor submits a form, the script writes the attribution values into the form's hidden fields, and Fluent Forms saves them with the rest of the submission.

Installation is a one-time step per site. The script must load on every page where a lead form appears, not only on the landing page, because the visitor may submit the form somewhere else.

Where the script comes from depends on the owner's signup flow: {{OWNER_TRIAL_DURATION}} and {{OWNER_TRIAL_CTA_URL}}. Installation help lives at {{OWNER_SUPPORT_URL}}.

Step 3: Add the hidden fields to your Fluent Forms form

In the Fluent Forms editor, drag a Hidden field into the form for each value you want to store. Give each field a Name and a Default Value. The field names below are the ones the attribution script expects; if a name does not match, that value will not be written.

Hidden fieldWhat it stores
ChannelThe channel type, such as Paid Social
Channel Drilldown 1The first level of detail, such as the network
Channel Drilldown 2The second level, such as the campaign
Channel Drilldown 3The third level, such as the ad set
Channel Drilldown 4The fourth level, such as the specific ad
Landing PageThe URL of the page where the visitor first landed
Landing Page GroupThe grouped path, such as /blog

Add the same hidden fields to every lead capture form you want to track. A form without them will still submit, but the attribution columns will be blank. Step-by-step hidden-field help is at {{OWNER_SUPPORT_URL}}.

Step 4: Confirm the values arrive with each submission

When a visitor reaches the site from a tagged Facebook ad, the script stores the UTM values in a cookie in the visitor's browser. The values survive navigation to other pages, so a visitor who lands on a campaign page and later submits a quote form on a different page still carries the original campaign data.

On submission, the script places the stored values into the hidden fields, and Fluent Forms records them alongside the lead's name, email and other answers. To verify the setup, submit a test form from a tagged URL and check that the Channel and Channel Drilldown fields are populated in the entry.

Where the captured data can go

Once the values are stored in Fluent Forms, you can route them to the systems your team already uses:

  • CRM. Send the attribution fields to Salesforce, Pipedrive, HubSpot or a similar CRM to report on leads, conversions and revenue by campaign.
  • Spreadsheet. Send entries to Google Sheets or Excel through a Fluent Forms integration or an automation tool, then build charts or connect a reporting tool.
  • Email notifications. Add the attribution fields to the lead notification email so the source is visible in your inbox.
  • Billing platform. Connect Stripe, Square or PayPal so revenue can be linked back to the ad that produced the customer.

Why a cookie-based approach handles the multi-page journey

A common failure is assuming the UTM parameters will be on the page where the form is submitted. They usually are not. A visitor clicks an ad, lands on a campaign page, reads more, then clicks through to a quote form on a different URL. If the form only reads the current URL, the campaign data is gone.

Storing the values in a cookie solves this. The attribution script keeps the original UTM values for the visit and writes them into the hidden fields at submission time, regardless of which page the form sits on. The same mechanism also captures non-ad sources such as organic search, direct visits and referrals, so the channel report covers all leads rather than only paid ones.

Handling inconsistent UTM values

Campaigns are often tagged by different people, and the same network may appear as facebook in one ad and facebook.com in another. A cleaning step maps these variants to a single channel, so the lead is still counted under Paid Social and the channel report stays accurate. Keep the variant list short and documented; the goal is consistent reporting, not perfect spelling in every ad.

Three reports to run once data is flowing

Leads by channel. Compare Paid Social with organic search, direct and referral to see how much of your pipeline comes from ads versus other sources.

Leads by network. If you advertise on Facebook, Instagram and Messenger, this report shows which network produces the most leads, so budget can follow the result.

Leads by campaign. A monthly view of leads per campaign shows which campaigns convert and which only generate clicks. Use it to pause or adjust campaigns that never produce form submissions.

Pre-launch checklist

  • Every active Facebook and Instagram ad points to a URL with utm_medium, utm_source, utm_campaign, utm_term and utm_content filled in.
  • The attribution script loads on every page that contains a lead form.
  • Each lead form has the seven hidden fields with names that match the expected values.
  • A test submission from a tagged URL shows populated Channel and Channel Drilldown fields in the Fluent Forms entry.
  • A test submission from an untagged URL still records a channel, such as Direct or Organic Search, rather than a blank value.
  • The CRM or spreadsheet that receives the data has matching fields for the attribution values.

When you are ready to try the setup, start here: {{OWNER_TRIAL_CTA_URL}} ({{OWNER_TRIAL_DURATION}}).

Frequently asked questions

Do I need to add UTM parameters to every Facebook ad?

Yes, if you want campaign-level reporting. Without UTM parameters, the attribution script has no campaign, ad set or ad values to write into the hidden fields, and the submission will only show a broader channel such as Paid Social or a non-ad source.

What happens if a visitor submits a form on a different page from the one they landed on?

The attribution values are stored in a cookie in the visitor's browser, so they remain available when the visitor moves to another page and submits a form there. The hidden fields receive the original campaign data rather than the URL of the form page.

Why are my hidden fields empty after a test submission?

Check three things: the ad URL carried UTM parameters, the attribution script loaded on the page where the form was submitted, and the hidden field names match the expected names exactly. A mismatch in any of these three will leave the fields blank.

Can I capture leads from Instagram and Messenger as well as Facebook?

Yes. Use utm_source to record the network, such as facebook, instagram or messenger, and the Leads by Network report will separate them. The channel remains Paid Social for all of them.

Does this only track paid campaigns?

No. The same hidden fields also record organic search, direct visits, referrals and other non-paid sources, so the channel report can compare paid and unpaid leads side by side.