Pipedrive integration
Pipedrive is on the map, not in the product yet.
Deals and contacts read from Pipedrive and matched to organic sources, so SMB pipeline traces back to pages.
How it works
Pipedrive connects through OAuth 2.0 as a Marketplace app with narrow read scopes. We read deals and persons and match them against the source fields that mark organic arrivals, attributing pipeline to the published landing pages that started those relationships. The connection is read-only, and we target Pipedrive's v2 endpoints, the current generation of the API.
In the loop, Pipedrive carries the measure step for sales-driven small and mid-sized businesses. Content stops being judged on traffic alone: a page that quietly produces deals outranks a page that only produces visits, and the opportunity engine uses that to pick what gets written next.
Best forSMBs running their pipeline in Pipedrive who want organic content measured in deals, not sessions.
Setup, step by step
- Click Connect on the Pipedrive card, which starts the Marketplace OAuth flow.
- Sign in and approve the read scopes on Pipedrive's consent screen.
- Confirm which source fields on your deals and persons mark organic arrivals.
- Review the field matching the connector proposes and adjust if your setup uses custom fields.
- Check the first attribution report linking recent deals to landing pages.
Best practices
Keep source fields filled
Attribution can only follow deals whose source data exists. Make the organic source field part of how deals are created, whether by web forms or team convention, and the trail stays intact.
Tell us about custom fields
Many Pipedrive accounts track sources in custom fields rather than defaults. The connector lets you point matching at your actual fields during setup, and that mapping is worth a careful minute.
Read won deals as the strongest signal
Open deals show promise; won deals show truth. The reports separate the two so a page's attribution is weighted by outcomes, and early promise is visible without being mistaken for revenue.
Revoke from Pipedrive any time
The OAuth grant is visible and revocable in your Pipedrive settings. Revoking ends our read access immediately, and reconnecting later picks attribution back up without data loss on our side.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
The v1 to v2 API migration is in progress
Pipedrive is migrating endpoints from v1 to v2, so integrations still leaning on v1 surfaces face deprecations as the migration advances.
How we handle itWe target the v2 endpoints and track the migration timeline, so endpoint changes are absorbed on our side and your connection does not sit on borrowed time.
developers.pipedrive.com
Attribution depends on your source data
Deals and persons created without source information cannot be matched to organic landing pages, and show up as unattributed.
How we handle itUnattributed pipeline is reported as its own visible bucket rather than hidden, and the setup step that maps your source fields keeps the attributable share as large as your data allows.
developers.pipedrive.com
Questions teams ask
- Can SearchHandled edit our deals or contacts?
No. The Marketplace app requests read scopes only. We read deals and persons for attribution and cannot create, change, or delete anything in your Pipedrive account.
- We track lead sources in a custom field. Does that work?
Yes. During setup you point the matching at whichever fields your account actually uses, default or custom, and the connector reads those.
- What if we do not use Pipedrive?
GA4 conversion tracking remains the fallback measure, and the HubSpot, Salesforce, Zoho CRM, Close, and Attio integrations cover teams on other CRMs.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Pipedrive matters moves it up the rollout.