How to capture Facebook Ads data in FormAssembly
If you run Meta ads and collect leads through FormAssembly, the form submission is the moment where ad data either survives or disappears. This guide shows how to tag your ads with UTM parameters, install a small tracking snippet, add the right hidden fields to your forms, and then use the captured values in a CRM or spreadsheet to see which campaigns, networks and ad sets actually produce leads.
What you are trying to capture
The goal is simple: every FormAssembly submission should record not just the lead's name and email, but the ad that brought them in. That means the campaign, the ad set, the specific ad, and the network it ran on (Facebook, Instagram, Messenger and so on).
Once those values travel with the submission, you can answer questions like how many leads came from a given campaign this month, which Meta placement performs best, and whether Facebook Ads deserve more or less budget than other channels. The same data can be pushed to a CRM or a spreadsheet for reporting.
Step 1: Tag every Facebook ad with UTM parameters
UTM parameters are extra key-value pairs appended to the destination URL. They tell your tracking setup what campaign, network and creative sent the visitor.
A typical tagged URL looks like this pattern: the page path, then a question mark, then utm_medium, utm_source and utm_campaign joined with ampersands. For a paid social campaign on Facebook, a sensible default set is:
- UTM Medium = Paid social
- UTM Source = Facebook (or Instagram, or whichever network the ad runs on)
- UTM Campaign = the campaign name
- UTM Term = the ad set name
- UTM Content = the specific ad
Choose values that mean something to you, because whatever you put here is what you will later read in reports. Free UTM builder tools can help assemble the URL correctly.
Step 2: Install the tracking snippet on your site
The tracking snippet is a short piece of code added to your website. It watches where visitors arrive from and keeps that information available until they submit a form.
After signing up, you receive the snippet and add it to your site following the installation instructions. The snippet is what makes the rest of the workflow possible, so install it before testing any form.
Step 3: Add hidden fields to your FormAssembly forms
Hidden fields are the slots that receive the ad data. Add them to every form used to collect visitor information, such as a contact form or a quote request form.
The required fields are:
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Channel Drilldown 4
- Landing Page
- Landing Page Group
FormAssembly's documentation covers how to add hidden fields to a form. The names must match exactly, because the snippet looks for these specific field names when it writes values.
Step 4: Let the data flow into the submission
With the snippet installed and the hidden fields in place, the tracking code records the visitor's source in a cookie in their browser. When the visitor submits a FormAssembly form, the code writes the Facebook Ads values into the hidden fields, and those values are stored alongside the lead's name, email and other answers.
This is the point where the ad data becomes part of the record rather than a temporary URL detail.
Field and control map
Use this map to check your form configuration before going live. Each hidden field receives a specific piece of attribution data, and each one feeds a different kind of report.
- Channel Drilldown 1 through 4 hold the channel hierarchy, moving from broad channel to finer detail such as campaign, network and ad set.
- Landing Page holds the URL of the page where the visitor first arrived.
- Landing Page Group holds a grouped version of that page, such as a blog section, so you can compare content areas.
A quick pre-launch check: confirm all six fields exist with exact names, confirm the snippet loads on every page that hosts a form, and submit one test lead from a tagged ad URL to verify the values appear in the response.
Worked example
Suppose your ad points to a FormAssembly integration page and you tag it with utm_medium=paidsocial, utm_source=facebook and utm_campaign=brand-campaign. A visitor clicks the ad, lands on that page, then navigates to a separate quote page and submits the form there.
Without cookie-based storage, the UTM values would be gone by the time the form is submitted, because the URL on the quote page has no parameters. With the snippet in place, the original values are remembered and written into the hidden fields, so the submission still shows Paid Social, Facebook and brand-campaign.
What to do with the captured data
Once the values are stored with each response, there are several ways to use them:
- Review them in FormAssembly's Responses section alongside each lead.
- Send them to a CRM such as Salesforce, Pipedrive or HubSpot and build reports on lead volume, conversion to customer and revenue.
- Route them to a Google Sheet through FormAssembly's native Google Sheets integration, then analyse in the sheet or connect a dashboard tool.
- Include them in new-lead notification emails so the source is visible in your inbox.
Why a cookie-based approach beats URL-only tracking
URL-only tracking has a structural blind spot: it can only read what is in the address bar at the instant the form is submitted. Visitors rarely behave that way. They click an ad, browse a landing page, follow an internal link to a pricing or quote page, and only then fill in the form. By that point the address bar shows a clean internal URL, so a script that inspects only the current location has nothing to read and the submission arrives with no ad source attached.
A cookie-based approach changes the timing. The ad parameters are captured on arrival and kept in the browser, so the form page does not need to carry them. The result is that a lead who wandered through several pages before converting is still credited to the ad that started the visit.
Handling inconsistent UTM values
UTM values are typed by humans, and humans are inconsistent. The same network gets labelled facebook in one campaign and facebook.com in another, often because different people built the URLs or a template was edited over time. Left alone, those two spellings look like two different sources in your reports.
A tracking layer that normalises known variants can fold both spellings into a single Paid Social channel, so channel-level totals stay trustworthy even when the raw URLs disagree. Normalisation is a safety net, not a substitute for discipline: agreeing on a fixed set of UTM values before launch still gives you cleaner campaign and ad-set breakdowns, and it saves you from having to guess later which variant meant what.
Capturing the full picture, not just Facebook
Facebook Ads are rarely the only source of leads. The same setup also records visitors arriving through Direct, Referral, Organic Social and Organic Search, so you can compare channels rather than viewing Facebook in isolation.
Landing page data adds another dimension: the page URL and a grouped version of it show which content areas generate leads, customers and revenue.
Three reports worth building
Once the data reaches a CRM or spreadsheet, these reports answer the most common budget questions:
- Leads by channel: puts paid social side by side with every other source on a monthly basis. The comparison is the point — it tells you whether Meta ads are earning their budget or whether the same money would do more work in a channel where visitors arrive already closer to buying.
- Leads by network: Meta distributes a single campaign across its own placements, so one campaign can produce leads from Facebook, Instagram and Messenger at very different rates. Splitting lead counts by placement shows where the spend is actually converting, which lets you weight budget toward the placements that deliver.
- Leads by campaign: a month-by-month count of leads attributed to each campaign. Ranking campaigns by lead volume makes it obvious which ones are carrying the account and which are candidates for more budget — or for being retired.
Pre-launch checklist
Before you rely on the numbers, confirm each of these:
- Every active Facebook ad URL includes utm_medium, utm_source and utm_campaign, with utm_term and utm_content where you want ad set and ad detail.
- The tracking snippet is installed on all pages that host a FormAssembly form.
- All six hidden fields exist with exact names: Channel Drilldown 1-4, Landing Page and Landing Page Group.
- A test submission from a tagged URL shows the expected values in the response.
- A test submission after navigating between pages still shows the original values, confirming the cookie is working.
- Your CRM or spreadsheet connection maps the hidden fields to the right properties.
Frequently asked questions
Do I need UTM parameters on every Facebook ad?
Yes. The hidden fields can only receive values that exist in the URL. If an ad has no UTM parameters, the submission will not carry campaign, network or ad set information for that lead.
Why did my UTM data disappear when the form is on a different page?
URL-only tracking reads the parameters from the page where the form is submitted. If the visitor landed on one page and submitted the form on another, the parameters are no longer in the URL. A cookie-based tracking snippet stores the original values so they survive the navigation.
What are the exact hidden field names I need?
Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Channel Drilldown 4, Landing Page and Landing Page Group. The names must match exactly for the tracking snippet to populate them.
Can I see the ad data in FormAssembly itself?
Yes. The captured values appear alongside each lead in the Responses section, and they can also be included in new-lead notification emails.
What if my UTM source values are inconsistent between campaigns?
A tracking layer that recognises variations can still group leads into the correct channel. For example, utm_source=facebook and utm_source=facebook.com can both be assigned to Paid Social. Consistent naming still makes reporting easier.
Which reports should I build first?
Start with leads by channel to compare Facebook Ads against other sources, then leads by network to see which Meta placement performs best, then leads by campaign to decide where to increase budget.