Skip to content

Track Facebook Ads Through to Leads and Revenue in Pipeline CRM

You can connect Facebook campaign activity to Pipeline CRM outcomes by tagging ad URLs, preserving those tags in a browser cookie, and passing them through hidden form fields. Once the values arrive with the contact record, Pipeline reporting can show leads, opportunities, customers and revenue by channel and campaign.

How the attribution chain works

Pipeline CRM normally receives contact details when a form is submitted, but it does not automatically know which ad campaign produced that contact. Closing that gap requires a chain of evidence: the ad URL must identify the campaign, the website must retain that identification during the visit, the form must carry it forward, and the CRM must store it on the resulting record.

A small website script can inspect how each visitor arrived, classify that arrival into a standard channel such as Paid Social, and keep the classification in a browser cookie. When a form is completed, the script can populate hidden fields with the channel and its drill-down values. Those fields travel with the submission into connected systems, including Pipeline CRM.

Checklist before you start:

  • Confirm who owns the website, form tool and Pipeline CRM fields.
  • Decide a consistent naming convention for medium, source, campaign, term and content.
  • Identify every form that should capture attribution, not only the first landing-page form.
  • Plan how Pipeline CRM will store the values so reports can group them reliably.
  • Test a complete visit, form submission and CRM record before launching campaign reporting.

Step 1: Install the script and add hidden fields

Install the attribution script on the website, either directly through the site settings or through a tag manager. The exact snippet and placement instructions depend on the tool selected, so use the owner-confirmed product documentation for your stack.

Then add five hidden fields to each relevant form:

  • Channel
  • Channel Drilldown 1
  • Channel Drilldown 2
  • Channel Drilldown 3
  • Channel Drilldown 4

In most form builders, you can add a hidden field type directly or change an existing field to hidden in its settings. Keep the field names consistent across forms; otherwise the same attribution value may land in different CRM fields and become difficult to report on.

Step 2: Tag every Facebook ad URL consistently

UTM parameters are appended to the destination URL so the receiving website can identify the campaign behind a click. A practical convention for Facebook advertising 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 landing page URL can be extended with utm_medium=paidsocial, utm_source=facebook and utm_campaign=brand-campaign. Consistency matters more than clever naming: use the same spelling, casing and separators everywhere, and document what each value means before campaigns go live.

Step 3: Preserve the tags until form submission

When a visitor arrives from a tagged ad, the script stores the parameters in a cookie. That solves a common failure mode: the visitor lands on one page, reads several others, and only later completes a form. Without persistence, the original campaign tags may no longer be present in the URL at submission time.

At submission, the stored values are written into the hidden fields alongside the visitor's name, email and other details. In the source example, a Facebook visit produced Paid Social as the channel, Facebook as the first drill-down, Brand Campaign as the second, North America Ad Group as the third and Green Ad as the fourth. The setup also captured the landing page and landing page group, such as a features page grouped under /features, which helps show which content path preceded the enquiry.

Failure distinction to check: if the CRM record has contact details but blank attribution fields, work backwards through the chain. First confirm the ad URL actually contained UTM parameters, then confirm the script was present on the landing page, then confirm the hidden fields existed on the submitted form, and finally confirm the form-to-CRM mapping preserved those fields.

Step 4: Report inside Pipeline CRM

Once the submission reaches Pipeline CRM, the attribution values sit on the same record as the lead's contact information. From there, Pipeline's native reporting can be used, or the data can be sent to a business intelligence tool such as Tableau or Looker for more detailed analysis.

Three useful report patterns are:

  • Leads by channel: compare Facebook volume with Organic Search, Google Ads, SEO and other sources before shifting budget.
  • Customers by campaign: show new customers per month by campaign to identify which campaigns produce buyers, not only enquiries.
  • Revenue by campaign: show monthly revenue by originating campaign and compare it with ad spend to judge return.

The source illustrates the revenue view with an example month in which $65,000 in new revenue was attributed to Facebook Ads. Treat that figure as an illustrative captured example rather than a current benchmark: the decision value comes from comparing your own attributed revenue with your own spend, campaign by campaign.

What else this setup captures

The same mechanism is not limited to Facebook. It can also classify Organic Search, Organic Social, Referral and Direct arrivals, giving a fuller picture of where every lead originated.

It also helps with messy real-world tagging. If some campaigns use utm_source=facebook and others use utm_source=facebook.com, the tool can still assign those leads to Paid Social instead of splitting one source into two report rows. Landing page and landing page group data add another dimension, showing whether blog content, feature pages or other sections are associated with enquiries.

Before relying on the reports, run a short quality check: submit test forms from each major channel, confirm the channel and drill-down values in Pipeline CRM, and confirm that inconsistent UTM spellings still roll up correctly. Clean, consistent inputs will make the resulting channel, campaign and revenue reports far easier to trust.

Frequently asked questions

If a visitor browses several pages before submitting a form, are the Facebook campaign parameters lost?

No. The cookie preserves the parameters while the visitor moves between pages, so the form they eventually submit can still receive the original campaign data.

Does this only work for Facebook traffic?

Yes. The same setup also records sources such as Organic Search, Organic Social, Referral and Direct, allowing Facebook results to be compared with the rest of the pipeline.

What happens when UTM naming is inconsistent across campaigns?

It is designed to tolerate variations such as utm_source=facebook versus utm_source=facebook.com and still assign the lead to Paid Social, reducing the effect of inconsistent naming.