Description
Who This Is Built For
GF Advanced Conditional Shortcodes lets you stack several conditions inside a single [gravityforms] shortcode, so one tag can decide what a visitor sees based on more than one answer. If you build forms with Gravity Forms and have ever wished the built-in conditional shortcode could check two or three fields at once, this plugin was made for that exact gap.
Consider a store that sells accessories for cars and trucks. The owner builds an order inquiry form that asks about vehicle type, intended use, and budget range. After submission, the Confirmation message should recommend specific products. A truck owner who hauls gear needs bed liners and tonneau covers. A car owner who commutes needs floor mats and phone mounts. With the native shortcode, that means a pile of separate conditional blocks, each checking one field. With this plugin, a single shortcode can check vehicle type and use together.
Other people who benefit include agencies that configure Notifications for clients, membership sites that route applicants to different next steps, and event organizers who show different instructions to different ticket types. Anyone who writes Confirmations or Notification emails by hand and wants tighter control over the output will find it useful. It also suits developers who like keeping logic inside the content itself rather than writing custom code for every form.
What GF Advanced Conditional Shortcodes Does
The Gravity Forms conditional shortcode wraps content and shows it only when a field in the submission matches a test. The limitation is that it accepts one test. This plugin extends the [gravityforms] shortcode with extra parameters so you can list multiple conditions and tell the shortcode how to evaluate them together.
The central setting is the relation parameter, which is required. It accepts two values: all and any. Choose “all” and every condition must be true before the content appears. Choose “any” and a single matching condition is enough. That one switch covers a surprising range of situations. “All” is for narrow targeting, such as showing a message only to people who picked a particular product category and also selected express shipping. “Any” is for broad groupings, such as showing a discount note to anyone who ticked one of several qualifying options.
Each condition also uses a compare value, which is the text or number the submitted field is tested against, and an operator that defines how the test works. Operators include familiar choices such as greater_than and starts_with, which means you are not limited to exact matches. You can check whether a number exceeds a threshold, or whether a text entry begins with a certain prefix, such as a part number or a region code.
Because the output is still a shortcode, it works wherever shortcodes are processed. That includes Confirmations and Notifications, which are the two places most Gravity Forms users care about, and also other areas of a WordPress site that run shortcodes. You write the logic once, in the same place as the content it controls.
Key Capabilities
- Multiple conditions in one shortcode. Replace chains of separate conditional shortcodes with a single tag that is easier to read and easier to fix.
- “All” or “any” relation. Require every condition to pass, or let any one of them trigger the content.
- Comparison operators beyond equality. Use options like greater_than and starts_with to evaluate numeric and text-based field values.
- Works in Confirmations and Notifications. Tailor on-screen messages and emails using the same syntax.
- Usable anywhere shortcodes run. The logic is not locked to the form settings screen.
- Builds on the existing [gravityforms] shortcode. It adds parameters instead of introducing a new syntax, so anyone familiar with the original will recognize the structure.
- GPL licensed. The code is open for you to study, modify, and extend.
Cleaner than stacking shortcodes
Nesting or repeating single-condition shortcodes works until something breaks. A missing closing tag or a mismatched value can silently hide a block of content, and finding the culprit in a long Confirmation means reading every layer. Putting the conditions into one shortcode keeps the logic in one visible line. When a message does not display as expected, you have one place to look.
Flexible matching for real data
Forms collect messy information. People type postal codes, order numbers, quantities, and budgets. Operators like starts_with let you respond to the shape of an entry, while greater_than handles numeric thresholds. Combined with the “any” relation, you can group several acceptable answers without writing a separate block for each.
Getting Results
Using the plugin follows a short sequence: install it, write your shortcode, and test with a sample submission. Once active, you open the Confirmation or Notification you want to change and add the shortcode around the content that should be conditional. Set the relation to “all” or “any,” then define each condition with its field, operator, and compare value.
Returning to the car and truck accessories store, a Confirmation might contain several product suggestion blocks. One block requires that the vehicle field equals truck and the use field equals towing. Another uses “any” to show a general care kit if the customer selected one of several maintenance options. The buyer sees only the blocks that apply to them, and the page reads like it was written for that person.
The same approach improves email. A Notification sent to your team can include extra handling instructions only when a high order quantity and a rush option are both selected. A message sent to the customer can include a warranty note only for certain product lines. Staff spend less time scanning irrelevant text, and customers get messages that match what they asked for.
Adapting it to your workflow
Since the plugin is released under the GPL, developers can adjust its behavior, add custom operators, or fold it into a larger set of tools that a client site relies on. Agencies can keep a standard version across projects and modify it where a particular build demands something different. You are free to inspect how parameters are parsed, which makes troubleshooting less of a guessing game.
Taking it further
After the basics feel comfortable, try layering your approach. Use one shortcode with “all” for a precise audience segment and a second with “any” for a catch-all fallback. Test each path by submitting the form with different answers, and review the rendered Confirmation and the delivered email. Small test submissions catch typos in compare values before real customers do.
Frequently Asked Questions
What is the difference between the “all” and “any” relation?
With “all,” every listed condition must be met before the wrapped content is displayed. With “any,” the content appears as soon as one condition is true. Use “all” to narrow your audience and “any” to cover several acceptable answers in one shortcode. The relation parameter is required, so every multi-condition shortcode needs one.
Can I use it in both on-screen Confirmations and email Notifications?
Yes. The plugin extends the [gravityforms] shortcode, and that shortcode is processed in Confirmations and Notifications, as well as in other places on a WordPress site where shortcodes are supported. The syntax stays the same, so you can reuse logic between a Confirmation message and the matching email.
Does it only match exact values?
No. Each condition has an operator, and the options go beyond simple equality. You can use greater_than for numeric comparisons and starts_with for text that begins with a particular string. The compare value you supply is tested against the submitted field using whichever operator you choose, which gives you room to handle quantities, codes, and similar entries.

