Marketing Cloud Account Engagement (still "Pardot" to most of us) gives you two ways to capture leads from your website: forms and form handlers. They sound interchangeable. They are not — and picking the wrong one is one of the most common structural mistakes I find in Account Engagement audits.
Here's the difference, when to use each, and the traps to avoid.
A Pardot form is built, hosted, and rendered by Account Engagement. You design it in the form builder, drop it on a landing page or embed it on your site via iframe, and Account Engagement controls everything: fields, validation, styling, and what happens after submission.
A form handler is a connector. Your website keeps its own form — built in Webflow, WordPress, HubSpot, whatever your web team likes — and the form handler receives the submitted data by posting it to an Account Engagement endpoint. Your site controls the experience; Account Engagement just catches the data.
Same destination, opposite ownership.
You get the automation toolkit for free. Native forms support progressive profiling (show returning visitors new fields instead of re-asking), dependent fields, built-in bot protection, completion actions, and kiosk mode. None of that requires a developer.
Progressive profiling is the sleeper feature. If your grading model needs industry and company size (and it should — see our scoring vs. grading guide), progressive profiling lets you collect it over multiple visits without ever presenting a wall of twelve fields.
Change without a deploy. Marketing can add a field or change a completion action without filing a ticket with the web team.
The tradeoff: iframes. Embedded Pardot forms live in an iframe, which means styling them to match your site takes CSS effort inside the form template, and responsive behavior needs testing. It's solvable — it's just work people skip, which is why embedded Pardot forms so often look slightly "off."
Your website experience stays yours. If you've invested in a design system and conversion-optimized forms, a form handler keeps all of it — no iframes, no style mismatch, full control over UX and validation.
One form, many systems. Form handlers can pass data to Account Engagement and your other endpoints. If a submission needs to hit your ERP, a Slack webhook, and Account Engagement simultaneously, the handler model fits naturally.
Complex or multi-step forms. Custom quoting flows, calculators, applications — anything beyond "name, email, message" is usually easier built natively on your site and connected via handler.
The tradeoffs are real, though.
You lose progressive profiling and dependent fields. The handler only sees what your form sends.
Validation is on you. Account Engagement won't stop garbage data at the door — your site's form has to do it. (This includes business-email screening if that matters for your routing.)
Silent failures happen. Rename a field on your website form without updating the handler's field mapping, and data quietly stops arriving. Nobody notices until someone asks why lead volume dropped. If you run handlers, field-mapping checks belong in your regular system health reviews.
Use Pardot forms when marketing owns the page, you want automation features without developer time, and standard lead-capture is the job — most landing pages, gated content, newsletter signups. Use form handlers when the form experience is core to your website, you need multi-system submissions, or your web team has strong opinions and the skills to back them up.
Most companies should run a mix. What you shouldn't run is what I usually find: a pile of both, created by different people over five years, with no naming convention, orphaned handlers still receiving traffic, and three forms doing the same job with different completion actions.
Completion actions on everything. Every form and handler should assign a campaign, adjust score, and trigger the right follow-up. A form without completion actions is a bucket with no pipe.
Naming conventions. "2026-Q3_Webinar_Registration_Form" beats "New Form (3)." Your future self is begging you.
Test the sync. Submit a test on every active form and handler quarterly, and confirm the prospect record lands in Salesforce correctly. Form-to-CRM plumbing breaks quietly.
Audit annually. Orphaned forms with old branding and dead handlers are among the most common findings in our Account Engagement work — and among the easiest wins.
Not sure whether your current form setup is helping or hurting? That's a 30-minute conversation. Let's talk.
Founder of Thompson Technology. Salesforce and Account Engagement consultant for B2B companies.
