Conditional logic

Conditional logic limits a snippet to the requests it belongs on. Instead of wrapping code in if statements, you build the rule visually and FluentSnippets evaluates it before deciding whether to run the snippet.

Open a snippet, expand Advanced Conditional Logic, and switch it on.

How groups combine

• Conditions inside one group must all match. They are ANDed.
• Any one group matching is enough. Groups are ORed.

The example above reads: run this snippet when (the post type is product AND the visitor is logged out) OR (the URL contains /checkout).

Use + And to add a condition to a group and the OR divider to start a new group. The bin icon removes a condition; removing the last condition in a group removes the group.

A snippet with conditional logic switched off runs everywhere its run location allows.

Condition sources

User

User Role matches against every role the current user holds, so a user with two roles matches either. A logged-out visitor has no roles, which means “not includes in Administrator” is true for them.

Page

A few details worth knowing:

• Type of page returns one value per request, checked in order: homepage, then singular, then archive, then search, then 404, then author. A single post is is_singular, never is_archive.
• Post Type and Single Post/Page/CPT only match on singular requests. On an archive they are false, even if the archive is of that post type.
• URL matches against the full current URL including query string, and the comparison is lowercased. includes with /pricing matches https://example.com/pricing/ and https://example.com/pricing/enterprise/.
• Taxonomy Page matches the archive for a taxonomy. Taxonomy Term Page matches one specific term’s archive.

Date

All three use the site’s configured timezone, not the visitor’s. Date Range is the one to use for a seasonal banner that should switch itself off; Time Range for something like an “office is open” notice.

FluentCRM

These conditions only appear when FluentCRM is active.

They apply to the contact FluentCRM has identified for the current visitor, which may be someone who is not logged in but arrived from a tracked email link.

Operator reference

The labels in the picker map to these behaviours:

When conditions are evaluated

Conditions need to know what page is being served, which means they cannot be checked at the very start of a request. FluentSnippets handles this per type:

• Functions snippets move from the setup_theme hook to the wp hook as soon as you enable conditional logic, because wp is the first point at which the main query has run. This is the one behaviour change worth remembering: a conditional Functions snippet runs considerably later than an unconditional one. See When your code runs.
• Content, Styles and Scripts snippets are already attached to output hooks that fire well after the query, so nothing changes for them.
• Shortcode snippets are evaluated when the shortcode renders.

Where the rule is stored

The rule is written into the snippet’s own file as a JSON value on the @condition line, so it travels with the snippet when you export it, commit it, or copy the file to another site. See File format and headers.