Pardot Form Handler Builder
List your fields, paste the handler URL, and get the HTML form that posts to Account Engagement (Pardot), with hidden UTM fields, a honeypot and the field mapping to set up. Free, no sign-up.
The builder needs JavaScript.
How a Form Handler Works
A form handler lets your own HTML form, or a third-party form, send its data to Account Engagement. The form posts to the handler’s URL; the handler matches each input by its name to a prospect field and sends the visitor on to the success or error location.
Unlike a Pardot form, the handler doesn’t draw the form, validate it in the page or protect it from bots. That is your form’s job, and what this builder writes.
Settings on the handler
- External field name = the input’s name
- Data format: text, number, email, or email with checks
- Success and error location, data forwarding
- Kiosk/Data Entry Mode for shared devices
- Bot protection: not built in
Set It Up in Five Steps
From an empty handler to the first prospect.
- 1
Create the Handler
Choose a campaign and a tracker domain. Set the success and error locations.
- 2
Build the Form Here
List the fields with the names you want, then copy the HTML into your page.
- 3
Add the Same Fields to the Handler
One per row of the mapping table: external field name, prospect field, data format, required.
- 4
Map the UTM Fields
Create custom prospect fields for them first, or their values are dropped.
- 5
Submit a Test
Use a test address and check the prospect’s activities in Account Engagement.
Form Handler or Pardot Form?
A handler wins when the form must live in your own code.
| Feature | Pardot form | Form handler |
|---|---|---|
| Form design | Pardot layout templates | Your site’s own HTML and CSS |
| Validation in the page | Built in | Yours (required, type=email) |
| Bot protection | Pardot’s spam settings | Yours (honeypot, server checks) |
| Progressive profiling | Yes | No |
| Completion actions | Yes | Yes |
Before the Form Goes Live
Three things a working form handler still needs. Want it set up and tested? We build Pardot forms and handlers for teams like yours.
- Spam. Handlers have no bot protection of their own. Our article shows six ways to keep spam out. Read the article
- Consent. Collect only the fields you need, and record consent where you need it (GDPR).
- Data Formats. “Email not from ISPs and free email providers” rejects free-mail addresses at the handler; test it before you rely on it.
More Free Tools
Form Handler Builder FAQ
Short answers to what people ask about Pardot form handlers.
What is a Pardot form handler?
A URL in Account Engagement that receives the data of your own or a third-party form, maps each field to a prospect field and tracks the submission.
Why does my form handler not create prospects?
Most often an input name that doesn’t match the external field name, especially email. The names in the builder’s HTML and mapping table always match.
Is email required in a form handler?
Every form handler includes an email field when it is created. Send it, named as its external field name says.
How do I pass UTM parameters to a form handler?
Add hidden inputs named utm_source, utm_medium and so on, fill them from the page address with the builder’s script, and map them to custom prospect fields in the handler.
Does a honeypot stop all spam?
No. It stops simple bots that fill every field. Bots that post straight to the handler URL skip your page; for those you need checks on a server.
Is anything I enter stored?
No. The builder runs in your browser.
We Make Salesforce Marketing Work for You
Talk to a certified consultant, not a salesperson, and leave the first call knowing your next step.