Documentation User Guide

Advanced Conditional Logic in PRO

This page explains the advanced condition types available in Elzo Forms PRO.

Use this page when standard field conditions are not enough and you need form behavior or automations to respond to user context, URL values, cookies, or date and time rules.

Standard conditions vs PRO condition types

Standard field conditional logic usually checks values inside the form.

For example:

  • show a field when another field equals a specific value;
  • hide a field when another field is empty;
  • control a field based on a visitor’s selection.

Elzo Forms PRO adds condition types that can use context outside the field value itself.

PRO condition types can help you build workflows that respond to:

  • the current user;
  • the current URL or URL parameters;
  • browser cookies;
  • date and time rules.

This makes PRO useful for more advanced form behavior and automation workflows.

User conditions

Use User conditions when a rule should depend on the visitor’s WordPress user context.

Depending on your installed version and configuration, User conditions may help check values such as:

  • whether the visitor is logged in;
  • the user ID;
  • the user role.

Example uses:

  • run an automation only for logged-in users;
  • show different form behavior for a specific role;
  • skip a workflow for anonymous visitors.

User conditions are useful for membership sites, client portals, internal forms, and websites where logged-in users have different roles.

URL conditions

Use URL conditions when a rule should depend on the page URL or a URL parameter.

Example uses:

  • change form behavior when a specific URL parameter is present;
  • run a workflow only on a specific landing page;
  • route submissions differently based on campaign parameters;
  • preselect behavior based on page context.

For example, a URL may include a parameter such as:

?source=partner

A PRO condition can use that context when deciding whether a workflow should run.

Use URL conditions carefully. URL values can be changed by visitors, so they should not be used as the only protection for sensitive logic.

Use Cookie conditions when a rule should depend on a browser cookie.

Example uses:

  • adjust behavior for returning visitors;
  • run a workflow only when a specific cookie exists;
  • avoid repeating the same experience after a visitor completes a form;
  • connect form behavior to previous site interactions.

Cookies can be useful for visitor experience, but they should not be treated as secure identity data. Visitors can clear or block cookies.

Date and Time conditions

Use Date and Time conditions when a rule should depend on a date, time, or time period.

Example uses:

  • run a workflow only during a specific date range;
  • change behavior after a deadline;
  • show or hide form behavior based on time;
  • route submissions differently during a campaign period.

Date and Time conditions are useful when form behavior should change without manually editing the form every time.

Check the site timezone when using time-based rules. A rule may behave differently if the site timezone is not what you expect.

Using PRO condition types with automations

PRO condition types are especially useful in automations.

For example, an automation can run only when:

  • a field value matches;
  • the visitor has a specific user role;
  • a URL parameter is present;
  • a cookie exists;
  • the submission happens inside a date range.

This allows one form to support more than one workflow.

Using PRO condition types with form behavior

Depending on your form setup, PRO condition types may also help control form behavior beyond basic field values.

For example, you may use context such as URL, user, cookie, or date/time to decide how a form behaves for different visitors or situations.

Use this carefully and test each scenario separately.

Testing advanced conditions

Always test advanced conditions before using them on a live form.

To test:

  1. Create one condition at a time.
  2. Use a value that should match.
  3. Use a value that should not match.
  4. Test as a logged-in and logged-out visitor if using User conditions.
  5. Test with and without the expected URL parameter if using URL conditions.
  6. Test with and without the expected cookie if using Cookie conditions.
  7. Check the site timezone if using Date and Time conditions.
  8. Submit a test entry.
  9. Review the result and automation logs if available.

Advanced rules are easier to troubleshoot when each condition is tested separately.

Security notes

Do not rely on URL parameters or cookies as secure proof of identity.

Use User conditions for WordPress user context. Use server-side permissions, roles, and other security controls when a workflow affects sensitive data.

Only collect and process the data you actually need.

Troubleshooting

A User condition does not match

Check whether you are testing as the correct WordPress user. Also confirm the user role, login state, or user ID used by the condition.

A URL condition does not match

Check the exact URL parameter name and value. Parameter names and values must match what the condition expects.

Confirm that the cookie exists in the browser. Test in the same browser session, and remember that visitors can clear or block cookies.

A Date and Time condition does not match

Check the site timezone and the configured date/time range.

An automation does not run

Test the automation without advanced conditions first. Then add one condition at a time and review the automation logs if available.

  • Conditional Logic for Fields
  • Automations Overview
  • Create Your First Automation
  • Troubleshooting Automations

Applies to

  • Elzo Forms PRO
  • WordPress admin
  • Frontend form display
  • Automations
  • Conditional logic

Last reviewed

2026-07-04

 
Contact us