Track Facebook Ads in Sage CRM: from click to lead, customer and revenue
You can connect Facebook Ads activity to Sage CRM records by capturing campaign identifiers at the landing page, carrying them through the visit, and submitting them with the lead form. Once those values arrive in Sage CRM, reports can compare leads, opportunities, closed deals and revenue by channel and campaign.
Why connect ads to CRM records?
Without a link between ad clicks and CRM outcomes, a profitable campaign can be underfunded and a weak one can keep consuming budget. The practical fix is to attach campaign identifiers to the landing URL, preserve them during the visit, and store them on the resulting lead record. In Sage CRM those stored values become the dimension for reporting: count leads by channel, customers by campaign, and revenue by campaign, then compare each result with ad spend to judge return.
How the capture works
The attribution snippet reads technical signals about how a visitor arrived, groups the visit into a standard channel such as Paid Social, Organic Search or Paid Search, and saves the result in a browser cookie. When a form is submitted, the saved values are written into hidden form fields and travel with the name, email and phone data into Sage CRM. The same mechanism also records the landing page and landing page group, so content performance can be reviewed alongside campaign performance.
Four-step setup checklist
Install the snippet on the website, add hidden fields to every lead-capture form, tag Facebook Ads with UTM parameters, and test a submission end to end. Form builders commonly provide a hidden field type that can be dragged into a form or applied through field settings. After the test record reaches Sage CRM, check that Channel and each drilldown match the UTM values used in the ad URL before relying on reports.
UTM convention for Facebook Ads
UTM parameters are extra text appended to the destination URL. A consistent convention is: medium for the broad paid category, source for the platform, campaign for the campaign name, term for the ad set, and content for the specific ad. For example, a Sage CRM landing page URL can carry paid social as the medium, Facebook as the source, and a named brand campaign. Keeping that pattern consistent across campaigns prevents fragmented reporting.
Worked example: one Facebook lead
Channel = Paid Social; Channel Drilldown 1 = Facebook; Channel Drilldown 2 = Brand Campaign; Channel Drilldown 3 = North America Ad Set; Channel Drilldown 4 = Green Ad. That example shows the intended granularity: the first field answers which channel produced the lead, and the following fields identify the platform, campaign, ad set and ad. Landing page and landing page group can be reported separately to see which pages convert best.
What else the setup captures
Beyond Facebook, the same setup captures Direct, Referral, Organic Social and Organic Search, so Sage CRM shows the origin of all leads rather than only paid social. Cookie persistence reduces loss when visitors browse before submitting, and channel normalisation helps when source values vary slightly between campaigns. Those qualities matter because a report is only useful if every lead is assigned to one consistent channel.
Three reports to build in Sage CRM
Leads by channel shows whether Facebook is outperforming other sources and where budget should shift. Customers by campaign shows which campaigns produce new customers each month, guiding optimisation and testing. Revenue by campaign shows monthly revenue per campaign; comparing that revenue with ad spend, agency and creative costs indicates whether a campaign has a positive return and deserves more investment or should be paused. Sage CRM native reporting can be used for these views, or the data can be sent to a BI tool such as Tableau or Looker for more advanced analysis.
| Form field | Example value | Reporting use |
|---|---|---|
| Channel | Paid Social | Leads and revenue by channel |
| Channel Drilldown 1 | Platform breakdown within Paid Social | |
| Channel Drilldown 2 | Brand Campaign | Customers and revenue by campaign |
| Channel Drilldown 3 | North America Ad Set | Performance by ad set |
| Channel Drilldown 4 | Green Ad | Performance by individual ad |
Example values illustrate the drilldown pattern; use your own campaign, ad set and ad names.
Frequently asked questions
What is the shortest setup sequence?
Add UTM parameters to the ad URL, install the attribution snippet, add the five hidden fields to the form, and confirm a test submission carries Channel and drilldown values into Sage CRM alongside the lead details.
Why use Channel plus four drilldowns instead of one field?
Channel gives the broad group such as Paid Social, while drilldowns break it down by source, campaign, ad set and ad. That split lets one record be reported at channel level or campaign level without re-tagging later.
What if the visitor browses before converting?
Because the values are stored in a browser cookie when the visitor first lands. If they browse several pages before submitting, the original campaign values are still available for the form submission.
How should UTM values be structured?
Use the same naming convention across campaigns. For example, keep the source as Facebook rather than mixing Facebook and facebook.com, and keep medium as paid social. Consistent values make grouping in Sage CRM reliable.