Skip to content

Sending Pipedrive conversions to Meta Ads: three methods compared

If you run Meta Ads and manage leads in Pipedrive, you have three practical routes for reporting conversions back to Meta. Each one fits a different lead source and a different amount of weekly volume. This guide walks through all three, shows where each one breaks down, and gives you a short decision checklist so you can pick the right one without guessing.

Why conversion feedback matters

Meta Ads uses conversion signals to learn who is likely to become a customer. When you send those signals from Pipedrive, Meta can compare the people who clicked and converted with the people who clicked and did not, and adjust delivery toward the first group. The practical result is that campaigns can find more of the leads your sales team actually wants.

The harder question is where in the funnel to fire the conversion. Sending it at form submission gives Meta a lot of data but says little about lead quality. Sending it at deal close says a lot about quality but may arrive too late for Meta to use. The three methods below sit at different points on that trade-off.

Method 1: a form-submission conversion tool

A dedicated conversion tool such as Converly fires a server-side conversion to Meta when a visitor submits a form, books a meeting, or starts a chat on your site. You choose a trigger (for example, a form submission) and an action (send a conversion to Meta Ads), and the tool handles the rest.

It works with Pipedrive's own web forms and with third-party form and scheduling tools such as Gravity Forms, Typeform, Jotform and Calendly. On submission, the tool collects the lead's name, email and phone, picks up the Facebook identifiers (FBCLID, _fbc and _fbp), and sends everything to Meta's Conversions API. Sending those identifiers and contact details server-side is what typically produces an Event Match Score of 9 or 10; tracking only a thank-you page visit tends to score much lower. A conversion log shows what was sent and whether Meta received it.

Use this method when:

  • You bring in fewer than 50 new customers a week. Meta generally wants 50 or more conversions per ad set per week, so the form submission is often the only stage with enough volume.
  • Your sales cycle runs longer than 7 days. Meta's click attribution window is 7 days, so a conversion fired at deal close may fall outside it.
  • You want the simplest setup. This is the fastest of the three to get running.

Method 2: a tracking script with Zapier

If you want the conversion to fire later in the sales process — when a Lead becomes a Deal, or when a Deal is marked Won — you can capture the Meta identifiers at form submission and hold them against the Pipedrive record until that stage. This approach pairs a third-party tracking script with Zapier to carry the identifiers from your website forms into Pipedrive and then back to Meta.

The setup has four steps:

  1. Install the tracking script on your site and add hidden fields for FBCLID, FBC and FBP to your lead forms.
  2. When a visitor arrives from a Meta ad, the script stores the identifiers in the browser and writes them into those hidden fields on submission, alongside the lead's name, email and phone.
  3. The submission, including the identifiers, lands in Pipedrive. Pipedrive's own web forms create a new Lead automatically; third-party tools can push data in through their Pipedrive integration or Zapier.
  4. When the lead reaches your chosen stage, a Zap triggers the Facebook Conversions action using 'Send Other Event'. That is the option that lets you map fbclid, fbp and fbc across.

Field mapping in the Zap:

  • The script's fbc field → Click ID (fbc)
  • The script's fbp field → Browser ID (fbp)

Sending these identifiers is what lifts the Event Match Score to 9 or 10 and increases how many conversions Meta can match to real people. Without them, matching relies on email address, and many people have old addresses tied to their Facebook accounts.

Use this method when:

  • Lead quality is the problem, not lead volume. Firing the conversion at Lead-to-Deal teaches Meta what a good lead looks like.
  • Leads are converted into Deals quickly — within a day or two — so the conversion lands inside the 7-day click window.
  • You have roughly 50 or more Lead-to-Deal conversions per week, which gives the algorithm enough signal to optimize.

Method 3: Conversions API for CRM

Meta's Conversions API for CRM is built specifically for Lead Ads — the in-ad form format where Meta prefills contact details from the person's Facebook or Instagram account. Lead Ads tend to produce more leads but weaker quality: forms are easy to submit by accident, the prefilled email is often stale, and the person may not have looked at your product at all.

The CRM integration closes that loop. You store the Meta Lead ID against each Pipedrive record as leads arrive. When a lead reaches a chosen stage (for example, Lead converted to Deal), a Zap using the Facebook Conversions action and 'Send a Funnel Event' maps the Meta Lead ID, contact email and contact phone back to Meta.

Before the funnel can be configured, real leads need to flow through for about a week, and Meta wants to see roughly 50 leads within a 7-day period. Once there is enough data, you open Events Manager, go to your dataset's Settings tab, find the conversion leads integration section, and define the stages of your sales funnel — the order they happen in and which stage counts as a good lead.

Use this method when:

  • You run Lead Ads (Instant Forms). It only works with the Meta Lead ID, which exists only for leads who filled in a form inside Facebook or Instagram. Website form leads should use Method 1 or 2.
  • You get plenty of leads but your sales team says they are low quality. Reporting which leads became Deals teaches the algorithm the difference. Meta's own figures put the improvement at around 21% lower cost per quality lead.
  • Leads are converted within a few weeks, even if deals take months to close. Meta wants the optimized stage to happen within 28 days of lead arrival and stops accepting updates on leads older than 90 days.
  • You have enough volume. The funnel will not activate below roughly 50 CRM events across 7 days, which in practice means a few hundred new Lead Ad leads per month and a sales team that keeps Pipedrive current. Below that, send traffic to your website and use Method 1.

Which method fits your situation

The choice is not really about preference. It comes down to where your leads come from and how much volume you have at each stage. The table below is a decision aid; read the 'why' column before committing, because the volume thresholds are the part most teams get wrong.

A simple way to frame it: send the conversion from the funnel stage that has enough volume for Meta to learn from, using the method that matches your lead source.

Pre-launch checklist

Before you switch on any of the three methods, confirm the following:

  • Lead source: are leads arriving through website forms, Lead Ads, or both? Method 3 only applies to Lead Ads.
  • Weekly volume at the chosen stage: can you clear roughly 50 conversions per ad set per week? If not, move the conversion earlier in the funnel.
  • Sales-cycle timing: will the conversion fire inside Meta's 7-day click window? If not, Method 1 is safer.
  • Identifier capture: are FBCLID, _fbc and _fbp being written into hidden fields and stored against the Pipedrive record?
  • Zap mapping: in the Facebook Conversions action, are fbc and fbp mapped to Click ID and Browser ID respectively?
  • CRM hygiene: is your sales team updating Pipedrive stages reliably? Method 3 depends on it.
  • Logging: can you see what was sent to Meta and whether it was received?

A worked example

Suppose your team runs website lead forms and closes about 20 new customers a week, with a sales cycle of three to four weeks. At 20 deals a week you are below the roughly 50 conversions per ad set per week that Meta wants, and a deal-close conversion would often land outside the 7-day click window. Method 1 fits: fire the conversion at form submission, where volume is highest and timing is inside the window.

Now suppose the same team moves to Lead Ads and starts receiving around 300 leads a month, but the sales team reports that most are junk. Volume is now high enough for Method 3, and the quality signal is exactly what the Conversions API for CRM is designed to carry. The team stores the Meta Lead ID on each Pipedrive record, fires a funnel event when a Lead becomes a Deal, and after about a week of data configures the sales funnel in Events Manager.

If the same team received only a handful of Lead Ad leads a week, Method 3 would never activate. The better move would be to send traffic to a website landing page and use Method 1 or 2.

Wrap-up

Sending conversions from Pipedrive back to Meta Ads lets Meta see which clicks became leads and customers, so it can find more people like your best customers. The method you choose should follow your lead source and your volume at each funnel stage, not a default preference. Pick the one that matches your situation, confirm the identifiers are being captured, and check the Event Match Score after launch.

Method selection by lead source and volume
Your situationBest methodWhy
Leads come from forms on your website, and you get fewer than 50 qualified leads per weekMethod 1: ConverlyThe form submission is the highest-volume point in your funnel, so it's going to give Meta the most conversions. It's also more likely to land inside Meta's 7-day attribution window, and it's a 5-minute setup.
Leads come from forms on your website, you get plenty of them, but the quality is poorMethod 2: marketing attribution software + ZapierSending the conversion when a Lead is converted into a Deal (rather than when they submit a form) teaches Meta what a good lead looks like for your business, so it can go find more of them. Only works if your sales team qualifies leads inside the 7-day window though.
Leads come from forms on your website and you want to see which campaigns produce actual Deals and revenue (not just leads)Methods 1 + 2 togetherUse Converly to send the form submission conversion (that's what Meta optimizes on), and use marketing attribution software plus Zapier to also send Deal converted and Deal won events. Those extra events give you columns in Ads Manager showing leads and Deals side by side for every campaign, and let you build audiences of actual customers.
Leads come from Lead Ads (forms inside Facebook or Instagram), you get 150+ leads a month, and your sales team keeps Pipedrive up to dateMethod 3: Conversions API for CRMThis is the only method built for Lead Ads. It uses the Meta Lead ID to tell Meta which leads your sales team converted into Deals, and Meta's own figures put the improvement at around 21% lower cost per quality lead once the feedback loop is running.
Leads come from Lead Ads, but you only get a handful of leads a weekConsider sending traffic to your website insteadMethod 3 never activates below roughly 50 CRM events a week, so at low volumes the Lead Ads feedback loop simply isn't available to you. Send people to a landing page on your site and use Methods 1 or 2 to send conversions back to Meta Ads.

The 50-conversions-per-week and 150+ leads-per-month figures are the thresholds described in the source; check Meta's current documentation for the latest requirements.

Frequently asked questions

Can I use more than one method at the same time?

Yes. The most common combination is Method 1 for the form-submission conversion (which is what Meta optimizes on) plus Method 2 for Deal converted and Deal won events. The extra events give you columns in Ads Manager showing leads and Deals side by side, and let you build audiences of actual customers.

What is an Event Match Score, and why does it matter?

It is Meta's rating of how well your conversion tracking is set up. Sending conversions server-side with the lead's name, email and phone, plus the Facebook identifiers (FBCLID, _fbc and _fbp), is what typically produces a score of 9 or 10. Tracking only a thank-you page visit tends to score much lower.

Why does the 7-day click window matter for method choice?

Meta counts a conversion against an ad click only if it happens within 7 days. If your sales cycle is longer than that, firing the conversion at deal close may fall outside the window. Firing it at form submission keeps it inside.

Does Method 3 work for leads who fill in a form on my website?

No. Method 3 depends on the Meta Lead ID, which only exists for leads who completed a form inside Facebook or Instagram. Website form leads should use Method 1 or Method 2.