Capture Facebook Ads Data in Webflow Forms
Visitor counts alone do not show which Facebook campaign produced a lead. This guide explains how UTM tagging, an attribution snippet and hidden Webflow fields can carry campaign, ad set and ad information through to each form submission, so you can report on leads rather than clicks.
Why form-level attribution matters
Analytics platforms can count visits, yet they often stop short of connecting a submitted lead back to the paid campaign that brought the person to the site. A Webflow form can close that gap when the submission also carries structured source information. The practical goal is simple: for every lead, know the channel, the campaign, the ad set and the ad, plus the page where the visit began.
Step 1: Tag each Facebook destination URL
UTM parameters are extra query values appended to the destination URL. For a Facebook campaign, a consistent pattern is: utm_medium identifies paid social, utm_source identifies Facebook, utm_campaign carries the campaign name, utm_term carries the ad set name, and utm_content carries the specific ad. Keep the vocabulary stable across campaigns; changing spellings or formats creates fragmented reports later. A URL builder can help assemble the values, but consistency is the important part.
Step 2: Install the attribution snippet
Place the attribution snippet on the website so it can read how a visitor arrived, including the UTM values from the ad click. The snippet then determines the originating channel and prepares that information for form submission. Installation should be checked on the live site, not only in the builder, before testing a form.
Step 3: Add hidden fields to Webflow forms
Add hidden fields to each Webflow form that should report source. The fields listed for this workflow are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Channel Drilldown 4, Landing Page and Landing Page Group. In Webflow, the documented approach is to drag in an Embed block and paste the supplied field code. Visitors do not see these fields, but their values travel with the submission.
Step 4: Let submissions carry the attribution values
When a visitor arrives from a tagged ad, the tool captures the UTM values. If that person later submits a contact or quote form, the tool writes the derived attribution values into the hidden fields. Webflow then stores them beside the visitor's name, email and message. Test with a known campaign value and inspect the resulting submission before relying on the data.
Use the data in CRM, spreadsheets or notifications
Once the fields are captured, route them where the team works. A CRM can connect leads to customers and revenue. A CSV export from Webflow can feed spreadsheet charts. A BI tool can provide richer campaign views. For a small team, the same values can be appended to email notifications so each new lead shows its origin immediately. Before launch, run a checklist: every ad URL is tagged, naming is consistent, the snippet loads on all relevant pages, hidden fields exist on every target form, and a test submission contains the expected values.
Beyond Facebook: coverage, persistence and cleanup
The same setup can cover more than paid social. Organic search, organic social, referral and direct visits can also be classified, giving a complete lead-source picture. Storing UTM values in a browser cookie helps preserve them across pages. Normalising inconsistent values, such as facebook versus facebook.com in utm_source, reduces misclassification. Capturing the landing page URL and its group also shows whether a blog section or an individual post is producing leads.
Three reports to build first
Three reports provide a useful starting point. Leads by channel compares Facebook with other sources and supports budget decisions. Leads by network separates Facebook, Instagram, Messenger and other placements within the Facebook family. Leads by campaign over time shows which campaigns convert into leads rather than only generating clicks. Together, they move discussion from traffic volume to lead quality and campaign contribution.
| UTM parameter | Suggested Facebook value | What it identifies |
|---|---|---|
| utm_medium | Paid social | The broad media type |
| utm_source | The platform | |
| utm_campaign | Campaign name | The campaign |
| utm_term | Ad set name | The ad set |
| utm_content | Specific ad | The individual ad |
Naming pattern for tagging Facebook ad destination URLs
| Hidden field | Purpose in the submission |
|---|---|
| Channel | Primary source channel |
| Channel Drilldown 1 | First level of source detail |
| Channel Drilldown 2 | Second level of source detail |
| Channel Drilldown 3 | Third level of source detail |
| Channel Drilldown 4 | Fourth level of source detail |
| Landing Page | Exact page where the visit began |
| Landing Page Group | Grouped landing page, such as a blog section |
Fields to add to Webflow forms for attribution capture
| Report | Question it answers | Decision it supports |
|---|---|---|
| Leads by channel | How does Facebook compare with other channels? | Where to allocate marketing resources |
| Leads by network | Which Facebook-family network produces the most leads? | Which placement to emphasise |
| Leads by campaign | Which campaigns produce leads over time? | Which campaigns to refine or expand |
Example reports once attribution fields are captured in a CRM or spreadsheet
Frequently asked questions
What is the shortest setup sequence for Webflow form attribution?
Add UTM parameters to the destination URL for each campaign, ad set and ad, install the attribution snippet on the site, add the listed hidden fields to the Webflow form, then submit a test lead and check that channel, drilldown, landing page and landing page group values arrive with the submission.
How should UTM values be structured for Facebook ads?
Use medium for paid social, source for Facebook, campaign for the campaign name, term for the ad set name and content for the specific ad. Consistent naming matters more than the exact labels, because later reports group by those values.
What do hidden fields do in a Webflow form?
Hidden fields are present on the form but not visible to visitors. The attribution tool fills them in the browser, so Webflow captures them alongside the name, email and other fields a visitor enters.
Why might attribution data survive a move to another page?
The tool described stores UTM parameters in a browser cookie, so the values can still be passed when the visitor later submits a form on a different page. That differs from relying only on the first landing URL.
Where can captured Webflow form data be used?
Send the captured fields to a CRM for lead-to-customer and revenue reporting, download them as CSV for spreadsheet charts, connect a BI tool for campaign views, or include them in email notifications for teams without a CRM.
Which three reports are most useful first?
Start with leads by channel to compare Facebook with other sources, leads by network to compare Facebook, Instagram, Messenger and other placements, and leads by campaign over time to separate campaigns that produce leads from those that only produce clicks.