Pardot and Account Engagement · form handlers
The form worked.
The lead went nowhere.
Form handler failures do not raise errors, because from Pardot's side nothing failed: the submission arrived and a prospect was created. Everything that was supposed to happen next simply did not. Below are the five ways that happens, and the thirty minute audit that finds all five in your own org.
Reviewed 27 August 2026.
Pattern 01
Endpoints nobody remembers creating
Form handlers accumulate. An event landing page, a campaign that ran for one quarter, a partner microsite, a page somebody built in a hurry. Each created an endpoint, and each endpoint still accepts submissions long after the page it served was forgotten.
How to find it
Export the form handler list from Pardot settings, then crawl your own site for the endpoint URL pattern and compare the two. The endpoints that appear in Pardot and nowhere on the site are the dead ones. The endpoints that appear on the site and not in your list are the ones somebody built without telling marketing.
Pattern 02
Completion actions that point at things that no longer exist
Completion actions are configured once and rarely reopened. Meanwhile the assets they reference get renamed, paused or deleted: an engagement programme, a list, a Salesforce campaign, an automation rule. The submission still succeeds, the prospect is still created, and nothing downstream happens.
How to find it
Open the top ten form handlers by volume and read every completion action against what currently exists in the org. Five minutes each. This is the single highest return check on the list, because the failure is invisible from every dashboard: the form worked, the lead arrived, and nobody was told.
Pattern 03
Field mappings broken by a rename on either side
A form handler maps the name of an HTML input to a Pardot field. Rename the input from company_name to company on the website, or rename the field in Pardot, and the mapping stops matching. Pardot does not reject the submission. It accepts it and leaves the field empty.
How to find it
Submit a test through each of your top handlers with a recognisable value in every field, then open the prospect that was created and check which fields are populated. The empty ones are your broken mappings. Do this after any website redesign, because a redesign renames inputs as a matter of course.
Pattern 04
A spam honeypot that is catching people
The honeypot is a field hidden with CSS. Bots fill everything they can see in the markup, humans do not fill what they cannot see, and submissions with the field populated are discarded. It works until something makes the field visible or fills it automatically: a stylesheet change, a page builder update, or a browser password manager.
How to find it
Fill your own form in a normal browser with autofill enabled and confirm the prospect appears in Pardot. Then check the honeypot field is genuinely invisible on the rendered page rather than merely intended to be. This one is worth checking specifically after any front end deployment.
Pattern 05
A website platform update that changed how the form posts
The form lives in a page builder or a content management system that you do not control the release schedule of. The vendor updates how forms generate HTML, or how their script submits, and the post to Pardot changes shape. Nothing in Pardot changed, and nothing in Pardot will tell you.
How to find it
The signature is a clean break: submissions for one form stop on a specific date and every other form is unaffected. Compare submission counts per handler month over month and look for a step rather than a slope. Then check what was deployed to the site that week.
The method
Thirty minutes, and you do not need me for any of it.
This is the sequence I run at the start of every engagement that touches lead capture. It is written out in full rather than summarised, because the point of publishing it is that you can run it yourself and decide afterwards whether you need help.
Export the inventory
In Pardot, open the form handler list and export it. You want the name, the endpoint URL, the created date and the submission count. Five minutes, and it is the only step that needs Pardot access.
Crawl your own site for the endpoints
Search your site source for the endpoint pattern. Every page that posts to Pardot will contain it. Ten minutes, and it produces the second half of the comparison.
Cross reference the two lists
In Pardot but not on the site means a dead endpoint that still accepts data. On the site but not in your list means somebody built a capture path nobody told marketing about. Both are findings.
Read the completion actions on the survivors
For the handlers that are genuinely live, open each one and check every completion action still points at something that exists. This is where most of the damage is, and five minutes per form is enough.
Submit one test through each
A recognisable value in every field, then open the prospect and see which fields arrived. Empty fields are broken mappings.
The choice underneath all five
Handlers buy you design control and sell you a maintenance surface.
A native Pardot form is rendered by Pardot, so there is no mapping to break, no endpoint to lose track of and no page builder to update underneath you. What you give up is control of the markup.
A handler keeps your markup and moves the fragility to the seam between two systems maintained by two different people. Every one of the five patterns above lives in that seam. Neither choice is wrong, but only one of them needs a quarterly review, and it is worth deciding that deliberately rather than inheriting it.
Why this will not fix itself
Account Engagement is in maintenance, so the platform will not close this gap.
There is no announced end of sale and no forced migration, and the product still receives support and security updates. What it does not receive is investment in new capability, which means the gaps described above are not on anybody's roadmap. The current status is written up here.
Practically, that makes the quarterly review a decision rather than a chore. Nobody is going to build the alert that would have told you.
Asked often enough to answer here
Questions
What is a Pardot form handler, and how is it different from a Pardot form?
A form handler is an endpoint that accepts data from a form built somewhere else, on your own site, in a page builder, or in another tool. A Pardot form is hosted inside Pardot and rendered from there. The handler exists so you can keep your own markup and styling and still capture into Pardot. That flexibility is exactly what makes it fragile: the form and the endpoint are maintained by two different people who rarely talk.
Why do form handler failures never raise an error?
Because from Pardot's point of view nothing failed. The submission arrived and a prospect was created. A completion action pointing at a deleted list, or a field mapping that no longer matches, is not an error condition. It is an instruction with nothing on the other end. That is why these are found by audit rather than by alert.
How long does the self audit take?
About thirty minutes for the inventory and cross reference, plus five minutes per form for the completion action review. For most orgs that is one afternoon, and it is written out above in full precisely so you can run it without hiring anybody.
Should we move to native Pardot forms instead?
It depends on which problem you would rather have. Handlers give you your own markup and cost you a maintenance surface that breaks quietly. Native forms give up design control and remove that surface entirely. If your forms are simple and your brand can live with what Pardot renders, native forms are less to maintain. If the design matters, keep handlers and put the audit above in your quarterly calendar.
What does it cost if we want help?
The paid check is 500 euro, runs against your own exports, and is delivered within three working days with a costed order of work. Remediation is quoted in hours at fifty euro from what the check finds, and every price is published. The self audit above costs nothing and will find most of it.
The paid check is €500 against your own exports, delivered within three working days and credited against the work. Remediation is quoted in hours at fifty euro, and every price is published here. That number sits below what a partner would quote deliberately rather than as a discount: no delivery manager, no partner margin.
Serhii Skrypnyk · Senior Salesforce Administrator and developer · 7 Salesforce certifications · on the platform since 2018. Reviewed 27 August 2026.