Meta Conversions API setup for Pipedrive
Meta on Pipedrive means won deals sent as a Lead or Purchase event with the deal value and a stable event ID from the deal ID. Won-deal volume in B2B is often too thin for Meta to optimize on, so an earlier qualified stage usually has to carry the learning while the won deal carries the judgement.
Free30 minutesNo obligation
Pipedrive + Meta CAPI · what breaks
What goes wrong on Pipedrive
- 01
The identifier stops at the person and never reaches the deal
The single most common failure. Deals are where the value lives and where the field is usually missing.
- 02
Form fills counted as conversions
Cheap, abundant, and weakly correlated with won revenue.
- 03
Deal value ignored
A small deal and a large one are the same conversion unless the value is sent.
- 04
Long pipelines against import windows
Measure your median click-to-won before assuming a closed-won upload is possible.
Pipedrive + Meta CAPI · the fix
What changes — Pipedrive + Meta CAPI
Won deals as the conversion
From the deal's stage change, at the actual deal value.
The identifier present on the deal
Not only on the person, which is where most implementations stop.
Lost deals excluded and reopened deals handled
So the number reflects the pipeline as it actually is.
Pipedrive + Meta CAPI · architecture
How Meta tracking behaves on Pipedrive
The Meta destination on Pipedrive.
- 1
Won deals as a Lead or Purchase event
Consistently, with the deal value.
- 2
Customer data hashed from the person record
Normalized before hashing.
- 3
A stable event ID from the deal ID
So a re-sent event cannot double-count.
- 4
Lost deals not sent at all
Rather than sent and reversed, which is messier here.
- 5
Qualified-stage events where volume is thin
Meta needs volume to optimize, and won deals alone are often too sparse.
Pipedrive + Meta CAPI · diagnose
Where Pipedrive tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Open a won deal and look for the identifier field
If it is on the person and not the deal, you have found the cause.
- 02
Compare won deals against reported conversions
Per deal, over a closed window.
- 03
Check the conversion action type
Import versus website. They are not interchangeable.
- 04
Measure median click-to-won
Against every import window, before anything else is designed.
- 05
Check for stage discipline
If half the team marks won late, the dates are wrong and so is everything built on them.
Pipedrive + Meta CAPI · prove
The QA evidence — Pipedrive + Meta CAPI
Run on Pipedrive specifically, on a live conversion rather than in preview mode.
Source of truth
Pipedrive's deals report — deals marked won by won-date, at their deal values
- A test lead taken through to a won deal, with the identifier confirmed present on the deal record.
- Won deals reconciled per deal against what each platform reports, over a closed window.
- A reopened deal confirmed not to produce a second conversion.
- The median click-to-won measured and stated in writing against every import window.
- Deal values confirmed sent as actual amounts rather than an average.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Pipedrive + Meta CAPI · free audit
What we check in the free audit
- Open a won deal and look for the identifier field
- Compare won deals against reported conversions
- Check the conversion action type
- Measure median click-to-won
- Check for stage discipline
Checked against
Pipedrive's deals report — deals marked won by won-date, at their deal values
Free30 minutesNo obligation
Pipedrive + Meta CAPI · when not to buy
When you don't need this on Pipedrive
Worth reading before you buy anything, from us or anyone.
- If your median click-to-won exceeds 90 days, closed-won upload cannot work against the original click. We will say so before quoting.
- If your team's stage discipline is inconsistent, fix that first — every number here depends on it.
- Check identifier coverage on your own deals before commissioning anything. Ten minutes, and it decides the whole project.
- If you close nearly everything you quote, form-fill optimization may be defensible and this is a smaller job.
Pipedrive + Meta CAPI · what we deliver
What gets built for Meta on Pipedrive
A shared event ID on both paths
the Pipedrive deal ID
Standard event names, exactly cased
Meta matches on name and ID together, so a case difference alone produces two events.
Customer data normalized then hashed
Lowercase and trimmed email, phone in E.164. This is where nearly every low match quality score comes from.
fbc and fbp forwarded from the browser
fbc only exists if fbclid was captured on landing — a very common gap.
Written guarantee
95%+ tracking accuracy
Measured against Pipedrive's deals report — deals marked won by won-date, at their deal values. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Pipedrive + Meta CAPI questions, answered
Either, consistently, with a value. Purchase is the more natural fit when the deal represents a completed sale. What matters is that the choice is documented and that the same event is not also being sent from somewhere else.
Use the Pipedrive deal ID as the event ID. Then a retried send or a reopened-and-rewon deal cannot produce two conversions.
Email and phone from the person record, normalized before hashing. B2B contact data is usually clean, so the losses here come from skipping normalization rather than from missing fields.
Probably not on its own — Meta needs volume to learn. Send an earlier qualified stage as a secondary event for volume, and keep the won deal as the one you judge performance on.
Free · 30 min
Get Pixel and CAPI counting once on Pipedrive
WhatsAppFree30 minutesNo obligation
