I Reviewed 100 Conditional Logic Support Tickets. Here’s What We See Most in Gravity Forms.
I went through our support tickets to see what keeps coming up with Gravity Forms conditional logic, and what to do if you run into the same issues.
- What looks like a conditional logic limitation usually isn’t
- When you need AND/OR together
- When conditional logic could use more operators
- When a chain of conditional logic breaks across pages
- When there’s too much conditional logic in one form
- The logical conclusion
Somewhere in our support inbox is a ticket about a form with over 1,300 conditional fields — and guess what, it was painfully slow. 🥲
Conditional logic in Gravity Forms lets you show or hide fields based on someone’s answers. Sounds easy enough, until you’re juggling a lot of rules at once. So I went through 100 of our support tickets tagged “conditional logic” and grouped them by the issues people were running into.
Turns out, Gravity Forms conditional logic could already handle some of them, while others were cases where it could use a little help.
I’ll walk through what came up most, and what you can do if you run into the same thing. 🪄
What looks like a conditional logic limitation usually isn’t
Two issues I found with Gravity Forms conditional logic weren’t really limitations at all.
- One common issue was assuming you needed a paid plugin just to show a field only to logged-in users. But you can handle logged-in status natively — I’d just drop a user merge tag like
{user:ID}into a hidden field’s default value, then build the conditional logic off that field instead.
- The other was having a required field hidden by conditional logic. You might expect the form to flag it as missing, but it won’t. By default, a field hidden by conditional logic just doesn’t get checked on submission.
A wizard’s advice? If something in conditional logic feels limited, it’s worth checking the fine print first. Sometimes the feature you need is already there — and just needs a little more playing around with. 😉
When you need AND/OR together
What it looks like: You want to show a field if conditions A and B are both true, or if C is. Native conditional logic only gives you one flat set of rules — either All or Any — so you can’t combine both in the same group. I saw this come up in 18% of the tickets I reviewed.
Where to start: For this, I’d reach for Advanced Conditional Logic. We built it for situations where conditional logic could use a little more room to work. In this case, it lets you group rules, so you can combine AND and OR in the same setup.
When conditional logic could use more operators
What it looks like: You want to show a field only if another field doesn’t contain a certain word. Native conditional logic can check if a field contains text, but not if it doesn’t.
I saw the same kind of issue a few more times, just with a different operator missing each time.
Where to start: For this, I’d reach for Advanced Conditional Logic. It adds several operators on top of the native ones, including does not contain, which lets you show or hide a field based on what’s missing, not just what’s there.
When a chain of conditional logic breaks across pages
What it looks like: In one case, a field on one page controlled a field on another, which controlled a third. The chain froze the multi-page form entirely because Gravity Forms doesn’t officially support nested conditional logic.
I saw multi-page issues like this in 14% of the tickets I reviewed, including Next buttons disappearing or rules breaking because they depended on an earlier page.
Where to start: The best workaround here is still what the mothership (aka Gravity Forms) recommends: add both conditions to the last field. That way, it isn’t relying on the field before it to pass anything along.
When there’s too much conditional logic in one form
What it looks like: One support ticket had a form with over 1,300 conditional fields, and with that much conditional logic running at once, things can start to slow down.
That’s because conditional logic runs in the browser, which can end up evaluating a lot of rules as someone interacts with the form.
Where to start: Cut down on fields, or split your form into a few smaller ones.
Worth knowing: if splitting your form means someone has to re-enter info they’ve already filled out, I’d recommend checking out Easy Passthrough — it passes that data straight into the next form.
The logical conclusion
Some issues just needed a little more digging into what Gravity Forms’ built-in conditional logic could already do.
And for the ones that genuinely needed more flexibility, Advanced Conditional Logic gives you a little more room to work. It might not cover every conditional rule out there (at least not yet…), but it sure helps with a good chunk of the issues that came up. ✨
Still, my best advice? See how far the built-in conditional logic can take you before assuming you really need something more.
Not sure if it’s a real limitation or just something you missed? Let’s figure it out! Just ask for a free blueprint, and our friendly Support Wizards will map it out with you. 🧙