CRM
Pipedrive teams rename stages constantly and run a pipeline per product line, which is exactly what breaks attribution tools that look for a stage called Closed Won. Attribi asks Pipedrive for deals it considers won, so your stage names, your pipelines, and the next reshuffle are all irrelevant. Every won deal becomes an offline conversion carrying its value on each ad platform you have connected, and the campaign that produced the person is written back onto their record.
No credit card required · 5-minute setup
Attribi reads the deals Pipedrive itself marks won, not a stage spelled a particular way, so renaming stages or adding a pipeline never quietly stops the flow. Each one becomes a closed-won conversion carrying the deal value and its currency.
Open deals sitting at the stages you nominate fire a qualified conversion. Pipedrive identifies stages by number rather than name, so you paste the ids from Settings under Pipelines and stages, which is fiddly once and then immune to renaming forever.
Attribi creates 16 custom fields on your Person object and fills the visitor id, first touch source, campaign and time, last touch source and campaign, and the touch count as leads convert. Your reps see the origin of a contact on the record they already have open.
Pipedrive custom fields are addressed by an opaque hash rather than a readable name, and Attribi stores that mapping at setup. It reads the click ID pair back off the person when a deal moves, so an upload can still be matched on the click with no script on your site.
A moving deal is tied back to the person Attribi already knows using the primary email and primary phone number on the linked Pipedrive person, both hashed before any upload leaves us. Records with a real email address match best.
Authorize Pipedrive from the Connections page and choose how Attribi should behave: full, where a converting visitor becomes a person if Pipedrive does not have one, or attribution only, where Attribi never creates a record and only enriches people you already own.
One button creates the custom fields and stores the hash keys Pipedrive hands back, which is what later writes and reads address. Every Pipedrive plan permits this, so unlike most CRMs there is no edition to check first. Clicking it again is safe, because fields that already exist are reused rather than duplicated.
Find the numeric ids of the stages you treat as qualified in Settings, Pipelines and stages, and paste them comma separated. Won deals need no configuration and flow either way. Leave the list empty and Attribi reports on won deals only.
Stages Attribi supports for Pipedrive.
CRM
Zoho CRM ad attribution: won Deals become offline conversions carrying their amount, and campaign history is written onto the Contact your reps read.
CRM
HubSpot ad attribution in both directions: campaign data is written onto the contact your reps already read, and closed deal revenue is pulled back out.
Ad platform
Google Ads offline conversion tracking: send qualified leads and closed-won revenue from your CRM, so your account sees CRM-verified outcomes, not just form fills.
Yes for won deals, which is where the revenue is. Attribi asks Pipedrive for deals whose status is won rather than matching a stage label, so renaming stages, running several pipelines, and reorganising them later all leave closed-won reporting untouched. Qualified detection is the part you configure, and because you give Attribi stage ids rather than stage names, renaming a qualified stage does not break that either. Moving a stage between pipelines does change its id, and that is the one case worth re-checking.
Seven of the sixteen it creates on the person: visitor id, first touch source, first touch campaign, first touch time, last touch source, last touch campaign, and touchpoint count. The rest, including the attribution path, the landing page, the referrer, and the two click ID fields, are created so the schema is complete but not written by Attribi. Attribi also creates the same 16 fields on the deal object, and does not write those at all today, so expect to see them empty in your deal view.
No. Custom field creation is available on every Pipedrive plan from Essential upward, which makes this the one CRM connection in Attribi with no edition caveat. HubSpot free portals and Salesforce Essentials both refuse programmatic field creation; Pipedrive does not. Rate limits apply to the API, but creating sixteen fields once is well inside them.
Not through Pipedrive’s own hosted WebForm, which cannot populate custom fields from URL parameters. If your forms are hosted elsewhere, or you post to the Pipedrive API yourself, the click ID field can be filled and Attribi reads it back. If not, matching falls back to hashed email and phone, which is weaker than click-level matching but is what most pixel-less setups run on. Installing the Attribi script is the reliable way to get click-level matching on Pipedrive.
Only in full mode, and only when a search by exact email finds nobody. In attribution only mode Attribi looks the person up, writes attribution onto them if they exist, and does nothing otherwise, so an outside tool never adds records to your database. A won deal with no value on it is recorded but uploads no revenue conversion, because there is no figure to send.
Updated
Sign up and connect it from the Connections page.
Start FreeNo credit card · Free forever up to 1,000 visitors