Track Facebook Ads in Close CRM: a 4-step attribution setup
Knowing that a lead exists in Close CRM is not the same as knowing which Facebook campaign produced it. Without campaign-level attribution, a profitable campaign may be underfunded while an unprofitable one continues to consume budget. This guide explains how to carry Facebook campaign data from the ad click, through your website forms, and into Close CRM so leads, opportunities, customers and revenue can be reported by campaign.
How the attribution flow works
An attribution snippet installed on your website examines how each visitor arrived, classifies that visit into a standard marketing channel, and stores the result in a browser cookie. When the visitor later submits a form, the stored values are written into hidden fields on that form. The form submission then carries those values into connected systems, including Close CRM, alongside the person's contact details. This creates a direct path from an ad click to a CRM record without asking visitors to enter campaign information themselves.
Step 1: Install the snippet and prepare your forms
Install the attribution snippet on your website, normally through site settings or a tag manager. Then add these hidden fields to each lead-capture form: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Channel Drilldown 4. Most form builders let you add a hidden field directly or convert an existing field to hidden through its settings. Check that every form you want to measure has the same field names before testing a submission.
Step 2: Tag Facebook ads with UTM parameters
Add UTM parameters to the destination URL behind each Facebook ad. A consistent convention makes later reporting easier: UTM Medium for the paid social channel, UTM Source for Facebook, UTM Campaign for the campaign name, UTM Term for the ad set, and UTM Content for the individual ad. You may choose your own naming, but keep the mapping stable across campaigns so Close CRM reports do not fragment the same activity under multiple labels.
Step 3: Let the form capture campaign and landing-page data
When a visitor arrives from a tagged ad, the UTM values are retained in a cookie while they browse. On form submission, those values populate the hidden fields together with the visitor's name, email, phone and other submitted details. For example, a brand campaign could produce Channel = Paid Social, Channel Drilldown 1 = Facebook, Channel Drilldown 2 = Brand Campaign, Channel Drilldown 3 = North America Ad Set, and Channel Drilldown 4 = Green Ad. The landing page URL and landing page group are captured as well, making it possible to see which page or content section a campaign sent visitors to.
Step 4: Report inside Close CRM
After submission, the campaign fields arrive in Close CRM with the lead record. Use Close CRM's reporting tools, or send the data to a business intelligence tool such as Tableau or Looker for more advanced analysis. A practical starting checklist is: confirm the snippet loads on landing pages; confirm all five hidden fields exist on each form; test a tagged URL end to end; verify the values appear on the resulting Close CRM record; and check that landing page and landing page group are populated.
Three reports to build first
Three reports cover the main decisions. Leads by channel shows how Facebook compares with Google Ads, SEO and other sources. Customers by campaign shows which campaigns produce closed business each month. Revenue by campaign connects that customer activity to revenue, so spend can be compared with the revenue attributed to each campaign. In the captured example, $65,000 in new revenue was attributed to Facebook Ads in August; the decision rule illustrated was that spend below that amount would indicate a positive return, while campaign-level breakdowns show where to increase or stop investment.
Why retention and cleaning matter
Cookie-based retention means the original UTM values survive browsing across pages, improving accuracy when the converting page is not the landing page. Channel cleaning also helps when source naming varies, for example facebook versus facebook.com, by grouping both under Paid Social. Because other channels are captured too, you can compare all lead and customer origins in one place. Landing page data adds a content dimension, showing whether particular pages or page groups are associated with stronger campaign performance.
| UTM parameter | Suggested Facebook value | CRM drilldown it supports |
|---|---|---|
| UTM Medium | Paid social | Channel |
| UTM Source | Channel Drilldown 1 | |
| UTM Campaign | Campaign name | Channel Drilldown 2 |
| UTM Term | Ad set name | Channel Drilldown 3 |
| UTM Content | Specific ad | Channel Drilldown 4 |
Naming is a suggested convention; consistency matters more than the exact labels.
Frequently asked questions
Does this only work for Facebook traffic?
No. The same capture also records other origins, including Organic Search, Organic Social, Referral and Direct, so reports can compare Facebook with the rest of your pipeline rather than viewing Facebook in isolation.
What if a visitor browses before completing a form?
Yes. The values are held in a browser cookie, so a visitor can browse several pages before submitting and the original campaign details are still passed with that submission.
What if UTM naming is inconsistent between campaigns?
Inconsistent values such as facebook and facebook.com for the source can still be grouped under Paid Social, which reduces split reporting caused by naming variations.