Server-side tracking for Pipedrive
The Pipedrive server-side build is small and has one step everybody misses: the custom field has to exist on the deal, not just on the person. Deals are a separate object created by a salesperson days later, and a value written to the person does not travel there on its own. Fire on the deal-won webhook and send the real deal value rather than an average.
Free30 minutesNo obligation
Pipedrive server-side · 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 server-side · the fix
What changes — Pipedrive server-side
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 server-side · architecture
What Pipedrive exposes to a server container
The server-side build on Pipedrive specifically.
- 1
Create the custom field on the deal, not just the person
Then copy it across when the deal is created, via automation or the API.
- 2
Fire on the deal-won webhook
Not on form submission, which measures the cheapest event in the funnel.
- 3
Send the actual deal value
Not an average — the spread is the signal.
- 4
Handle lost and reopened deals
A reopened deal should not double-count when it wins.
- 5
Measure median click-to-won first
It decides whether closed-won can be uploaded at all.
Pipedrive server-side · 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 server-side · prove
The QA evidence — Pipedrive server-side
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 server-side · 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 server-side · 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 server-side · what we deliver
What the server-side build gives you on Pipedrive
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from Pipedrive won deals
Pipedrive's deals report is authoritative. Pin down which stage counts as won and whether your team uses it consistently — inconsistent stage discipline produces a number nobody can defend.
Deduplicated at every destination
On a shared event ID, verified before any existing path is removed.
Consent enforced before dispatch
A denied destination receives nothing, verified by capture rather than configuration.
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 server-side questions, answered
You need a handler for the deal-won webhook. A container is worth it once several destinations are involved; otherwise a small endpoint does the same job.
A Pipedrive automation that copies the person's custom field to the deal on creation, or your own code doing the same via the API. Then verify on a real deal rather than assuming the automation fired.
They will have no identifier unless the person record already carried one and the automation ran. That is the realistic coverage ceiling and it should be measured and stated.
Two to four days, plus a closed window of reconciliation. The field mapping is quick; measuring coverage and the cycle length is where the time goes and it is the part that matters.
Free · 30 min
Move Pipedrive events off the browser
WhatsAppFree30 minutesNo obligation
