Connect Pipedrive to Fibbler

You can connect Pipedrive in two ways: from inside Fibbler, or by installing the Fibbler app from the Pipedrive Marketplace. Either way you end up authorizing the same connection and land back in Fibbler ready to configure attribution.

Option A: connect from Fibbler

In Fibbler, go to Data Sources
Click "Connect CRM" and pick Pipedrive from the list. The button says "Connect LinkedIn First" and can't be clicked until LinkedIn Ads is connected
Sign in to Pipedrive and approve the requested permissions
You'll be redirected back to Fibbler's Data Sources page

Option B: install from the Pipedrive Marketplace

Open the Fibbler app in the Pipedrive Marketplace and click "Install now"
Review the requested permissions and click "Allow and Install"
If you're not signed in to Fibbler yet, you'll be asked to log in or create an account, and the installation resumes automatically afterwards
Confirm the connection when prompted, and you'll land on Fibbler's Data Sources page

Permissions Fibbler needs

Deals (full access): Fibbler reads your deals to calculate influenced pipeline and revenue, and needs write access to create the deal filters it uses for attribution tracking.
Contacts (full access): Pipedrive groups Organizations under its "Contacts" permission, so this scope is what lets Fibbler read your organizations and match them with LinkedIn ad data. Write access is needed to create the filters Fibbler relies on.
Contact Fields (full access): so Fibbler can create and update custom fields at the organization level when it syncs ad metrics back into Pipedrive (CRM sync), and the signal fields Ad Engagement Signals writes.
Access to basic information: to identify your Pipedrive workspace and default currency.

Fibbler authenticates with OAuth 2.0 and never asks for or stores your Pipedrive API token. What Fibbler writes back to Pipedrive is the filters it needs, the ad metrics it syncs into organization-level custom fields, and, if you enable Ad Engagement Signals, that feature's own fields and a note. Fibbler never edits or deletes your deals.

We never touch your contacts. Even though Pipedrive bundles Organizations and people together under one "Contacts" permission, Fibbler only ever works with organization records. It does not read, store, or modify individual people/contacts in your Pipedrive account.

Data storage: Fibbler stores company-level and deal/opportunity data from your CRM to power attribution and analytics features. This includes company names, domains, deal amounts, and deal stages. All stored data is encrypted at rest. See our Security page for details.

Configure your CRM settings

After connecting Pipedrive, make sure to complete the CRM configuration in Fibbler:

Select your sales pipelines: Pick the Pipedrive pipelines Fibbler should use for attribution. You can pick more than one, or leave it empty to include deals from all pipelines. Then click "Save Properties"

You don't map any stages for Pipedrive. Fibbler reads won and lost straight from each deal's status in Pipedrive.

What Fibbler writes to Pipedrive

Beyond the filters it needs for attribution, nothing until you turn a feature on. Two features write to your organizations, and both are off by default. On an organization that already exists they only ever write Fibbler's own fields: your name, address, owner and everything else your team maintains are never changed by us.

CRM Data Sync custom fields (optional)

CRM Data Sync is optional. If you enable it, Fibbler creates organization-level custom fields for LinkedIn impressions, clicks, engagements, paid video views, organic impressions, organic engagements and engagement level, each over a 7, 30 and 90-day window.

With the Google Ads or Meta Ads add-on, it also creates one visit field per channel and window, named Google Ads Visits (7 days), (30 days), (90 days) and the same three for Meta Ads Visits. The sync runs weekly on Sundays and only updates organizations that already exist. The details are in the Google Ads CRM Sync and Meta Ads CRM Sync docs.

Ad Engagement Signals in Pipedrive (optional)

Ad Engagement Signals sends the companies engaging with your ads to the place your team already works. With Pipedrive as a destination, a signal does four things in your workspace.

It creates six organization fields, the first time a signal writes to Pipedrive. There is one set however many signals you run:

Fibbler Signal Type — why the organization was surfaced: New, or Rising fast
Fibbler Signal Date — when Fibbler last surfaced it
Fibbler Signal Name — which signal surfaced it
Fibbler Signal Channels — which ad channels it engaged with
Fibbler Signal Why — the evidence, in one line
Created by Fibbler — set only on an organization a signal created

It keeps a saved filter, one per signal, named Fibbler: followed by the signal's name. Pipedrive has no lists, so the queue is a filter on organizations: this signal's name, and a signal date inside the last 30 days. Fibbler moves the date forward on every run, because Pipedrive's filter conditions take an absolute date and nothing relative.

It leaves a note on the organization, with the one-line reason a rep reads.

It creates an organization that is missing.Signals are optional and only run once you set one up and turn it on. When a signal sends to Pipedrive and the organization isn't there yet, we create it. Each one created this way is stamped with Created by Fibbler, so you can find them all again.

Because every organization carries only the last signal that touched it, the filter's name condition is what keeps two signals from sharing one view. Give your signals distinct names.

Uninstalling the app

You can disconnect Pipedrive at any time, from either side:

From Fibbler: go to Data Sources and click Disconnect on the Pipedrive connection. Fibbler revokes its access token and stops syncing.
From Pipedrive: uninstall the Fibbler app in your Pipedrive Marketplace settings. Fibbler is notified automatically and stops syncing your data.