Pardot Dependent Fields: How to Set Up Conditional Form Fields in Account Engagement
Dependent fields let a Pardot form ask the next question only when the last answer makes it relevant. Here is how they work in Marketing Cloud Account Engagement today: where the setting lives, what it can and cannot do, how it differs from progressive profiling, how the values reach Salesforce, and how to test a form before it goes live.
Key Takeaways
- A Pardot dependent field appears only when another field on the same form has a specific value, such as showing State after a visitor picks USA as their country.
- You set it on the controlling field's Dependent tab in Step 2 of the form wizard, not on the Advanced tab. Each rule pairs one value with one field to show.
- Salesforce documents dependent fields for text and dropdown controlling fields, on Account Engagement-hosted forms only. Form handlers do not support them.
- Progressive profiling is different: it shows a field based on data the prospect gave on earlier forms, not on an answer in the current one.
- Clean data in Salesforce needs matching values: picklist values, State and Country integration values and checkbox mappings must line up before the form goes live.
What are Pardot dependent fields? They are conditional fields on a Marketing Cloud Account Engagement (formerly Pardot) form. A dependent field stays hidden until a visitor enters a set value in another field on the same form, then it appears. Forms stay short for everyone, and each visitor only answers the questions that apply to them, so the data reaching your prospect records and Salesforce is more specific.
We first published this guide in 2023. This version is rebuilt from Salesforce's current Account Engagement Help, release notes and API documentation, checked in October 2026. It corrects where the setting lives, adds the documented limits, compares dependent fields with progressive profiling, and covers Salesforce sync and testing. It is written for marketing operations teams and Salesforce admins at growing and mid-market companies who run Account Engagement forms, and for anyone who still calls the product Pardot. Salesforce renamed Pardot to Marketing Cloud Account Engagement in April 2022, and both names are used below.
How Do Dependent Fields Work on a Pardot Form?
Each rule says: when this field equals this value, show that field. You build the rule on the controlling field, such as Country, and pick the value that triggers it, such as USA, and the field to reveal, such as State. Add more value-and-field pairs for other answers. The revealed field must already be on the form; the rule only controls when it is displayed.
Same-form logic
The trigger is an answer given on this form, in this visit. Nothing depends on what the prospect submitted before.
Value-to-field rules
"When this field equals" one value, "Show this field". Add a pair for each answer that needs a follow-up question.
Hosted forms only
The logic runs on forms built and hosted in Account Engagement, whether on a landing page or embedded on your site in an iframe.
When Should You Use Dependent Fields on Account Engagement Forms?
Use them when a follow-up question only makes sense for some answers. If every visitor should answer a question, it is a normal field. If only visitors who choose a certain country, product, event format or "Other" need it, make it dependent. The form stays short for most people, and the visitors who see the extra field are the ones whose answer you actually need.
| Form | Controlling field and value | Dependent field revealed | Why it helps |
|---|---|---|---|
| Contact or demo request | Country = USA | State (dropdown) | Territory routing and assignment need a clean state value. This is Salesforce's own example. |
| Product inquiry | Interested in = a specific product line | A question that only applies to that product, such as current system or volume | Sales gets qualifying detail without making every visitor answer every product's questions |
| Request for quote | Request type = Quote | Quantity, timeline or specification fields | Quote requests arrive with the details needed to respond, and can be scored apart from general inquiries |
| Event registration | Attendance = In person | Dietary or accessibility requirements | Virtual attendees are not asked logistics questions that do not apply to them |
| Any form with "Other" | How did you hear about us = Other | Please specify (text) | Keeps the dropdown reportable while still capturing the rare answer |
Each example uses a dropdown as the controlling field. That is deliberate: a dropdown gives the visitor a fixed list, so the value they choose matches the value in your rule exactly. Rows two to five are illustrations of the pattern; your own fields and values will differ.
How Do You Set Up Pardot Dependent Fields, Step by Step?
Add every field to the form first, then open the controlling field's Dependent tab and create one rule per trigger value. The setting is in Step 2 of the form wizard. It is available in all Account Engagement editions, and you need the Account Engagement Administrator or Marketing role to edit fields on a form.
Salesforce documents these steps in Set Up Dependent Form Fields, and every tab of the field editor in Form Field Options. Teams that build forms through the API can do the same with the v5 Form Field object's addDependent operation, which stores the trigger value and the form field to display. One correction to the earlier version of this post: the rule is not on the Advanced tab. It has its own Dependent tab.
What Are the Limits of Pardot Dependent Fields?
They are simple rules with a few firm boundaries. Salesforce documents them for text and dropdown controlling fields, on hosted forms only, with one value revealing one field per rule. Anything beyond that, such as chained dependencies or required dependent fields, is not described in Salesforce's documentation, so treat it as something to prove in testing rather than to assume.
If a form needs complex branching, it is often a sign the form is trying to do two jobs. Splitting it into two shorter forms, or capturing the extra detail later with progressive profiling, usually gives cleaner data than a deep chain of conditions.
Dependent Fields vs Progressive Profiling: What Is the Difference?
Dependent fields react to an answer on the current form; progressive profiling reacts to what the prospect told you on earlier forms. Use dependent fields to branch within one submission. Use progressive profiling to keep each form short and gather more over several visits. Both are set per field in Step 2 of the form wizard, on separate tabs, and both work on hosted forms only.
| Setting | Where | What triggers it | Use it for |
|---|---|---|---|
| Dependent fields | Dependent tab of the controlling field | A value entered in another field on the same form | Follow-up questions that only apply to some answers |
| Progressive profiling | Progressive tab of the field to show | The prospect already has data in the fields you list | Asking job title or budget on a second download, after name and email are known |
| Always display even if previously completed | Advanced tab | Turns off the default of hiding fields the prospect has completed | Fields that must be confirmed each time, such as email or consent |
| Hidden field type | Basic tab, Type | Never shown; captures a value without the visitor seeing it | Campaign, source or UTM values passed to the prospect record |
Salesforce's example of progressive profiling: Form A asks for name and email, and Form B shows Job Title only when the prospect already has a name and email. A prospect who views Form B before submitting Form A does not see Job Title. Setup is in Gather Prospect Data Over Time: on the field's Progressive tab, select "Show this field only if the prospect already has data in the following field(s)" and add those fields. Our guide to progressive profiling in Salesforce Marketing Cloud covers the technique in more depth, including Marketing Cloud Next.
Which Other Pardot Form Field Settings Improve Data Capture?
Field values, prefill, email validation and global field defaults matter as much as the conditional logic. A dependent field only produces clean data if the values behind it are controlled, the right fields prefill, and every form uses the same definitions. These settings sit on the Basic, Advanced and Values tabs of the same field editor.
Values tab
For checkbox, radio button and dropdown fields: show a friendlier label while storing the original value, assign a profile, or add everyone who picks a value to a list.
Email data format
Set the email field to accept only addresses with a valid mail server, or to reject ISP and free email providers on B2B forms.
Load Default Data
Changing a prospect field's global settings does not update forms already using it. Edit the field on each form and click Load Default Data.
Do not prefill
Most fields prefill by default from data collected earlier on the same device. Turn it off for fields that should always be entered fresh.
Maintain the initial value
Keeps the first value a prospect submitted instead of overwriting it on later submissions. It does not apply to the email field.
Predefined values
Give dropdown prospect fields a predefined value list so every form, import and automation rule uses the same values.
The Spring '26 prefill change
Salesforce's Spring '26 release notes added a privacy check to Account Engagement-hosted forms: eligible fields now prefill only when the visitor uses the same device on which that information was last collected. Before, prefill could appear across devices. Expect returning visitors on a new laptop or phone to see more empty fields, and do not design forms that assume a known visitor's answers will already be there.
How Do Dependent Field Values Sync to Salesforce?
Like any other prospect field: through the field mapping to the lead or contact, so the values must be acceptable to Salesforce. A dependent field that collects a value Salesforce rejects causes a sync error rather than clean data. Check value lists, picklist restrictions and field types before launch, especially for State and Country.
| Situation | What Salesforce documents | What to do |
|---|---|---|
| Restricted picklist in Salesforce | Values pushed from Account Engagement must be identical to the Salesforce values, or the sync fails | Copy the picklist values exactly into the prospect field's predefined values |
| Keeping value lists aligned | On a mapped field, "Use pre-defined values" lets field setting changes sync from Salesforce | Turn it on for dropdown fields mapped to Salesforce picklists, then Load Default Data on each form |
| State and Country picklists | Values sent to Salesforce must match the picklist's Integration Value, and the keep-values-in-sync option is not supported with this feature | Build Country as a dropdown with State dependent on it, using the integration values; Salesforce's own article uses the Dependent tab for this |
| Checkbox to a Salesforce checkbox | Account Engagement checkboxes are multi-select; Salesforce checkboxes are true or false | Use a radio button prospect field with values true and false, shown on the form as a checkbox with the true value only |
| Salesforce dependent picklists | No Salesforce documentation says controlling and dependent picklist rules carry into Account Engagement forms | Rebuild the logic yourself on the Dependent tab and keep the value lists in step with Salesforce |
Sources: Salesforce's articles on fields that do not sync, State and Country picklists with Account Engagement, mapping checkbox fields and mapping custom fields. Two more mapping details from that last page: the connector user must be able to see the Salesforce field, and a lead field and a contact field only map to the same prospect field if their API names are identical.
How Do You Test a Pardot Form With Dependent Fields?
Submit the form once for every trigger value, each time as a brand-new visitor, then check the prospect record and the Salesforce lead. Account Engagement remembers visitors by cookie, so a second test from the same browser is credited to the first test prospect, and a returning visitor sees the thank-you content instead of the form for 10 minutes.
?PI_ALWAYS_DISPLAY=1 to the form URL, to see the form again with progressive fields applied.Salesforce's Testing Forms article explains these behaviours. One more check from community experience: if a cloned form shows every field at once, open the controlling field on the copy and confirm its Dependent tab rules are still there before publishing.
Do Dependent Fields Work With Form Handlers or Marketing Cloud Next Forms?
Not with form handlers, and Marketing Cloud Next forms use a different set of rules. A form handler only receives data posted from a form you build elsewhere, so the conditional display has to live in that form. Marketing Cloud Next has its own form builder, whose documented rules cover progressive profiling and prefill rather than Account Engagement's value-based dependent fields.
Choose a hosted form when you want dependent fields, progressive profiling, Account Engagement's bot protection, thank-you content and form view reporting. Salesforce's forms versus form handlers comparison lists these as hosted-form features.
Choose a form handler when the form must come from your website or a third-party tool. Build the conditional logic in that tool, and map every field it posts. Salesforce's form handler considerations also recommend bot protection and a required email field.
Our guide to Account Engagement form handlers covers setup and field mapping for the second path. If you are moving to Marketing Cloud Next, Salesforce's progressive profiling rules for forms live on each field's Rules tab and need a read data provider, and rules cannot be added to hidden fields. Plan to redesign conditional forms for that builder rather than expecting the Dependent tab rules to carry over.
How Do You Design Pardot Forms That Capture Better Data?
Start from the decisions the data must support, such as routing, scoring and reporting, and ask only for what those decisions need. Then choose the mechanism for each question: a normal field if everyone must answer, a dependent field if only some answers need follow-up, progressive profiling if it can wait, and a hidden field if the visitor should not have to type it.
- 1
List the decisions. Which fields drive assignment, scoring, segmentation and Salesforce reports? Anything that drives none of them is a candidate to drop.
- 2
Standardize the values. Define dropdown values once on the prospect field, matched to Salesforce picklists and integration values, and load them on every form.
- 3
Branch only where it pays. Use dependent fields for one level of follow-up questions, not for every possible answer.
- 4
Capture source silently. Use hidden fields for campaign and UTM values so attribution does not depend on the visitor.
- 5
Test, then audit. Test every branch before launch, and review sync errors and empty fields after the first few weeks of submissions.
This is the same discipline we apply in client work. In a published Salesforce Financial Services Cloud and Pardot audit, we validated form tracking for a financial services client; the case study reports that 100% of form submissions now pass UTM values correctly to Salesforce. For a U.S. manufacturer, our Pardot for manufacturers case study describes separating request-for-quote submissions from routine contact form inquiries with dedicated RFQ scoring, alongside landing page and form optimization. And when an organization had to move Pardot to a new Salesforce org, our Pardot migration case study reports that 100% of existing marketing assets and automations were migrated rather than rebuilt.
The Bottom Line
Pardot dependent fields are one of the simplest ways to make Account Engagement forms shorter and their data more useful, as long as the values behind them are controlled and every branch is tested. Twopir Consulting implements, audits and optimizes Marketing Cloud Account Engagement for growing and mid-market companies, from form and field design to Salesforce sync, scoring and nurture.
- 1
Set dependent fields on the controlling field's Dependent tab, one value and one field per rule.
- 2
Use dropdowns as controlling fields, with values matched to Salesforce.
- 3
Use hosted forms for conditional logic; form handlers do not support it.
- 4
Combine dependent fields with progressive profiling and hidden fields rather than one long form.
- 5
Test every branch as a new visitor and check the Salesforce record before launch.
Get Account Engagement Forms That Sales Can Trust
Tell us which forms feed your pipeline and where the data breaks down. We will review your fields, dependencies and Salesforce sync, and show you what to fix first.
Schedule a Discovery CallFrequently Asked Questions
Edit the form and go to Step 2 (Fields). Click the pencil icon next to the field that should control the others, open the Dependent tab, and select Display other fields in this form based on the value of this field. Then pair each trigger value with the field to show. It is not on the Advanced tab.
Salesforce Help says a dependent field can be based on any text or dropdown field, and does not list radio buttons or checkboxes. The documented approach is to make the controlling question a dropdown with the same values. A dropdown also guarantees the selected value matches the trigger value in your rule.
No. Salesforce states that conditional fields are not available on form handlers because they do not work on external content. If your form is built on your website or in a third-party tool, build the conditional logic in that form and use the form handler only to receive and map the submitted fields.
Dependent fields show a field when a visitor enters a set value in another field on the same form. Progressive profiling shows a field only when the prospect already has data in fields you choose, usually from earlier forms. Dependent fields branch within one visit; progressive profiling builds a profile over several visits.
Make Country a dropdown, add State to the form, then on Country's Dependent tab set When this field equals USA and Show this field State. Add more pairs for other countries. If you use Salesforce State and Country picklists, the values must match Salesforce's integration values or the sync fails.
Check that the field to reveal is on the form, that the trigger value matches the controlling field's value exactly, and that the controlling field is a text or dropdown field. On a copied form, confirm the Dependent tab rules were kept. Test in a private window, since cookies can show thank-you content instead of the form.
Yes. Salesforce announced in April 2022 that Pardot would be called Marketing Cloud Account Engagement. The product, logins and URLs did not change at the time, and parts of the interface and Help still say Pardot. Forms, form handlers and dependent fields work the same under either name.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Marketing Cloud Account Engagement and its Salesforce sync, for 500+ clients over 12+ years.