Conditional Property Logic with Combination Operators
Monday, August 31, 2026
What it is
Combine multiple conditions when setting up conditional logic on properties, triggering dependent properties to appear based on the values of multiple properties.
Why it matters
Until now conditional property logic could only look at one property at a time. With multi-condition logic, records surface the right fields only when multiple criteria are met - show a renewal date only when a contact is a customer AND has an active subscription, apply a lead score only when a form was filled AND the contact is in a target industry, require a reason for churn when a deal is Closed Lost AND high priority.
The Take
It's always like, why did we win? Oh, features. Oh, cool. Price. Also why we lost.
The room agreed this is a long-standing ask, and both use cases that came back were the same one: pipeline conditionals. Show or require a set of properties when the deal is in this stage and the product is this - and cascade the prompt as a rep advances to the next stage. That is where conditionals actually get used, and it is where the one-property-at-a-time limit hurt most. Capturing that nuance is the point.
One quibble with HubSpot's own example, raised on air: requiring a reason-for-churn field only on high-priority closed-lost deals. You would want that on all of them. Though as the counter went, we can't focus on what happens when we win, folks, only when we lose.
And the deeper data problem this does not touch - the one-reason problem, where every closed-lost comes back "price" or "features," and the very same reason shows up on the wins.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
Produced by Value-First Media