Track Facebook Ads leads and customers inside your CRM
Website analytics can show visits and page views, but for lead-driven businesses it rarely answers which campaigns produced enquiries or paying customers. Capturing campaign parameters at form submission and storing them on the CRM record closes that gap, letting you report leads, customers, and revenue by the activity that created them.
1. Install tracking and add hidden form fields
Install the tracking snippet using the method for your site builder, such as WordPress, Wix, or Webflow. Then add hidden fields to every lead-capture form so campaign values can travel with the visitor's name and email. Most form builders support hidden fields natively; follow the relevant builder guide for the exact placement.
2. Tag Facebook Ads with UTM parameters
UTM parameters are extra URL text that identify the campaign behind a click. For example, a destination URL can carry utm_medium=paidsocial, utm_source=facebook, and utm_campaign=brand-campaign. Keep naming consistent across campaigns, and use a documented set of values so reports group activity correctly.
3. Let the tool populate the hidden fields at submission
When a visitor arrives, the tracking tool records the channel and landing page in a browser cookie. If that visitor later submits any form, the stored values are populated into the hidden fields and submitted alongside the visible form data. This persistence matters when the conversion page differs from the first page visited.
4. Pass the values into the CRM
If the form is built into the CRM, such as HubSpot Forms or Salesforce Web-To-Lead, the values appear directly on the contact or lead record. If the form lives in a third-party builder, map the hidden fields through the same native integration or automation used for the rest of the lead data, such as Zapier.
What gets captured
Two data groups are captured. Marketing channel data identifies how the lead arrived — for example Paid Social — plus drill-down detail such as campaign, ad group, or keyword where available. Landing page data records the first page seen and its group, such as a blog section, so content performance can be compared. Inconsistent UTM spellings, such as facebook versus facebook.com, should be normalised to the same channel.
Three reports to build first
Start with leads by channel to compare Facebook Ads against Paid Search, Organic Search, Organic Social, Referral, and Direct. Next, break customers down by Meta network — Facebook, Instagram, Messenger, and others — to see where ads convert. Finally, report revenue by campaign over time to direct budget toward the campaigns generating paying customers, not just enquiries.
Pre-launch checklist
Before launch, test one Facebook click through to a form submission and confirm every hidden field lands on the CRM record. Check a second page submission to verify cookie persistence, and submit with inconsistent UTM spellings to confirm normalisation. Review the three reports above with real records before scaling spend.
| Hidden field | What it records |
|---|---|
| Channel | Broad channel such as Paid Social |
| Channel Drilldown 1 | First level of channel detail |
| Channel Drilldown 2 | Second level of channel detail |
| Channel Drilldown 3 | Third level of channel detail |
| Landing Page | First page the lead viewed |
| Landing Page Group | Category or section of that page |
Field names as listed in the source workflow; confirm exact field labels in the configured CRM before implementation.
Frequently asked questions
How do I connect Facebook Ads data to CRM records?
Add UTM parameters to the destination URL behind each Facebook campaign, install tracking code on the site, add hidden fields to lead forms, and pass the submitted values into the CRM through its native form or an integration.
Which hidden fields carry the attribution data?
Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group.
Does the data survive if a visitor browses before submitting a form?
Yes. The tracking data is stored in a browser cookie, so it can be written into the form even when the visitor completes it on a different page from the landing page.
What changes between built-in and third-party forms?
With a CRM's own form, values flow directly to the contact or lead record. With a third-party form builder, send them using the same native integration or automation tool used for the other lead fields.