How To Use Conditional Rendering in Avada

Last Update: November 26, 2025

Avada Conditional rendering allows you to determine which Avada Elements are rendered on a web page. In this help file, we will look at how it works and some ways to use it. Read on to find out more about this exciting feature, and watch the video below for a visual overview.

For privacy reasons YouTube needs your permission to be loaded.

What is Avada Conditional Rendering?

Conditional Rendering (not to be confused with Element Visibility) is a powerful feature that lets you show or hide any Avada Design Element and Layout Element based on specific conditions you define. Instead of displaying duplicate content to every visitor, you can tailor what appears on the page based on factors such as user login status, device type, date and time, page or post ID, WooCommerce conditions, custom fields, and more.

This feature gives you complete control over who sees what and when, enabling personalized experiences, targeted messaging, and flexible design variations—all without writing any code. Whether you want to display a promo only to mobile users, hide content from logged-out visitors, or change layouts based on product categories, Conditional Rendering makes it seamless inside the Avada Builder.

A few straightforward examples of this would be an Avada Column that displays only when a user is logged in, a Header container that renders only on small screens (such as a mobile phone), or a Container on a store’s Cart page that does not render when the Cart is empty. Multiple conditions can also be applied for complex situations. There is a significant difference in the amount of code loaded onto the page between not rendering an Avada Element and simply hiding it using the Avada Element Visibility option.

Conditional Rendering – Allows you to hide/display any Avada Element based on specific conditions. Because this method does not render the HTML unless it is set to visible, it is considered a performance-enhancing method.

Element Visibility – Allows you to hide/display an Avada Element based on the screen size at which it is viewed (Small/Medium/Large). Because this method renders the HTML for each state regardless of whether it is hidden or visible, it is considered less performant than Conditional Rendering.

Where Is It Found?

Conditional Rendering is located in the ‘Extras’ tab of each Design and Layout Element. Because these Elements contain all the page’s content, they support almost all imaginable use cases.

How To Use Avada Conditional Rendering

There will be an enormous variety of situations in which this feature could be used. The best we can offer here is a breakdown of the possible values and a few scenarios to give you the idea.

As you can see in the screenshot below, when you click on the + Add New Logic Button, you are presented with a Condition Type option, a Relational Operator selector (Equal To, Not Equal To, and in some instances, also Greater Than, Less Than, and Contains), and a Condition Value field. Below this is an AND/OR option, which you can use to combine further Logic Terms–AND allows you to combine conditional statements, while OR allows for multiple conditions to be valid.

Examples Of Conditional Rendering

Website Mobile Header

One example of using rendering logic is when you want a different header (or part of the header) on mobile. In this case, you could build your header as usual for desktop and apply rendering logic to the holding container that renders it only when the screen size equals desktop, as shown in the left image below.

Then you could create another Avada Container with the mobile header contents and set conditional rendering on it, rendering it only when the screen is mobile, as shown in the image below on the right. You could also make a third container for a tablet, or add (or subtract) it to one of the other conditional statements.

Online Store Cart Page

Another example of how to use Conditional Rendering is when building a WooCommerce store’s Cart Page. When a Cart is empty, for example, you would not want all the usual Cart Elements to display. So by using Conditional Element Rendering across the various Columns and Containers on the page, we could easily achieve that scenario. See the Avada WooCommerce Builder – Cart page for specific details of how to achieve this. Another example can be found in the video at the top of the page.

There are many more scenarios where this feature would be helpful, including rendering content based on whether a user is logged in, or what their role is, whether an Event or Sale has started or finished, and whether the content is being viewed on a mobile or tablet, or even on a specific browser, to name a few examples. This feature brings an incredible level of flexibility to your page content, and is just another example of the innovation we continually bring to the table for Avada users!

Condition Types & Values

In the list below, you can see all the available Condition Types. There is a variety of Relational Operators and Condition Values. As you can imagine, there are many scenarios in which this feature could be used to control the contents of the Container or Column Element. The way to think of it is “I want to render this container if…”

Device Type – Possibly the most basic of all conditional rendering, this allows you to set whether the content renders or not on a particular device type (size). The relational operators are Equal To and Not Equal To, and the possible values are Desktop, Mobile & Tablet, Tablet and Mobile.
GET Variable – This lets you check for a custom variable and value defined in the URL’s query string. It can particularly be useful when redirecting visitors after a form submission or similar. The relational operators are Equal To, Not Equal To, Greater Than, Less Than and Contains.
SESSION Variable – This lets you check for a custom variable and value stored server-side and linked to the session. The relational operators are Equal To, Not Equal To, Greater Than, Less Than and Contains.
User Agent – The User Agent is a short, technical description of the web browser, operating system, (and maybe mobile device) that you’re using as you access the internet. The relational operators are Equal To, Not Equal To, Greater Than, Less Than and Contains, and the Condition value will be the user agent you want to check for.
Referrer – The referrer is the webpage that sends visitors to your site using a link. In other words, it’s the webpage that a person was on right before they landed on your page. The relational operators are Equal To, Not Equal To, and Contains, and the Condition Value is the Referrer URL.
User Role – This is the WordPress User Role. The relational operators are Equal, and Not Equal To, and the Condition Values are whatever user roles you have registered on your website, such as Administrator, Editor, Author, Contributor etc.
User State – This refers to whether the user is logged in or not. The relational operators are Equal To and Not Equal To, and the Condition Values are Logged In, and Logged Out.
Custom Field – Check the value of a WP custom field variable. The relational operators are Equal To, Not Equal To, Greater Than, Less Than and Contains.
Post Published Date – This can be used to check against the publishing date of a post or page. A field lets you specify the format you want to use, so you can limit the check to the year, e.g., the second. The relational operators are Equal To, Not Equal To, Greater Than and Less Than, and the Condition Value also accepts the same inputs as strtotime().
Post Modified Date – This can be used to check against the the last modification date of a post or page. A field lets you specify the format you want to use, so you can limit the check to the year, e.g., the second. The relational operators are Equal To, Not Equal To, Greater Than and Less Than, and the Condition Value also accepts the same inputs as strtotime().
Post Category – This can be used for the Post Category. The relational operators are Equal To and Not Equal To, and the Condition Values will be a list of Post Categories on your site.
Post Tag – This can be used for your post tags. The relational operators are Equal To and Not Equal To, and the Condition Values will be a list of the post tags on your site.
Post Term – This can be used for your post terms. The relational operators are Equal To and Not Equal To, and the Condition Value is a Term ID.
Post Count – This can be used to check whether an archive page has more or less posts than specified by you. The relational operators are Equal To, Not Equal To, Greater Than and Less Than, and the Condition Value is a number.
Term Count – This can be used to check against the total number of terms on a taxonomy archive. The relational operators are Equal To, Not Equal To, Greater Than and Less Than, and the Condition Value is a number.
Term ID – This can be used for your Term ID. The relational operators are Equal To and Not Equal To, and the Condition Value is a Term ID.
Featured images Count – This can be used to check against the number of Featured images that have been set. The relational operators are Equal To, Not Equal To, Greater Than and Less Than, and the Condition Value is a number.
Comment Status – This can be used for the status of a comment. The relational operators are Equal To and Not Equal To, and the Condition Values are Open or Closed.
Comments Count – This can be used to check against the number of comments related to a given post. The relational operators are Equal To, Not Equal To, Greater Than and Less Than, and the Condition Value is a number.
Number Of Headings – This can be used to check against the number of headings used on a given post. This is particularly useful, if you want to display a Tabel of Contents element conditionally. The relational operators are Equal To, Not Equal To, Greater Than and Less Than, and the Condition Value is a number.
Cart Status – This can be used based on the status of the Cart. The relational operators are Equal To and Not Equal To, and the Condition Values are In or Empty.
Sale Status – Similarly, this can be used based on the Sale status. The relational operators are Equal To and Not Equal To, and the Condition Values are Started or Ended.
Stock Quantity – This can be used based on the stock quantity of a product. The relational operators are Equal To, Not Equal To, Greater Than and Less Than, and the Condition Value is simply a number.
Stock Status – This can be used based on the status of stock. The relational operators are Equal To and Not Equal To, and the Condition Values are In Stock or Out Of Stock.
Product Purchase Status – This can be used based on the purchase status of a product. You can add a specific ID for a product, or you can leave the field empty to use the current product. The relational operators are Equal To and Not Equal To, and the Condition Values are Purchased or Not Purchased.
Product Type – This can be used based on the type of the product. The relational operators are Equal To and Not Equal To, and the Condition Values are Simple Product, Grouped Product, External/Affiliate Product or Variable Product.
Product Category – This can be used for the Product Categories. The relational operators are Equal To and Not Equal To, and the Condition Values will be a list of Product Categories on your site.
Product Tag – This can be used for your product tags. The relational operators are Equal To and Not Equal To, and the Condition Values will be a list of the product tags on your site.
Related Products – This can be used for your related products. The relational operators are Equal To, Not Equal To Greater Than and Less Than, and the Condition Value is a number.
Up-Sells Products – This can be used for your Up-Sells products. The relational operators are Equal To, Not Equal To Greater Than and Less Than, and the Condition Value is a number.
Cross-Sells Products – This can be used for your Cross-Sells products. The relational operators are Equal To, Not Equal To Greater Than and Less Than, and the Condition Value is a number.
Product Variations – This can be used for your Product Variations. The relational operators are Has and Has Not, and the Condition Value is the Attrbute name eg. color or size.
Order Received Status – This can be used for the Status of the received order. The relational operators are Equal To and Not Equal To, and the Condition Values are Pending Payment, Processing, On Hold, Completed, Cancelled, Refunded, Failed, or Draft.
Order Received Total Value – This can be used for the total value of your recieved order. The relational operators are Equal To, Not Equal To Greater Than and Less Than, and the Condition Value is the total value of the order. Note. This only works on the Order Received Page (after user checks out).
Order Received Download Count – This can be used for the total number of items in your recieved order. The relational operators are Equal To, Not Equal To Greater Than and Less Than, and the Condition Value is the number of items that can be downloaded on the order receieved page. Note. This only works on the Order Received Page (after user checks out).
Event Status – This can be used based on the status of your event. The relational operators are Equal To and Not Equal To, and the Condition Values are Started or Ended.
ACF Field – This can be used for your ACF Fields. There is a Field Name field, and the relational operators are Equal To, Not Equal To Greater Than, Less Than and Contains. The Condition Value is needs to match the type of the field.
ACF Repeater Count – This can be used to check against the number of rows available for a single repeater field. There is a Field Name field, and the relational operators are Equal To, Not Equal To Greater Than, Less Than and Contains. The Condition Value is is a number.
ACF Repeater Single Value – This can be used for your ACF Repeater Single Values. There is a field for the field name and value – field[1][name], and the relational operators are Equal To, Not Equal To Greater Than, Less Than and Contains. The Condition Value needs to match the type of the repeater sub field.
ACF Repeater Sub Field – This can be used for your ACF Repeater Sub Field. There is a Sub Field Name field, and the relational operators are Equal To, Not Equal To Greater Than, Less Than and Contains. The Condition Value needs to match the type of the repeater sub field.
ACF Relationship Count – This can be used to check against the number of available ACF Relationships. There is a Field Name field, and the relational operators are Equal To, Not Equal To Greater Than, Less Than and Contains. The Condition Value is a number.