Connect every Pipedrive deal to the journey that created it.
One connection adds this tool to your revenue journey—joined with your website, CRM and ad activity from first click to closed-won.
Sign in to install
Integration Details
Built by
Spectacle
Category
CRM
Setup Time
About 5 minutes
Sync Frequency
Real-time
Authentication
OAuth 2.0 ("Connect" from workspace settings)
Compatible With
All Pipedrive plans
Resources
Overview
Spectacle connects to Pipedrive in about 5 minutes and attributes every person created, organization created, and deal stage change to the marketing touchpoints that came before it. Pipedrive records that a deal moved to Proposal Made. Spectacle records the Google Ads click, the 3 pricing-page visits, and the colleague from the same organization who arrived through LinkedIn, and reports the deal's value against what each of those touchpoints cost.
At a glance
- Category: CRM
- Setup time: About 5 minutes
- Authentication: OAuth 2.0 ("Connect" from workspace settings)
- Pipedrive plan: All Pipedrive plans
- Spectacle plan: All Spectacle plans (Essential, Scale, Enterprise); company-level attribution on Scale and Enterprise
- Direction: Pipedrive → Spectacle. Audience and conversion syncs go Spectacle → ad platforms. Nothing is written back into Pipedrive
- Objects: Persons, organizations, deals and deal stages across every pipeline, person-organization associations, optional custom person and organization fields
- Sync: Real time
- Docs: /docs/pipedrive
- Marketplace: Pipedrive Marketplace
The gap in Pipedrive's own reporting
Pipedrive gives every lead and deal one source. The source origin and source channel fields hold a single value, set by hand or filled in when the record is created, and Insights can group won and lost deals by that one value. That is the whole of Pipedrive's attribution: no touchpoint history, no second touch, no visits before the person existed, and no ad cost next to the deal value. A deal that started with a paid search click, warmed up through 2 LinkedIn retargeting views, and converted on a webinar follow-up shows as "Webinar", or more often as blank, because the rep was busy closing it.
Spectacle sits underneath: a first-party tracking snippet on your site, your ad accounts connected, and Pipedrive stage changes turned into attribution events on the same timeline.
What syncs
- Persons: Person Created event, matched to the visitor's journey by primary email or your User Id field
- Organizations: Organization Created event; persons rolled up to the organization for account-level journeys (Scale and Enterprise plans)
- Deals and stages: Deal Created plus one event per stage change, named after your own stage, across every pipeline
- Deal properties: Value, currency, status, owner, pipeline, and stage synced to the person and the organization
- Custom person and organization fields (optional): Synced as properties you can filter and segment on
The full event list and every configuration option live in the Pipedrive docs. This page summarizes; Docs is the source of truth.
What you get
- A source for every deal, filled in by the journey. No dependence on the rep remembering the source field; the touchpoints are already on the timeline when the deal is created.
- Won value across 4 attribution models. Deal value distributed first-touch, last-touch, linear, or U-shaped, by channel, campaign, and keyword.
- Your stage names, tracked as they are. Lead In, Contact Made, Proposal Made, or whatever you called them, each becomes an event, in every pipeline you run.
- Cost per deal and per won deal by channel. Ad spend from Google, Meta, and LinkedIn joined to Pipedrive outcomes.
- Pipedrive milestones back to Google Ads. Send Deal Created or Deal Won as conversions with value so Smart Bidding optimizes toward deals, and build Customer Match lists from Pipedrive-backed segments for exclusions and retargeting.
Pairs with
Pipedrive + Google Ads (conversion and audience sync) · Pipedrive + Meta Ads · Pipedrive + Calendly · Pipedrive + CallRail · Other CRMs: HubSpot, Salesforce, Odoo
- Connect Pipedrive. Settings → Integrations → Pipedrive → Connect. Authorise through Pipedrive's OAuth screen with a user who can grant app access. About a minute.
- Configure the optional fields. User Id Field on persons and Company Id Field on organizations for identity stitching (standard field names or the 40-character custom field id), plus any custom fields you want to filter on.
- Events arrive. Person, organization, and deal changes reach Spectacle and are stitched to the visits already recorded on your site. Every pipeline is included; the pipeline name is a property on each deal event.
Step by step with screenshots: Connect Pipedrive.
- A source for every deal, filled in by the journey. No dependence on the rep remembering the source field; the touchpoints are already on the timeline when the deal is created.
- Won value across 4 attribution models. Deal value distributed first-touch, last-touch, linear, or U-shaped, by channel, campaign, and keyword.
- Your stage names, tracked as they are. Lead In, Contact Made, Proposal Made, or whatever you called them, each becomes an event, in every pipeline you run.
- Cost per deal and per won deal by channel. Ad spend from Google, Meta, and LinkedIn joined to Pipedrive outcomes.
- Pipedrive milestones back to Google Ads. Send Deal Created or Deal Won as conversions with value so Smart Bidding optimizes toward deals, and build Customer Match lists from Pipedrive-backed segments for exclusions and retargeting.
See the integration in practice
A real estate developer ran Meta and Google campaigns into a sales pipeline in their CRM and judged them on the ad platforms' own cost per lead, where the two channels looked close. Measured in Spectacle as cost per CRM contact, the contacts the sales team could call, one channel came out at $878 and the other at $128. The same pipeline view works on Pipedrive persons and deals. (Anonymized; long-funnel B2C.)
Connect every Pipedrive deal to the journey that created it.
Understand how to connect your tools, improve attribution, and build better reporting across your revenue journey.
Build
Create integrations that connect your platform with Spectacle attribution and reporting workflows.
Learn more
Get listed
Publish your integration in the Spectacle directory and help teams discover new connected workflows.
Learn more
API & Docs
Explore Spectacle APIs, setup guides, and developer documentation to build custom workflows and integrations.
Learn more
FAQ
Does Spectacle integrate with Pipedrive?
Yes. Spectacle connects to Pipedrive over OAuth and turns person creation, organization creation, deal creation, and every deal stage change into attribution events on the customer journey. Setup takes about 5 minutes and needs no custom fields or webhooks on your side.
Which Pipedrive plan do I need?
Any Pipedrive plan; the connection is made through Pipedrive's standard app authorisation. Pipedrive's own source reporting in Insights holds one source value per deal on every plan, and no plan adds multi-touch attribution or ad cost.
Does Spectacle write attribution back into Pipedrive?
No. Spectacle reads from Pipedrive and never writes back into it, unless you set that up yourself through an automation. Attribution lives in Spectacle's reports, and audiences and conversions sync from Spectacle to Google, Meta, LinkedIn, and other ad platforms, so your team keeps working in Pipedrive unchanged.
Why doesn't Pipedrive's lead source match Spectacle?
Pipedrive stores one source per record, entered by a person or set at creation. Spectacle records every visit from the first anonymous click, including visits by other people at the same organization, and applies one journey window across all channels. A deal marked "Referral" in Pipedrive often shows a paid click 6 weeks earlier in Spectacle.
Does Spectacle track my custom stages and multiple pipelines?
Yes. Every stage you have configured becomes an event named after that stage, and deals from every pipeline are included with the pipeline name as a property, so you can report attribution per pipeline. Renaming or adding a stage needs no reconfiguration.