Track Facebook Ads in Nimble CRM: From Click to Revenue
Knowing that a lead exists in Nimble CRM is only half the picture. The useful question is which campaign, ad set and ad produced that lead — and whether the resulting opportunity, customer and revenue justify the spend. This guide explains a four-step setup that carries Facebook Ads attribution through a website form into Nimble CRM, plus the reports that setup makes possible.
Why attribution matters before you scale or cut spend
Without source attribution, a profitable Facebook campaign can be overlooked and an unprofitable one can keep consuming budget. The risk runs both ways: scaling a winner requires evidence, and stopping a loser requires evidence too.
The workflow described here answers four practical questions inside the CRM:
- How many leads came from Facebook Ads compared with other channels?
- How many opportunities did those leads create, and which campaigns generated them?
- How many closed-won deals or customers originated from Facebook Ads, and how does their close rate compare?
- How much revenue followed, and how does revenue compare with ad spend for ROI?
How the attribution flow works
The attribution tool is a small snippet installed on the website. On each visit it examines technical signals about how the visitor arrived, classifies the visit into a marketing channel such as Paid Social, Organic Social or Paid Search, and stores that classification in a browser cookie.
When the visitor submits a form, the stored values are copied into hidden form fields. The form then sends those values, together with the visible submission data, to the connected backend — in this case Nimble CRM, and potentially also email, billing or analytics tools connected to the same form.
That design separates two jobs: the website snippet determines origin, while the form and CRM preserve the origin alongside the contact record for later reporting.
Four-step setup
Step 1 — Install the snippet and prepare the form
Install the provided snippet on the website, directly through site settings or via a tag manager such as Google Tag Manager. Then add five hidden fields to each relevant form:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Channel Drilldown 4
Most form builders support this by dragging in a Hidden field type or converting an existing field to hidden in its settings. Examples named in the source include Gravity Forms, Typeform and Jotform.
Step 2 — Tag every Facebook Ads destination with UTM parameters
UTM parameters are extra text appended to the destination URL. A consistent convention for Facebook Ads is:
- UTM Medium: Paid Social
- UTM Source: Facebook
- UTM Campaign: campaign name
- UTM Term: ad set name
- UTM Content: specific ad name
For example, a destination page with parameters for medium, source and campaign would carry those three values in its query string. Free UTM builder tools can help construct the URLs consistently.
Step 3 — Let the tool write attribution into the form
When a visitor arrives from a tagged Facebook ad, the UTM values are captured and held in a cookie as the visitor moves around the site. On form submission, they are placed into the hidden fields alongside the visitor's name, email and other details.
Worked example: a marketer promotes a CRM product with a brand campaign. A visitor clicks the ad, browses, then requests a demo. The hidden fields receive Paid Social as the channel, Facebook as Drilldown 1, the brand campaign name as Drilldown 2, the ad group name as Drilldown 3 and the ad name as Drilldown 4. The tool also captures the landing page URL and landing page group, such as the features section of the site.
Step 4 — Send the combined record into Nimble CRM
The attribution values arrive in Nimble CRM with the lead's contact details. Reports can then be built with Nimble's built-in reporting, or exported to a BI tool such as Tableau or Power BI for more advanced analysis.
What this approach adds beyond basic UTM tagging
Four capabilities distinguish this approach from simply appending UTM parameters to a URL:
- All channels, not just paid social: Direct, Referral, Organic Social and Organic Search are captured too, giving a complete origin picture for every lead and customer.
- Persistence across browsing: cookie storage means the attribution survives navigation, so a form completed on a different page still carries the original campaign data.
- Normalisation of messy UTMs: variations such as facebook versus facebook.com as the source are mapped to the same Paid Social channel, preventing fragmented reporting.
- Landing page context: the landing page URL and its group are captured alongside channel data, making it possible to assess how content sections perform.
Reports you can build — and a pre-launch checklist
Once attribution data sits on each CRM record, three report types become straightforward:
- Leads by channel — Count leads per channel to compare Facebook Ads against Google Ads, SEO and other sources, and to guide where marketing budget should shift.
- Customers by campaign — Count new customers per month, broken down by the Facebook campaign that originated them, to identify which campaigns actually produce customers rather than only enquiries.
- Revenue by campaign — Total revenue per month by originating campaign. The source gives an illustrative example of $65,000 in new revenue from Facebook Ads in August: if total Facebook spend plus agency and creative costs fall below that figure, the channel is returning a positive ROI. Breaking the same view down by campaign shows which campaigns deserve more investment and which should be paused.
A practical checklist before trusting these reports:
- Confirm every Facebook ad destination uses the same UTM convention.
- Confirm all five hidden fields exist on every lead form.
- Submit a test form from a tagged ad link and verify all fields arrive in Nimble CRM.
- Check that a visitor who browses multiple pages before submitting still carries the original attribution.
- Review channel totals for unexpected Direct or unknown volume, which can signal missing tags.
Bottom line
Attribution that reaches the CRM turns Facebook Ads from a clicks-and-costs channel into a pipeline-and-revenue channel. With UTM parameters captured at the click, preserved through the visit, written into the form and stored on the Nimble CRM record, teams can trace leads, opportunities, customers and revenue back to the campaign, ad set and ad that created them — and compare that performance with every other channel.
| Field | What it stores | Example from the worked demo scenario |
|---|---|---|
| Channel | Broad marketing channel derived from UTM data | Paid Social |
| Channel Drilldown 1 | Source platform | |
| Channel Drilldown 2 | Campaign name | Brand Campaign |
| Channel Drilldown 3 | Ad set or ad group name | North America Ad Group |
| Channel Drilldown 4 | Specific ad name | Green Ad |
| Landing page | First page the visitor arrived on | Features contact-management page |
| Landing page group | Section of the landing page | /features |
Example values are illustrative, taken from the source's worked scenario, and depend on the UTM parameters actually used behind each ad.
Frequently asked questions
What is needed to connect Facebook Ads data to a Nimble CRM lead?
Add UTM parameters to the ad destination URL, install the attribution snippet on the site, add hidden Channel and Channel Drilldown fields to the form, and connect the form to Nimble CRM so the captured values arrive with the lead record.
Does this only capture Facebook Ads traffic?
Yes. The same setup captures Direct, Referral, Organic Social and Organic Search alongside Paid Social, so reporting is not limited to Facebook traffic.
What happens if a visitor browses several pages before submitting a form?
The attribution values are stored in a browser cookie, so they persist while the visitor browses and can still be written into a form completed on a later page.
How are inconsistent UTM values handled?
Inconsistent values such as facebook and facebook.com for the source are normalised to the same channel, reducing split reporting caused by naming variations.