Pipedrive web forms are enquiry forms built inside Pipedrive that you embed on a website or share as a link, and each submission lands in the CRM as a lead or a deal. If you are still comparing tools across CRM software in South Africa, the detail that is easy to miss is the packaging: Pipedrive sells the feature inside its LeadBooster add-on, not as part of the base plan.
That changes the decision. For a South African team the question is whether to pay for the native form block, keep the form your website already uses and push submissions across, or run both. This post is built from Pipedrive's own help pages and the POPIA text, read in October 2026, and not from a walkthrough inside a live account.
Quick Answer
Pipedrive web forms need the LeadBooster add-on, listed from $39 per company per month on monthly billing or $32.50 on annual billing (prices change), which is about R640 or R534 at the R16.42/USD index assumption (Aug 2026). A submission creates a lead or a deal. Pipedrive documents no default consent field and says embedded forms currently do not respond to consent-banner signals, so privacy wording and the timing of the embed script are for you, as the website operator, to settle under your own consent policy.
Jump to
Losing enquiries between your site and your CRM?
Send us a short description of how an enquiry travels from your website to a salesperson today and we will show you where it is most likely to go missing.
Request a flow reviewWhat Are Pipedrive Web Forms and Which Plan Includes Them?
Pipedrive's native lead-capture forms are customisable and send their data directly into the CRM, and they are included only in the LeadBooster add-on. According to Pipedrive's web forms page, the feature is not available as a standalone purchase, and the add-on can be added to any Pipedrive CRM plan.
The same page lists LeadBooster from $32.50 per company per month billed annually, or $39 per company per month billed monthly, with a 14-day free trial. Pipedrive's own LeadBooster overview adds that the trial is open even to existing customers, and lists the add-on's four parts: Prospector, Chatbot, Live Chat and Web Forms. So Pipedrive web forms pricing is a bundle price, and the other three tools come with it whether you use them or not.
What the add-on costs in Rand terms
Using the SA Digital Cost Index (SADCI) calculation assumption of R16.42/USD (Aug 2026), which is an index assumption and not a live rate:
Monthly billing: $39 × R16.42 = R640.38, about R640 a month.
Annual billing: $32.50 × R16.42 = R533.65, about R534 a month, or $390 × R16.42 = R6,403.80, about R6,404 a year.
Annual billing saves $78 a year against monthly ($468 versus $390).
The price is stated per company, not per seat, so it does not multiply with headcount. The figures exclude any VAT, banking or exchange-rate costs on your actual invoice. Compare the total with the seat prices in our CRM software pricing guide before you decide.
Setup also has a permission requirement: Pipedrive's web forms support article says the user needs deals admin permission enabled. If a marketing contractor does the site work, it follows that the form has to be built by someone with that permission inside your account (our inference from the requirement).
What Happens to a Submission After Someone Presses Send?
A completed submission creates either a new lead or a new deal in Pipedrive, and you choose which when you set up the saving options. Leads sit in the Leads Inbox, which Pipedrive describes as a dedicated space for unqualified leads, until someone converts them.
Converting is a single action. Pipedrive's Leads Inbox article says "Convert to deal" lets you define the pipeline, visibility and value, and that any person, organization, notes or files attached to the lead stay attached.
For most enquiry forms the lead route is the safer default, because a cold web enquiry is not yet an opportunity with a value, and the Leads Inbox is built to hold unqualified entries. Our recommendation, not a Pipedrive rule: send quote-request submissions straight to a deal, and everything else to the Leads Inbox.
Three things the support pages I read do not document are worth asking Pipedrive about before you buy:
- Duplicates. Whether a repeat submission from the same email address matches an existing person or creates a second one is not described. Test it with your own address.
- Form quantity. No limit on the number of forms is stated either way.
- Hidden fields and UTM tracking. Neither is mentioned. Outfunnel, a vendor that sells Pipedrive integrations, says the native forms do not capture UTM parameters. Treat that as one vendor's view and check it in your trial.
If duplicate records appear anyway, our CRM duplicate contact cleanup guide covers the clean-up routine. Email replies to these leads are a separate mechanism, covered in our post on Pipedrive email sync.
Key Takeaway
Pipedrive's native block writes each submission into the CRM as a lead or a deal, and the support pages do not document duplicate matching or UTM capture. Test a repeat submission and a tagged link in the free 14-day trial before committing to the add-on.
How Is the Capture Block Built and Placed on a Site?
The block is assembled from a mandatory introduction, input fields, optional message blocks and a final submit button, then shared as a link or embedded with code Pipedrive provides. Pipedrive's support article says the input fields can map to text, large text, single option, multiple option, date, address, monetary, numerical and phone custom fields, and to a file attachment field.
Styling covers colours, background, fonts and form style, with optional images and a toggle for Pipedrive branding. You also set a thank-you message or a redirect. A redirect gives you a stable thank-you URL to attach conversion tracking to.
The Pipedrive web forms embed options are the two on the support page, and no plugin route is described:
| Placement | How it works | Best For |
|---|---|---|
| Share as link | A direct URL you send by email or on social media | Campaigns, quotes and events where no landing page exists yet |
| Embed on your website | You paste the code Pipedrive provides into the page | A contact or quote page you control |
For spam, Pipedrive says it uses the latest version of reCAPTCHA when spam protection is switched on. If your site already fights junk submissions, our guide to WordPress form spam prevention explains the options you would otherwise use.
Tracking is a separate question: a form loaded from another provider's code may not be picked up by the tracking you set up for your own forms, so test it with a real submission and read our lead form tracking guide for what to verify.
Not sure your form submissions are being counted?
Tell us which form tool and analytics set-up you use and we will give you a fit assessment on whether a Pipedrive-hosted block will be trackable.
Get a tracking fit checkShould You Use the Native Block or Keep Your Existing Enquiry Form?
Use the native block when no form tool exists yet and Pipedrive is already chosen; keep your own form when it already carries tracking and spam filtering that you would have to rebuild. The add-on costs about R534 to R640 a month depending on billing, so the convenience has to be worth that. There are three realistic options, and none is universally better.
| Your situation | Route | Why | Best For |
|---|---|---|---|
| No form tool yet, and Pipedrive is already chosen | Native Pipedrive block | Submissions arrive in the CRM with no connector to maintain | Small teams who want one fewer system |
| A site form already in place with tracking and spam filtering | Keep it and send entries across by integration | Pipedrive's API has an Add a lead endpoint, and a lead must be linked to a person or an organization or both | Teams with a developer or an integration tool on hand |
| Design-led site where the form must match the brand | Third-party builder with a Pipedrive connection | Outfunnel reports limited design customisation in the native block, so check it against your page | Marketing-led sites that already invest in layout |
The integration route has its own costs: a connector subscription, developer time, or both, and someone has to own the failures when a submission does not arrive. Those are Pipedrive web forms alternatives rather than replacements, because they all still end in the same lead or deal record. The native block avoids the connector but adds the add-on fee.
Before choosing, read our HubSpot vs Pipedrive comparison if the tool itself is not settled, and form optimisation in South Africa for what makes enquiry forms convert at all. A capture block that is free but long converts worse than a paid one that is short.
What Does POPIA Expect From an Enquiry Capture Block?
POPIA expects the person to be told who is collecting their information and why before it is collected, and the form is where that notice lives. This section is general information and not legal advice.
Under section 18(1), as reproduced on popia.co.za (a secondary source for the Act), the responsible party must make the data subject aware of items that include the information being collected, the name and address of the responsible party, the purpose, and whether supplying it is voluntary or mandatory. The list also covers the consequences of not providing it and details of cross-border transfers.
The section's list goes further than these items and has its own exceptions, so the table below is a practical starting checklist for the block, not full compliance. The notice has to reach the person before collection, where the information is collected from them directly.
| POPIA s18(1) item | Where it can sit in the block |
|---|---|
| Who is collecting and their address | A message block under the fields naming your company and address |
| Purpose | One sentence: "to respond to your enquiry and prepare a quote" |
| Voluntary or mandatory | Mark only the fields you need as required; leave the rest optional |
| Transfer outside South Africa | A link to your privacy policy covering where the CRM data is hosted, once you have confirmed it with Pipedrive |
On Pipedrive web forms consent, the support article says there is no default consent field. The workaround is a single-option custom field with Yes and No options, set to Required, so the form cannot be submitted without it.
As the workaround reads, that suits an acknowledgement of your privacy notice, which evidences that notice was shown but is not itself consent to marketing. It is a poor fit for marketing consent, because making a marketing tick-box compulsory ties the enquiry to the newsletter. Keep any marketing option separate and un-required.
That matters because electronic direct marketing has its own rule. Section 69, as reproduced on popia.co.za, bars it unless the person consents or is an existing customer within s69(3).
Section 69(2) allows only one approach to ask a prospect for consent. The s69(3) exception applies where the details were obtained in the course of a sale, the marketing is for your own similar products or services, and the person was given a reasonable chance to object. Each message must carry sender identity and opt-out details. Answering the enquiry is one purpose; adding the person to a campaign list is another. Our POPIA email compliance guide covers the consent rules in full.
Two points specific to the product come from Pipedrive's LeadBooster cookies article. First, embedded Web Forms load a single Cloudflare cookie, __cf_bm, which Pipedrive describes as bot mitigation.
Second, the article states that Chatbot and Web Forms "don't currently detect or respond to consent management platform (CMP) signals or visitor opt-out preferences", and that you, the website operator, are generally the data controller for your visitors' personal data. Pipedrive's operator guidance is that you configure your site to prevent these scripts loading until consent is obtained. That is Pipedrive's instruction, not a POPIA rule, and whether a bot-mitigation cookie needs gating at all depends on your own consent policy.
Where the CRM data is hosted is a separate matter. POPIA section 72, as reproduced on popia.co.za, restricts transfers of personal information to a foreign third party unless a listed condition is met, such as the recipient being bound by law, binding corporate rules or a binding agreement giving adequate protection, or the person's consent. So ask Pipedrive for the hosting region and the data processing terms. Our guides on CRM security under POPIA and cross-border transfers go through the questions to ask.
Key Takeaway
For a South African site, the Pipedrive block needs a visible privacy notice covering POPIA s18(1) items, a required acknowledgement field built with the Yes/No workaround, a separate un-required marketing option, and a decision under your own consent policy on when the embed script loads, since Pipedrive currently does not read consent-banner signals.
Unsure what your enquiry form must say under POPIA?
Send us the form wording and the tools it feeds and we will run a free audit of where the personal data goes.
Book a free auditWhy South African Businesses Choose Growth Pulse Media
Growth Pulse Media is a Johannesburg digital agency founded by Dirk van Greuning, who built and scaled a large South African ecommerce business before starting the agency. All work is executed in-house and the client load is kept limited so senior attention stays on each account.
Our focus is the digital strategy that decides where enquiries come from and what happens to them, which determines whether a paid capture block earns its fee. We write about CRM selection and lead flow as a strategy question, and we are not a Pipedrive implementation partner.
Who This Is NOT For
This post suits owners and managers deciding how enquiries reach Pipedrive, and three kinds of reader will get little from it.
Anyone who wants a click-by-click build. This is a decision guide drawn from documentation. Pipedrive's help centre has the current screens.
Teams that have not chosen a CRM. Settle the tool first with the HubSpot vs Pipedrive comparison, then come back to how enquiries get in.
Anyone who needs a legal opinion. The POPIA section is general information, and the Act is reproduced here from a secondary source. Take specific questions to a POPIA practitioner.
Frequently Asked Questions
Is the Pipedrive form builder free?
No. Pipedrive says Web Forms are included only in the LeadBooster add-on, which its web forms page lists from $39 per company per month on monthly billing or $32.50 on annual billing, and prices change. A 14-day free trial is available.
What does a Pipedrive web form create when someone submits it?
It creates either a new lead or a new deal, depending on how you set the saving options. Leads sit in the Leads Inbox until you convert them to a deal.
Can a Pipedrive form be embedded on a WordPress site?
Pipedrive describes two options: share the form as a link, or embed it on your website using code it provides. The support article does not describe a dedicated WordPress plugin, so the embed code is the documented route.
Does a Pipedrive form include a POPIA consent checkbox?
No default consent field exists. Pipedrive's workaround is a single-option custom field with Yes and No options, marked Required. Pipedrive also says embedded forms currently do not respond to consent-banner signals, and its guidance is that you configure your site to hold the script back until consent is obtained.
Do I need LeadBooster if I already have a contact form?
Not necessarily. Pipedrive's API has an Add a lead endpoint, so an existing form can send submissions across through an integration. The trade-off is the connector and developer time against the add-on fee.
Need your forms and CRM to work together?
Tell us where enquiries come from and where your team answers them. We work with South African businesses on strategy, lead generation and paid media through Google Ads, Meta Ads and GA4. No obligation, and we'll get back to you within 24 hours.
Talk to Growth Pulse Media

