Skip to content

How to track leads and customers from Facebook Ads in Nutshell CRM

Facebook Ads can generate enquiries that later become opportunities and customers, but that value is hard to prove if the CRM only records who submitted a form. By tagging ad links, storing the campaign details in the browser, and passing them through hidden form fields into Nutshell CRM, each lead can carry its channel, campaign, ad set and ad with it. That makes it possible to report leads, opportunities, closed deals and revenue by the Facebook activity that produced them.

How the attribution flow works

A small script placed on the website examines how each visitor arrived, using the same kinds of signals analytics tools use. It groups the visit into a marketing channel, stores that classification in a cookie, and later copies it into hidden fields on the form the visitor completes. When the form is connected to Nutshell CRM, those hidden values travel with the contact details, so the CRM record shows both who the lead is and which channel and campaign brought them in. Landing page and landing page group can also be passed through, which helps when different pages or content sections are being tested.

Step 1: Install the snippet and prepare forms

Install the attribution snippet on the website, either directly through site settings or through a tag manager. Add five hidden fields to every lead form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. Most form builders let you drag in a hidden field type or hide an existing field in its settings. Check that each form actually submits the hidden values alongside name, email and phone before sending live traffic.

Step 2: Tag Facebook Ads with UTM parameters

Append UTM parameters to the URL behind each Facebook ad. Keep one naming convention across the account: use the medium to mark paid social, the source to mark Facebook, the campaign for the campaign name, the term for the ad set and the content for the individual ad. Consistency matters because those values become the drill-down fields in the CRM. A link builder can help assemble the final URL, and Facebook's own guidance covers where parameters are entered in Ads Manager.

Step 3: Capture the data and send it to Nutshell CRM

When a visitor arrives from a tagged ad, the parameters are saved in a cookie. If they browse other pages before submitting, the values are still available. On submission they are written into the hidden fields and sent to Nutshell CRM with the lead's contact details. From there, native CRM reporting can be used, or the data can be exported to a business intelligence tool for more detailed analysis.

Why cookie storage and clean channel mapping matter

Cookie-based storage means the campaign data survives browsing across the site, so attribution is not lost when the form is on a later page. Normalisation helps when source values vary slightly between campaigns, grouping them under the correct channel instead of splitting them. Because the same mechanism covers organic search, organic social, direct and referral visits, Facebook can be compared with the rest of the funnel on a like-for-like basis.

Three reports to run each month

Start with leads by channel to see how Facebook compares with other sources and where budget should shift. Then look at customers by campaign to find which campaigns produce buyers rather than only enquiries. Finally, review revenue by campaign and compare it with ad spend: if revenue from a campaign exceeds its cost, it is generating a positive return and may deserve more investment, while campaigns that produce revenue below cost are candidates for pausing or rework. Use the same three views each month so trends are visible rather than one-off snapshots.

UTM naming convention for Facebook Ads
UTM parameterRecommended valueWhat it identifies
utm_mediumPaid socialThe paid social channel
utm_sourceFacebookFacebook as the source
utm_campaignCampaign nameThe campaign
utm_termAd set nameThe ad set
utm_contentSpecific adThe individual ad

Recommended convention from source; exact values are chosen by the advertiser.

Example hidden-field values on form submission
Hidden fieldExample valueMeaning
ChannelPaid SocialMarketing channel
Channel Drilldown 1FacebookSource
Channel Drilldown 2Brand CampaignCampaign
Channel Drilldown 3North America Ad GroupAd set
Channel Drilldown 4Green AdSpecific ad

Worked example from source, dependent on the UTM values used behind the ad.

Monthly Facebook Ads reporting checklist
ReportQuestion it answersDecision it supports
Leads by channelHow many leads came from each channel?Where to allocate resources
Customers by campaignWhich campaigns produce new customers?Where to invest budget and time
Revenue by campaignWhat revenue did each campaign generate versus its cost?Which campaigns to scale, keep or stop

Report types described in source; figures depend on the advertiser's own CRM data.

Frequently asked questions

What should I add to Facebook Ads links to make them trackable in Nutshell CRM?

Add UTM parameters to the destination URL so the campaign, ad set and ad can be identified when the visitor later submits a form. A consistent pattern is: medium for the paid social channel, source for Facebook, campaign for the campaign name, term for the ad set, and content for the specific ad.

What if someone browses several pages before completing a form?

The attribution data is stored in a browser cookie when the visitor arrives, then written into hidden form fields at submission. That means the visitor does not need to submit on the first page they land on for the original campaign data to be carried through.

Can I compare Facebook Ads with other channels in the same CRM?

Yes. In addition to Facebook, the same setup can record visits from organic search, organic social, direct and referral traffic, so reports can compare Facebook results with other channels rather than looking at Facebook in isolation.

What happens if UTM naming is inconsistent across campaigns?

Inconsistent values such as facebook and facebook.com for the same source can be normalised to the same channel, reducing split reporting caused by naming variations. Consistent UTM naming is still recommended because it makes drill-down reporting cleaner.