Skip to content

Capture Facebook Ads Data in FormCraft

Facebook Ads can bring a steady flow of leads, but without per-lead attribution you cannot tell which campaign, network or ad set deserves more budget. This guide shows how to connect UTM-tagged Facebook Ads to FormCraft forms so each submission carries the source data alongside the lead's name and email. It also explains where the data can go and which reports become possible.

What you are trying to capture

The goal is to attach a small set of attribution values to every FormCraft submission. Those values describe the channel, the campaign hierarchy and the landing page. The exact hidden-field names are listed in the form controls contract that accompanies this page; use those names exactly when you build the form.

The practical result is a FormCraft entry that contains both the lead's contact details and the marketing context. That context is what lets you compare Facebook Ads against other channels later.

Step 1: Tag your Facebook Ads with UTM parameters

UTM parameters are extra text appended to the destination URL. They do not change the page itself; they give your form and analytics tools a consistent way to read the campaign context.

A typical tagged URL for a FormCraft integration page looks like this:

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

For Facebook Ads, a practical convention is:

  • UTM Medium: Paid social
  • UTM Source: Facebook, Instagram or the network where the ad runs
  • UTM Campaign: the campaign name
  • UTM Term: the ad set name
  • UTM Content: the specific ad

You can choose different values, but keep the convention stable across campaigns. Free UTM builder tools are available if you prefer not to assemble the URL by hand.

Step 2: Install the attribution script on your site

Attribution Analytics is a small snippet placed on the website. When a visitor arrives, it inspects the technical data about how they got there, including UTM parameters, and determines the origin. When the visitor submits a form, it writes the attribution values into the hidden fields, and FormCraft captures them with the rest of the submission.

Snippet delivery and installation instructions depend on the provider's current offer: {{OWNER_TRIAL_TERMS}} and {{OWNER_INSTALL_DOC_URL}}. Follow the provider's installation instructions for your site platform rather than pasting the snippet into an arbitrary location.

Step 3: Add the hidden fields in FormCraft

In the FormCraft form builder, drag a Hidden field type into the form for each value you want to capture. The field names must match the contract exactly so the script can populate them. The required set covers the channel, four drilldown levels, the landing page and the landing page group.

A useful build check is to submit a test entry from a tagged URL and confirm that every hidden field is populated. If a field is blank, check the field name first, then the script placement.

Step 4: Confirm the data reaches FormCraft

When someone clicks a tagged Facebook Ad, the script stores the UTM values in a cookie in the visitor's browser. The visitor can move between pages, read content and return later in the session. When the form is submitted, the script writes the stored values into the hidden fields, and FormCraft records them with the lead's name, email and other answers.

This cookie behaviour is the difference between a simple URL read and a durable attribution record. It means the form does not have to sit on the same page as the ad's landing page.

Where the captured data can go

Once FormCraft holds the attribution values, you can route them onward. Three common destinations are:

  • CRM: send entries to your CRM to report leads, conversions and revenue by campaign. Supported CRM integrations: {{OWNER_CRM_INTEGRATIONS}}.
  • Spreadsheet: use Zapier or FormCraft add-ons to write rows into Google Sheets or Excel, then analyse there or connect a reporting tool.
  • Email: include the attribution values in lead notification emails if email is your main response channel.

Choose the destination that matches how you already work. A CRM is the better fit when you need to connect leads to closed revenue; a spreadsheet is simpler for early-stage analysis; email is enough when you only need to see the origin at a glance.

Why a cookie-based attribution layer helps

Consider a visitor who taps a Facebook Ad and arrives on a landing page, then browses to a pricing page and opens a quote form there. If the form only reads UTM parameters from whatever URL is loaded at submit time, the campaign values from the original click are no longer present, and the entry looks like an unattributed visit.

A cookie-based layer closes that gap by keeping the values available across the session. It also absorbs naming drift, such as one campaign using utm_source=facebook and another using utm_source=facebook.com, because the tool classifies the lead into the correct channel rather than relying on an exact string match. The result is a more dependable lead count for Facebook Ads and for other channels.

Beyond Facebook Ads: other channels and landing pages

The same setup can classify leads from Paid Search, Organic Search, Organic Social, Referral and Direct. That matters when you want to compare Facebook Ads against the rest of your mix rather than judging it in isolation.

The landing page fields add a second dimension. The full landing page URL and the landing page group (for example, /blog) let you report on sections of the site and on individual pages. You can then see whether a particular blog post or campaign landing page produces more leads than another.

Three reports worth building

Once the data reaches a CRM or spreadsheet, three reports give a useful starting view:

  1. Leads by channel. Compare Facebook Ads with Paid Search, Organic Search, Organic Social, Referral and Direct. This shows where Facebook sits in the overall mix.
  2. Leads by network. If you run ads across Facebook, Instagram and Messenger, compare lead volume by network to see which placement is producing form submissions.
  3. Leads by campaign. Break leads down by campaign over time to see which campaigns produce leads rather than only clicks.

Each report answers a different budget question. Channel-level reporting supports overall allocation; network-level reporting supports placement decisions; campaign-level reporting supports creative and offer decisions.

Setup checklist

  • [ ] Every active Facebook Ad has a destination URL with UTM parameters.
  • [ ] The UTM convention is written down and used consistently.
  • [ ] The attribution snippet is installed on the site.
  • [ ] Each FormCraft form contains the required hidden fields with exact names.
  • [ ] A test submission from a tagged URL populates every hidden field.
  • [ ] The destination (CRM, spreadsheet or email) receives the attribution values.
  • [ ] At least one report is built to compare Facebook Ads with other channels.

Frequently asked questions

Do I need UTM parameters on every Facebook Ad?

Yes, if you want the attribution layer to identify the campaign, network, ad set and ad. The script reads the UTM values from the ad's destination URL. Ads without UTM parameters will not carry that context into the form.

What happens if a visitor lands on one page and submits the form on another?

The attribution values are stored in a cookie in the visitor's browser, so they remain available when the form is submitted on a different page. A URL-only method would lose the values in that journey.

Can I capture leads from channels other than Facebook Ads?

Yes. The same hidden fields can classify Paid Search, Organic Search, Organic Social, Referral and Direct leads, so you can compare Facebook Ads with the rest of your marketing mix.

Which FormCraft field type should I use for the attribution values?

Use the Hidden field type. Drag one into the form for each required value and give it the exact field name from the form controls contract.

Where can the captured data be sent?

FormCraft's native integrations or a connector such as Zapier can send the values to a CRM, a spreadsheet or a lead notification email. The right destination depends on whether you need revenue reporting, flexible analysis or a simple origin check.