How to track lead source in Pipedrive

Pipedrive is the pipeline-first CRM most growing sales teams reach for. Its native fields cover the pipeline state well; what they don’t cover is which marketing channel produced each Person. SourceLoop adds: first-touch and last-touch source on every Person, the full UTM trail, the visitor’s pre-conversion journey, and multi-touch attribution models that follow Persons through to closed-won Deals.

This article covers the OAuth connect flow only. After connecting, see:

• Push UTMs and lead source to Pipedrive Person fields
• Map SourceLoop stages to Pipedrive labels and statuses

Why connect Pipedrive to SourceLoop?

Pipedrive’s native attribution is limited. SourceLoop adds:

• First-touch and last-touch source on every Person, not a single Source field
• Full UTM trail (source, medium, campaign, content, term) per touchpoint
• Multi-touch attribution models (first, last, linear, position-based, time-decay)
• Visitor journey viewable on the Person record (every page browsed pre-conversion)
• Revenue-by-channel when payment integrations are connected, attributed back to the original Person

All of this lives on Pipedrive Person, Organization, and Deal custom fields, so it shows up in Pipedrive list views, filters, and the Insights builder.

Before you start

You’ll need:

• A SourceLoop workspace with the tracking pixel installed
• A Pipedrive company account (any plan)
• A Pipedrive Admin user (required for OAuth + creating custom fields)
• Admin or Owner role in SourceLoop

Step 1: Open the CRM integrations page

1. Sign in to SourceLoop.
2. Click Setup in the left sidebar.

3. Click the CRM tab inside Setup.

4. Scroll to the Pipedrive card and click Connect.

You’ll be redirected to Pipedrive’s OAuth consent screen.

Step 2: Authorise SourceLoop on Pipedrive

1. Sign in to Pipedrive if you aren’t already.
2. Pick the Pipedrive company you want to connect (if you have multiple).
3. Review the scopes SourceLoop is requesting (read/write on Persons, Organizations, Deals, Pipelines, Stages, Users, plus custom field management).
4. Click Allow and install.

Pipedrive redirects you back to SourceLoop. The connection card flips to Connected and shows your Pipedrive company domain (e.g., acme.pipedrive.com).

Step 3: Pick what to sync

After connecting, the Pipedrive drawer opens with sync settings:

1. Inbound sync (Pipedrive → SourceLoop): pulls your existing Persons, Organizations, and Deals into SourceLoop so SourceLoop can stitch attribution onto them and dashboards reflect your real pipeline.
2. Outbound sync (SourceLoop → Pipedrive): pushes UTM and source data from SourceLoop into Pipedrive custom fields on Person, Organization, and Deal records.
3. Sync scope — choose between Contacts and Deals (most teams) or Deals only (if you don’t want SourceLoop touching the Person object).

Most teams enable both directions and the full Contacts and Deals scope. Click Save to start the first sync.

Step 4: Wait for the initial sync

The initial sync pulls existing Pipedrive records into SourceLoop. Duration depends on volume:

• Small account (under 5k Persons): under 5 minutes
• Mid-size (5k-50k): 10-30 minutes
• Large (50k+): up to a couple of hours

The sync runs server-side. Watch the Last sync timestamp on the Pipedrive card.

After the initial run, deltas sync every 15 minutes automatically.

What gets written to Pipedrive

Out of the box, SourceLoop creates and writes to these custom fields on the Person object:

• sourceloop_first_source, sourceloop_first_medium, sourceloop_first_campaign, etc.
• sourceloop_latest_source, sourceloop_latest_medium, sourceloop_latest_campaign, etc.
• sourceloop_first_landing_page, sourceloop_latest_landing_page
• sourceloop_id — internal link (don’t delete or edit)

These custom fields are created on Pipedrive’s side automatically the first time SourceLoop writes to them, no manual setup required (provided the connecting user is an Admin).

For mapping to your own existing custom fields or to push to Organizations and Deals, see Push UTMs and lead source to Pipedrive Person fields.

What’s next

• Field mapping — by default SourceLoop maps to its own sourceloop_* fields. To map to your existing fields or push to Organization / Deal custom fields, see Push UTMs to Pipedrive.
• Label / status mapping — translate SourceLoop’s lifecycle stages into Pipedrive label_ids and deal stages. See Map SourceLoop stages to Pipedrive labels.
• Troubleshooting — if a sync looks stuck or fields aren’t writing, see Troubleshoot Pipedrive sync issues.