Track Your Facebook Ads in Pipedrive in Four Steps
If you run Facebook ads but can't say how many leads, deals or customers they produced, your CRM is missing the link between spend and outcome. This guide walks through connecting a Facebook ad click to a Pipedrive record so each lead carries its channel, campaign, ad set and ad, and shows which reports turn that data into budget decisions.
Why ad-to-CRM attribution matters
Two costly mistakes sit on opposite sides of the same blind spot. If Facebook ads are producing customers at a healthy return and you never see it, you under-invest in a channel that works. If they are not producing customers at a healthy return and you never see that either, budget keeps flowing to a channel that should be cut back.
Neither mistake is fixed by looking at ad platform numbers alone. Clicks and form fills are not customers. The measurement has to happen where deals close, which for many teams is Pipedrive. Once each record carries its ad source, you can answer questions like: how many leads came from Facebook versus Google Ads or organic search; which campaigns generate the most deals; what the close rate is for Facebook-sourced opportunities compared with other sources; and how much revenue those campaigns produced against what you spent.
What the attribution tool does
The mechanism is straightforward. A small piece of code is installed on your website. When someone arrives, it reads the technical signals about how they got there — the same kind of signals analytics platforms inspect — and classifies the visit into a standard marketing channel such as Organic Search, Paid Social or Paid Search. That classification is held in a cookie in the visitor's browser.
When the visitor submits a form, the stored attribution is written into hidden fields you have added to that form, and from there it travels into whatever systems your forms feed: Pipedrive, an email platform, a billing tool, analytics.
This is what makes the following reports possible:
- Lead counts by channel, with Facebook compared against Google Ads, SEO and the rest
- Deal volume by Facebook campaign, so you can see which campaigns pull their weight
- Closed-won deals and close rates for Facebook-sourced opportunities versus other sources
- Revenue generated and the return on ad spend
Step 1: Install the tracking code and add hidden fields
Get the tracking snippet from your attribution provider and follow its installation guide. Deploy it through the supported site settings or a tag manager such as Google Tag Manager.
With the code live, add hidden fields to every lead capture form. The five fields are:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Channel Drilldown 4
Most form builders make this easy — drag a hidden field type into the form, or switch an existing field to hidden in its settings. Gravity Forms, Wix Forms and Webflow forms all support it, and per-platform guides exist.
Before moving on, confirm that the five fields exist in the form configuration and are included in its CRM mapping. Use the tagged test in Step 4 to check the values that actually arrive.
Step 2: Tag your Facebook ad URLs with UTM parameters
UTM parameters are extra text appended to the destination URL that tells the tracking layer where the click came from. If the page you are sending people to is your Pipedrive integration page, the tagged version might look like this:
example.com/integrations/pipedrive?utm_medium=paidsocial&utm_source=facebook&utm_campaign=brand-campaign
You can design the parameters however you like, but a consistent convention pays off later. A common pattern for Facebook:
- UTM Medium = Paid social
- UTM Source = Facebook
- UTM Campaign = the campaign name
- UTM Term = the ad set name
- UTM Content = the specific ad
Free UTM builders exist if you would rather not assemble the strings by hand. The important discipline is consistency: the same slot should mean the same thing across every campaign.
Step 3: Let the tool fill the hidden fields
When a visitor lands from a Facebook ad, the UTM parameters are captured and stored in the browser cookie. Because the values live in the cookie rather than the URL, they survive as the visitor moves between pages — the attribution is not lost if the form sits several clicks away from the landing page.
On submission, the stored values are written into the hidden fields and captured alongside the lead's name, email and other details.
A worked example makes this concrete. Suppose a marketer runs Facebook ads for a CRM product. A person clicks an ad, browses a few pages and completes a form. Depending on the UTM tags used, the hidden fields would receive values like:
- Channel = Paid Social
- Channel Drilldown 1 = Facebook
- Channel Drilldown 2 = Brand Campaign
- Channel Drilldown 3 = North America Ad Set
- Channel Drilldown 4 = Green Ad
Landing page information is captured too — the full landing page URL and a grouped version of it (for example, everything under /features). That lets you evaluate which content performs, not just which ad.
Step 4: Confirm the data lands in Pipedrive
The form-to-CRM connection transfers the captured channel and drilldown values to the corresponding Pipedrive record alongside the lead's contact details.
You can then use the reporting features available in your Pipedrive setup, or a BI tool such as Tableau or Looker, to analyse the mapped fields.
Test the complete route: open a tagged ad landing URL, browse to the form and submit it. Inspect the recorded form submission first, then compare its five attribution values with the new Pipedrive record. If the form has the values but Pipedrive does not, check the connector and destination field mapping. If both are empty, check the ad URL, script loading, cookie availability and hidden-field configuration before testing again.
Field and value map
Use this map to sanity-check what each hidden field should contain after a Facebook ad click. The exact values depend on the UTM tags you applied.
Why this approach over alternatives
There are other ways to move Facebook ad data into Pipedrive. Four properties make this one worth considering:
- It captures more than Facebook. Leads arriving via referral, direct, organic social or organic search are classified too, so you can see the origin of every lead rather than a Facebook-only slice.
- It stores the data. Keeping UTM values in a browser cookie means the parameters still pass through when the form is completed on a different page, which improves the accuracy of lead and customer counts.
- It normalises messy tags. Campaigns that use utm_source=facebook in one place and utm_source=facebook.com in another still resolve to the correct channel — Paid Social in this case.
- It captures landing pages. The landing page URL and page group are recorded alongside the ad data, so content performance is visible as well.
Three reports to build first
Use three reports together so lead volume does not become the only reason for a budget change.
Leads by channel. Compare the number of leads recorded for Facebook, Google Ads, organic search and other channels. Follow the comparison through to close rates and revenue before deciding where to move spend.
Customers by campaign. Group new customers by month and originating Facebook campaign. This separates campaigns that generate enquiries from those that produce closed-won deals.
Revenue by campaign. Group closed-won revenue by month and campaign to compare results with campaign costs. For a hypothetical example, suppose a campaign is credited with $65,000 of revenue in August. That supports a revenue-to-spend comparison; it does not, by itself, establish profit or justify scaling. Include the relevant costs before deciding how to change the budget.
Setup checklist
Check the complete visit-to-CRM path in order:
- Confirm the tracking script runs on ad landing pages and along the browsing path to each lead form.
- Add all five hidden fields to every lead capture form.
- Document the UTM convention and apply it to each Facebook ad URL.
- Complete a tagged test visit and inspect the attribution values in the recorded form submission.
- Confirm those same values reach the intended Pipedrive fields.
- Build a channel report and a campaign report using the populated fields.
When a test fails, locate the first point where the values disappear: the tagged visit, form capture or CRM mapping. Compare the form submission with the CRM record before changing the setup.
Getting started
Validate the full ad-click-to-record journey before relying on campaign reports. Keep the field map and UTM naming convention with your campaign setup notes so future campaigns use the same structure.
| Hidden field | Sample value | Where it comes from |
|---|---|---|
| Channel | Paid Social | Channel classification of the visit |
| Channel Drilldown 1 | UTM Source | |
| Channel Drilldown 2 | Brand Campaign | UTM Campaign |
| Channel Drilldown 3 | North America Ad Set | UTM Term |
| Channel Drilldown 4 | Green Ad | UTM Content |
Sample values are illustrative and depend on the UTM parameters actually applied to the ad. The drilldown-to-UTM mapping follows the recommended convention in the guide; other conventions are possible.
| Symptom | Likely cause | Fix |
|---|---|---|
| Form submission has no channel value | Capture script, cookie or hidden fields were unavailable | Test the tagged landing-to-form route and confirm the script and all five fields |
| Form has attribution but Pipedrive does not | Connector or destination fields are not mapped correctly | Compare form values with the CRM record and check the field mapping |
| Paid test has a channel but missing campaign drilldowns | The intended UTM values were absent or were not retained | Inspect the actual ad URL and captured values before submitting again |
| Facebook test is classified unexpectedly | UTM values do not match the configured classification rules | Check medium and source against the provider's rules, then repeat the tagged test |
These are diagnostic patterns implied by the described setup, not logged error states from a specific deployment.
Frequently asked questions
Do I need UTM parameters if I already use Facebook's own tracking?
Yes, for CRM attribution. The ad platform reports on clicks and conversions within its own view; the UTM parameters are what carry the campaign, ad set and ad identity into your form and then into Pipedrive, where deals and revenue actually live.
What happens if a visitor views several pages before filling in a form?
The UTM values are stored in a cookie in the browser, so they persist across page views and are written into the hidden fields when the form is finally submitted. That is what keeps attribution intact when the form is not on the landing page.
What if my campaigns use inconsistent UTM source values?
Values such as utm_source=facebook and utm_source=facebook.com are both resolved to the Paid Social channel, so minor inconsistencies do not break channel-level reporting. Drilldown-level reporting still depends on consistent naming, so standardise where you can.
Can I report on channels other than Facebook?
Yes. Referral, direct, organic social and organic search traffic are classified the same way, so the channel field supports comparisons across every source, not just paid social.
Do I need a BI tool to build these reports?
No. Pipedrive's native reporting tools can produce the channel and campaign breakdowns. A BI tool such as Tableau or Looker is an option if you have access and want more advanced analysis.