How Do Pipedrive Web Forms Work: Configuration, Custom Fields Mapping, and Lead Routing Automation?
Quick Summary
| Topic | What You’ll Learn |
|---|---|
| Web Form Setup | How to create and embed Pipedrive CRM forms on your website |
| Custom Fields Mapping | Connecting form inputs to the right CRM fields |
| Lead Routing | Automating deal and contact assignment after form submission |
| Duplicate Handling | Preventing and merging duplicate records in Pipedrive CRM |
| Marketing Integrations | Connecting web forms to email and ad platforms |
| FAQ | Answers to the most common Pipedrive web form questions |
What Are Pipedrive CRM Web Forms and Why Do They Matter?
Every lead that fills out a form on your website represents a moment of intent. Whether they request a demo, download a resource, or ask a question, that moment needs to flow instantly and accurately into your CRM — without manual data entry, copy-paste errors, or routing delays.
Pipedrive CRM includes a native web forms feature (called LeadBooster Web Forms) that lets teams build branded, embeddable forms and connect them directly to their sales pipeline. When someone submits a form, Pipedrive CRM automatically creates a contact, a deal, or both — and can trigger routing workflows without any human intervention.
This article covers exactly how to configure Pipedrive CRM web forms from start to finish: form setup, custom field mapping, lead assignment logic, duplicate prevention, and marketing tool integrations.
How Do You Configure a Web Form in Pipedrive CRM?
Where Do You Find the Web Forms Feature?
Pipedrive CRM includes Web Forms as part of the LeadBooster add-on, available on all paid plans. To access it, navigate to Tools and Apps → LeadBooster → Web Forms from the main Pipedrive CRM menu. From there, click “Create new form” to open the form builder.
The form builder uses a drag-and-drop interface. Teams can add, reorder, and style fields without writing any code. Pipedrive CRM also provides a live preview panel so you see exactly how the form will appear to visitors before publishing.
What Form Field Types Does Pipedrive CRM Support?
Pipedrive CRM’s form builder supports the following input types:
| Field Type | Use Case |
|---|---|
| Single-line text | Name, job title, company name |
| Contact email address | |
| Phone | Contact phone number |
| Dropdown | Industry, company size, product interest |
| Checkbox | Consent, multi-select options |
| Date | Requested demo date, availability |
| Long text / textarea | Message, notes, project description |
| Numeric | Budget, headcount, quantity |
| URL | Website, LinkedIn profile |
Each field maps either to a Pipedrive CRM standard field (like “Name” or “Email”) or to a custom field you define — which is where precise mapping becomes critical.
How Do You Embed the Form on Your Website?
Once you finish building the form, Pipedrive CRM gives you three publishing options:
- Direct link — a hosted URL you share via email, ads, or social media
- Embed code — a JavaScript snippet you paste into any HTML page or CMS (WordPress, Webflow, Squarespace)
- Pop-up trigger — an inline script that displays the form as a pop-up based on user behavior
For most websites, the embed code option integrates most cleanly. Paste the snippet inside the <body> tag of the target page, and the form renders in your brand styles within a container div. Pipedrive CRM also lets you customize colors, fonts, button text, and the confirmation message visitors see after submitting.
How Do You Map Custom Fields Between Web Forms and Pipedrive CRM?
Why Does Field Mapping Matter So Much?
Field mapping determines where each piece of form data lands in Pipedrive CRM. Poor mapping — or no mapping at all — means valuable lead data ends up in free-text notes, gets lost entirely, or creates records that sales reps can’t filter or segment. Accurate mapping, by contrast, ensures every custom field in the CRM receives clean, structured data from day one.
How Do You Create and Map Custom Fields in Pipedrive CRM?
Before building your form, define all the custom fields you need in Pipedrive CRM under Settings → Data Fields. Pipedrive CRM lets you create custom fields for Contacts, Organizations, Deals, and Leads separately — so plan your field architecture with the end record type in mind.
A practical custom field setup for a B2B web form might look like this:
| Form Question | Custom Field Name | Record Type | Field Type |
|---|---|---|---|
| “What’s your company size?” | Company Size | Organization | Dropdown |
| “Which product are you interested in?” | Product Interest | Deal | Dropdown |
| “What’s your estimated budget?” | Budget Range | Deal | Dropdown |
| “How did you hear about us?” | Lead Source Detail | Contact | Single-line text |
| “Requested demo date” | Demo Requested Date | Deal | Date |
| “Additional notes” | Form Notes | Deal | Long text |
Once you create these fields in Pipedrive CRM, they become available inside the form builder’s field mapping panel. For each form question, open the mapping dropdown and select the corresponding CRM field. Pipedrive CRM then writes the answer directly into that structured field upon submission.
What Are the Most Common Field Mapping Mistakes?
Teams frequently encounter three mapping problems:
- Mapping to the wrong record type — e.g., mapping “Product Interest” to a Contact field instead of a Deal field, making it invisible in deal views
- Using free-text fields for structured data — e.g., letting “Company Size” map to a text note instead of a dropdown, which prevents filtering and automation
- Skipping UTM fields — not capturing
utm_source,utm_medium, andutm_campaignmeans attribution data never reaches Pipedrive CRM
To capture UTM parameters, add hidden fields to your Pipedrive CRM form and use JavaScript to populate them from the page URL before submission. Tools like HubSpot’s forms or Typeform handle this natively — but with Pipedrive CRM’s native forms, a small script on the hosting page handles it reliably.
How Do You Set Up Lead Routing Automation After Form Submission?
What Happens in Pipedrive CRM Immediately After a Form Submission?
When a visitor submits a Pipedrive CRM web form, the platform executes the following sequence automatically:
- Creates a Contact record (or updates an existing one)
- Creates an Organization record if a company name was submitted
- Creates a Deal or Lead record and links it to the Contact
- Populates all mapped fields with the submitted values
- Triggers any active Automation workflows connected to the new deal
That final step — triggering automations — is where routing logic lives.
How Do You Build Lead Routing Workflows in Pipedrive CRM?
Pipedrive CRM’s Automations tool (available on Advanced plan and above) lets you define trigger-action sequences. For web form submissions, the trigger is typically “Deal created” or “Lead added,” combined with condition filters based on the mapped custom fields.
A practical routing workflow for a multi-product B2B company:
Trigger: New deal created (source = web form)
“A” Condition Branch: If Product Interest = Enterprise Suite
- Assign deal owner → Enterprise Sales Team (round-robin)
- Set deal priority → High
- Add activity: Call within 2 business hours
- Send internal Slack alert to sales manager
“B” Condition Branch: If Product Interest = Starter Plan
- Assign deal owner → SMB Sales Pool (round-robin)
- Set deal priority → Medium
- Add activity: Email within 24 hours
- Enroll contact in nurture email sequence
“C” Condition Branch: If Budget Range = Under $1,000
- Tag deal as “Low Budget”
- Assign to self-serve onboarding workflow
- Send automated welcome email
What Lead Assignment Methods Does Pipedrive CRM Support?
| Method | How It Works | Best For |
|---|---|---|
| Round-robin | Cycles through a defined list of reps | Equal distribution across a team |
| Territory-based | Routes by geography or company region | Field sales teams |
| Product-based | Routes by product interest field | Multi-product companies |
| Score-based | Routes by lead score field (from integrated tool) | Teams using lead scoring |
| Manual fallback | Assigns to a default owner if no condition matches | Catch-all for edge cases |
Pipedrive CRM’s native Automations support product-based and manual assignment natively. Territory and score-based routing typically require integration with tools like Chili Piper, LeanData, or custom Zapier/Make workflows that read Pipedrive CRM field values and update the deal owner accordingly.
How Does Pipedrive CRM Handle Duplicate Records from Web Forms?
Why Do Duplicates Happen and Why Do They Cause Problems?
Duplicate records emerge when the same person submits a form more than once — or when a form submission creates a new contact for someone already in Pipedrive CRM. Duplicates cause two immediate problems: sales reps work the same lead twice without knowing it, and CRM data becomes unreliable for reporting and attribution.
How Does Pipedrive CRM Detect and Merge Duplicates?
Pipedrive CRM uses email address as the primary deduplication key. When a form submission arrives, Pipedrive CRM checks whether a contact with that email already exists. If it finds a match, it updates the existing record rather than creating a new one — preserving history while adding the new form data.
For deals, Pipedrive CRM does not automatically merge duplicates. Instead, teams should configure their routing automation to include a condition: “If an active deal already exists for this contact, skip deal creation and notify the deal owner instead.” This prevents the same rep from working two separate deal records for the same prospect.
Additionally, Pipedrive CRM includes a built-in Merge Duplicates tool under Contacts → Duplicates, which surfaces potential duplicate contacts based on name and email similarity. Running this tool monthly keeps the database clean.
For teams handling high-volume form submissions, third-party tools like Dedupely integrate directly with Pipedrive CRM and run continuous deduplication in the background — catching duplicates that slip through the native check.
How Do You Integrate Pipedrive CRM Web Forms with Marketing Tools?
Which Marketing Platforms Connect to Pipedrive CRM Forms?
Pipedrive CRM integrates with the major marketing platforms through native connections and third-party middleware:
| Platform | Integration Type | Key Data Synced |
|---|---|---|
| Mailchimp | Native (Pipedrive Marketplace) | Contact tags, list membership, email engagement |
| ActiveCampaign | Native + API | Contact fields, deal stages, automation triggers |
| HubSpot | Native two-way sync | Contacts, deals, lifecycle stages, form submissions |
| Google Ads | Via LeadsBridge or Zapier | Lead form extensions → Pipedrive CRM deals |
| Facebook Lead Ads | Via LeadsBridge or Make | Ad leads → Pipedrive CRM contacts and deals |
| Typeform | Native (Pipedrive Marketplace) | Form responses → mapped CRM fields |
| Slack | Native | Deal creation notifications to channels |
How Do You Connect Facebook Lead Ads to Pipedrive CRM?
Facebook Lead Ads bypass your website entirely — prospects submit forms inside Facebook’s interface. Connecting these leads to Pipedrive CRM requires a middleware tool like LeadsBridge or Make (formerly Integromat).
The workflow runs as follows: a prospect submits a Facebook Lead Ad form → LeadsBridge receives the submission via Facebook’s Lead Ads API → LeadsBridge maps the form fields to Pipedrive CRM fields → Pipedrive CRM creates the contact and deal, then fires any routing automations.
This integration ensures that paid social leads receive the same structured field mapping and immediate routing treatment as organic web form leads — critical for closed-loop attribution reporting.
How Do You Ensure Form Data Feeds Marketing Attribution Correctly?
Effective attribution requires that Pipedrive CRM captures not just who submitted the form, but why they arrived — meaning UTM parameters and referral source data. The most reliable setup combines:
- Hidden UTM fields on the Pipedrive CRM web form (populated via JavaScript from the URL)
- Custom Deal fields for
UTM Source,UTM Medium, andUTM Campaign - Pipedrive CRM filters and reports that group closed-won deals by those attribution fields
With this setup, marketing teams can pull a Pipedrive CRM report showing exactly which campaigns generated deals that eventually closed — giving both marketing and sales a shared view of revenue attribution.
Conclusions: Does Pipedrive CRM Web Forms Deliver on Its Promise?
Pipedrive CRM‘s web forms feature delivers genuine value for revenue teams that invest in configuring it properly. The form builder is approachable, the field mapping is flexible, and the automation layer — when built thoughtfully — turns every form submission into a structured, routed, and actionable pipeline entry within seconds.
The teams that get the most from Pipedrive CRM web forms share a common approach: they define their custom fields before building their forms, they map every question to a structured CRM field rather than a free-text note, and they build routing automations that reflect real sales logic — not generic templates. Furthermore, they connect Pipedrive CRM to their marketing platforms so that attribution data flows both ways, giving marketing credit for the leads it generates and giving sales the context it needs to convert them.
Ultimately, Pipedrive CRM web forms work best as part of a deliberate, integrated system — not as a standalone widget. When configuration, field mapping, routing, deduplication, and marketing integration all operate together, the result is a lead capture layer that sales teams actually trust and marketing teams can measure.
Frequently Asked Questions
Pipedrive CRM’s native web forms require the LeadBooster add-on, which is available as a paid upgrade on all Pipedrive CRM plans. However, teams that prefer not to use LeadBooster can still connect external form tools — such as Typeform, Gravity Forms, or Google Forms — to Pipedrive CRM via native integrations or Zapier workflows. These external tools submit data to Pipedrive CRM through the API, achieving the same outcome of automatic contact and deal creation, though the field mapping configuration happens inside the integration tool rather than the Pipedrive CRM form builder.
Pipedrive CRM’s form builder lets you customize all visible text — labels, placeholder text, button copy, and the confirmation message — in any language. For multi-region teams, the practical approach is to create separate forms for each language or region, each with its own routing automation that assigns leads to the appropriate regional rep pool. Custom fields in Pipedrive CRM are language-agnostic, so the same field schema works across all form variants. Furthermore, using separate forms per region makes attribution reporting cleaner — each form submission carries an implicit region signal that feeds into Pipedrive CRM’s deal filtering.
