True Conversionsby Nexopath

Connecting Pipedrive

Pipedrive connects via OAuth. The webhook is registered automatically — no manual configuration is needed inside Pipedrive.

Prerequisites

  • A Pipedrive account with admin access.
  • An account already created in True Conversions.

Connection Steps

  1. In your True Conversions dashboard, open the account (client).
  2. Click CRM Integrations.
  3. In the Pipedrive card, click Connect Pipedrive.
  4. You'll be redirected to Pipedrive's authorization page. Log in if prompted.
  5. Review the permissions and click Allow and Install.
  6. You'll be redirected back to True Conversions with a success message.

When you connect, True Conversions automatically:

  • Registers a webhook that listens for deal changes in Pipedrive.
  • Creates a GCLID custom field on person records (if it doesn't already exist).

What you get depends on Value Optimization

This matters and isn't obvious from the Pipedrive side:

  • Without Value Optimization enabled (default): True Conversions only receives an event when a deal changes to won. It's a single conversion event per deal — good for straightforward Enhanced Conversions.
  • With Value Optimization enabled (on the account page): True Conversions starts receiving every stage change on the deal, with the stage name included — this is what lets you send a different value at each funnel stage (Lead → SQL → Won) instead of just one value at close.

In other words: to track the full funnel, enable Value Optimization first (see Value Optimization) — only then does Pipedrive start sending intermediate stages.

Other status changes (e.g., "open", "lost") are ignored in both cases.

GCLID Field

For Google Ads to match the offline conversion back to the original ad click, the GCLID needs to be stored on the contact record in Pipedrive. True Conversions creates this custom field automatically when you connect. To populate it:

  1. Install the True Conversions GTM tag on your site (see Setup & Tracking).
  2. Make sure your form submission or CRM integration passes the gclid value into the GCLID field on the Pipedrive person record.

If you use a form-to-CRM integration (Zapier, Make, native capture), map the hidden gclid field from your form to the Pipedrive GCLID person field.

Re-authorizing

If the OAuth token expires, the status will show Expired on the CRM Integrations page. Click Re-authorize — the existing webhook is replaced automatically.

Disconnecting

Click Disconnect on the Pipedrive card. The registered webhook stops receiving events. To fully clean up, delete it manually in Pipedrive under Settings → Tools and integrations → Webhooks.