.jpg)
Pardot Forms (now part of Salesforce Marketing Cloud Account Engagement) are one of the fastest ways to capture leads directly into your Salesforce ecosystem — no middleware, no extra sync, no integration headaches. For marketing teams already working inside Salesforce, they're the path of least resistance. But Pardot Forms also come with real constraints: limited field mapping, styling restrictions, and no native multi-step support. This guide walks through where Pardot Forms shine, where they fall short, how they compare to Form Handlers, and when it's worth reaching for a third-party alternative like FormAssembly or HubSpot.
What Are Pardot Forms?
Pardot Forms are native lead capture forms in Marketing Cloud Account Engagement, the platform many teams still know by its former name, Pardot. They are built in the Classic Form Wizard, then either hosted on a Pardot landing page or embedded into your website with an iframe. When someone submits the form, the data is captured in Account Engagement and connected to a Prospect record that can sync with Salesforce.
They occupy a very specific place in the Salesforce form ecosystem. Pardot Forms are not the same as Form Handlers, which let you process submissions from custom-built forms. They are also different from Web-to-Lead, which is a standard Salesforce feature outside Pardot, and from third-party tools like Typeform, HubSpot, or FormAssembly.
The right choice depends on how much control you need, who owns the form, and how complex the experience has to be. Pardot Forms are often the fastest option when marketing needs to launch a simple lead capture form without developer support. But they also come with design, tracking, and flexibility limits — and those limits matter once your forms become part of a more polished website or campaign experience.
Strengths of Pardot Forms
Limitations of Pardot Forms
Prospect-only field mapping: Pardot Forms only support standard and custom Prospect fields. Fields related to Prospect Accounts, Opportunities, or custom objects cannot be used. This ensures consistent data structure but limits complex data collection.
Styling constraints: Custom CSS is often required to match brand design.
No multi-step forms: Forms are single-page only; no native support for step-by-step flows.
Limited UI/UX control: Less flexible than modern design-centric tools.
Classic Builder dependency: Forms must be built using the Classic Form Wizard.
Iframe tracking limitations: Forms embedded in iframes are harder to track — though solvable with Google Tag Manager and GA4.
If you need to create or update related records, consider using third-party form solutions from Salesforce AppExchange or switching to Form Handlers.
Pardot Forms vs Form Handlers
Both Pardot Forms and Form Handlers send data into Account Engagement, but they are not interchangeable. They solve different problems, and choosing the wrong option is one of the most common mistakes Pardot admins make.
Pardot Forms are created and managed directly inside Pardot. Your marketing team can configure fields, styling, and completion actions in the Classic Form Wizard, then embed the form with an iframe or place it on a Pardot landing page. They are quick to launch and do not require developer support. The trade-off is that you are working within Pardot’s limits: the form is tied to Prospect fields and the built-in Pardot styling system.
Form Handlers give you more flexibility. Instead of building the form in Pardot, you create it wherever you need it — on your website, a Webflow page, a custom React component, or another front-end experience. The Form Handler simply receives the POST submission and sends the data into Pardot. This gives you full control over the design, user experience, multi-step flows, custom validation, and advanced logic. The downside is that the form itself has to be built and maintained by you or your development team.
A simple way to choose: use Pardot Forms when marketing needs to own the form from start to finish. Use Form Handlers when the form is part of a custom website experience or needs more flexibility than the Classic Form Builder can provide.
Ideal Use Cases for Pardot Forms
When to Consider Alternatives
Alternative Options Worth Exploring
Common Issues with Pardot Forms
Most Pardot Forms problems fall into a small set of recurring issues. Here's how to diagnose them.
Form Submissions Aren't Reaching Salesforce
Usually a completion action misconfiguration or a Prospect field validation rule blocking the write. Check the form's completion actions, verify the Prospect field types match what the form sends, and look at the form's error log under Form Analytics.
Form Styling Doesn't Match the Website
Pardot Forms use the Layout Templates system, which expects custom CSS for brand alignment. If the form looks like a default Pardot form on a polished site, the Layout Template needs CSS overrides — or it's time to consider a Form Handler with a custom-built front end.
GA4 and Iframe Tracking Don't Work Out of the Box
Because Pardot Forms are embedded as iframes, GA4 can't read submission events from the parent page directly. The fix is Google Tag Manager: set up a cross-domain or postMessage event listener that fires when the form submits successfully, then forward it to GA4 as a conversion event.
Forms Are Creating Duplicate Prospects
Pardot deduplicates Prospects by email address, but if the same person submits with a different email (work vs personal), you'll get duplicates. Use Pardot's deduplication tools and consider a stricter email validation rule on the form.
Progressive Profiling Isn't Hiding Known Fields
Progressive Profiling only works when the Prospect cookie is recognized. If users submit from a different browser, an incognito session, or after clearing cookies, they're treated as new visitors and all fields show. This is a Pardot limitation, not a bug.
.png)
.png)
