Dependent properties in HubSpot let you control which fields appear on a record or form based on what a user has already entered. When a contact selects one option, a related sub-field appears automatically. When they choose a different option, that sub-field stays hidden.
The result is cleaner records and shorter forms. Contacts only see questions that apply to them. Your team only fills in fields that are relevant to the current deal or account.
In your HubSpot portal, go to Settings > Properties. Choose the object type you want to work on. Contacts and Companies are the most common starting points; the same setup applies to Deals and Tickets.
Dependent properties require a parent field with discrete options. Supported types are dropdown select and radio select. Multiple checkboxes work as a controlling field as well.
Scroll to the bottom of the property edit panel and click “Make this a controlling property”. This activates the dependency mapping interface.
Select an option from the controlling field, then choose which dependent property to display when that option is selected. Repeat for each value that should trigger a different field.
Add both the controlling property and the dependent properties to a form or record sidebar. Preview the form and confirm the conditional logic fires correctly before publishing.
What are dependent properties in HubSpot?
A dependent property is a CRM field that only becomes visible when a specific value is selected in another field, known as the controlling property. The controlling field drives the visibility of the dependent field.
For example: if a contact selects “Yes, interested in a training programme” from a dropdown, a follow-up field asking “Which programme are you considering?” appears. If they select “No”, that follow-up stays hidden.
This logic applies to contact and company properties as well as deal and ticket objects. It works in both CRM record views and HubSpot forms, including forms embedded on external websites.
Which property types support this logic?
Not every field type can serve as a controlling property. HubSpot currently supports dependent property configuration when the parent field is a dropdown select or radio select. Multiple checkboxes work as a controlling field as well, though the dependency triggers differently: each checkbox value maps independently to a dependent property.
Numeric fields and date pickers cannot act as controlling properties. File upload fields have the same limitation. If you are designing a conditional setup, start with a dropdown or radio select as the parent to ensure the dependency logic is available.
The dependent property itself can be any type you need. Number fields and date fields both work, as do dropdown selects and free-text inputs.
How do dependent properties work in CRM record views?
When a sales or service rep opens a contact or deal record, they see the controlling property in the record sidebar or detail section. The moment they choose a value, the associated dependent properties appear directly below.
This cuts down on scrolling through long property lists and reduces the number of “not applicable” or blank entries your team has to navigate. The record only surfaces fields that are relevant to the current selection.
For teams managing regional pipelines across Southeast Asia, this is particularly useful. A controlling field for “Country” can surface different qualifying fields depending on which country the contact is based in. Teams covering Singapore or Thailand and the Philippines often have market-specific question sets that differ considerably.
How do dependent properties work on HubSpot forms?
When you add the controlling property and its dependent properties to a HubSpot form, the conditional show/hide logic carries through automatically. A visitor selects a value from the controlling dropdown, and the relevant dependent fields appear below without a page reload.
This is one of the more practical uses of the feature for inbound lead capture. A question like “Are you currently using a CRM?” leads to a follow-up asking which one, but only when the answer is yes. The visitor who answers no sees a shorter, less intimidating form.
Dependent properties on forms are configured at the property level in Settings, not in the form builder itself. Any form that includes both the controlling property and the dependent properties will respect the logic automatically.
Can dependent properties trigger HubSpot workflows?
Yes. Once a value is recorded in a dependent property, that value can trigger workflows the same way any other property value does. The workflow treats it as a standard contact or deal field.
For example: a dependent property “Industry focus” that gets filled in as “Healthcare” can enrol the contact in a healthcare-specific sequence or assign them to a specialist rep automatically. The workflow configuration is no different from any property-based trigger.
This makes dependent properties particularly useful as qualification fields. They capture granular data that is only relevant in specific contexts, then feed that data into downstream automation without manual routing.
What are the most practical uses for dependent properties?
Lead qualification forms. A gating question on a form (“Do you have an existing CRM?”) reveals follow-up fields only when the answer is yes, keeping the form short for unqualified visitors.
Service request routing. A “Type of issue” dropdown on a ticket form can expose specific sub-category fields depending on whether the issue is a billing matter or a technical one. Each sub-category feeds the right data to the right support queue.
Deal qualification. A “Budget confirmed?” field on a deal record reveals a “Budget range” property only when confirmed, keeping early-stage deals uncluttered.
Multi-market segmentation. A “Primary market” field on a company record surfaces region-specific sub-fields for teams operating across multiple countries in Southeast Asia, where the qualifying questions are different per market.
How many dependent properties can one controlling value trigger?
HubSpot allows multiple dependent properties per option. A single dropdown selection can reveal two or three follow-up fields simultaneously. Each option in the controlling property can also map to a different set of dependent properties.
In practice, keep it to two dependent properties per controlling value. More than that tends to make record views feel cluttered, which defeats the purpose of using conditional logic in the first place.
What is the difference between dependent properties and conditional form fields?
In HubSpot, these are related but set up in different places.
Dependent properties are configured at the property level in Settings and apply across the whole portal, including CRM records and any form that uses those properties.
Progressive profiling is a form-specific feature that shows new fields to returning visitors across multiple submissions. It does not hide fields based on current selections; it rotates what fields appear over time.
For conditional display within a single form visit, dependent properties are the correct tool. The logic you set at the property level is what controls show/hide behaviour in the form.
FAQ
Can I use dependent properties on deal or ticket objects?
Yes. The same Settings > Properties path applies for contacts and companies, as well as deals and tickets. The dependency logic works the same way across all object types.
Does the dependency apply in the HubSpot mobile app?
The mobile app respects property visibility settings, though the record view layout differs slightly from the desktop interface.
Will dependent properties appear in list filters?
Yes. The dependent property is a standard CRM field. You can filter contact or deal lists by its value regardless of how it was surfaced on the record.
Can I remove a dependency without deleting the property?
Yes. Open the controlling property in Settings and go to the Dependent Properties section. Remove the mapping there. The property remains in the portal and on any records where it has been filled in. It simply stops being conditional.
Does dependent property logic work in HubSpot’s free tier?
Dependent properties are available on paid HubSpot tiers. The free CRM does not include this feature. Check your subscription level in Settings > Account > Account & Billing to confirm what is available in your portal.
Planning a HubSpot setup or integration in the region?
Contact us