Set up your bannerConfigure Your ToolsMarketing Automation and CRM

Pipedrive

How to configure Pipedrive at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features, Support marketing analytics

Overview

This guide explains how to implement different privacy configurations for Pipedrive's website lead-generation features and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. Pipedrive Chatbot, Web Forms and the paid Web Visitors add-on.

What the service does in this scope. Chatbot and embedded Web Forms load a single Cloudflare cookie, __cf_bm (third-party, 1 hour, bot protection), and a tracking script that records events (web form ID, embedded flag, URL, interaction type) for engagement statistics; this script is always used with these features. Web Visitors is powered by Dealfront (Leadfeeder) and sets _lfa and _lfa_expiry; Dealfront's consent manager creates _lfa_consent. Web Visitors collects data via Leadfeeder's AWS infrastructure and shows only company visits. Chatbot and Web Forms do not detect or respond to CMP signals; Pipedrive states that consent may be required and that the operator must prevent the scripts from loading until consent.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskWeb Forms and/or Chatbot; loaded after consent.
Configuration B — Higher riskAs A, plus Web Visitors (Dealfront) tracking; after consent.

No configuration without prior consent. Pipedrive's scripts always include event tracking.

Step 1 — Configure Pipedrive

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionUnlock additional website featuresUnlock additional website features; Support marketing analytics
2Chatbot / Web FormsLeadBooster settingsEmbedded; loaded after consentEmbedded; loaded after consent
3Web VisitorsAdd-on; Dealfront tracking scriptNot usedAfter consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. Check Pipedrive's DPA for hosting regions. Cloudflare (__cf_bm) and AWS (Web Visitors) are US enterprises subject to the US CLOUD Act; list the United States.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesUnlock additional website featuresUnlock additional website features, Support marketing analytics
Tracking methodThird party tracking (single session, cross-website)First party tracking (cross-session)
IdentifierNo identifierDevice identifiers, IP address
Data categoriesBrowsing and interaction data, User-provided dataBrowsing and interaction data, Device identifiers, IP address, User-provided data
Legal role of data recipientProcessorProcessor (Pipedrive); see Leadfeeder guide for Dealfront
Personalisation modelNo personalisationNo personalisation
Maximum storage duration1 hour (__cf_bm)Per Dealfront settings
Processing locationPer DPA; United StatesPer DPA; United States

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page