Elementor Display Conditions let you control whether a selected page element appears in a particular context. Instead of showing identical content to every visitor, you can define rules related to the current page or post, author, category, login status, date, time, archive or referring URL. This makes conditional visibility useful for notices, audience-specific messages and content that belongs only in a defined location.
The configuration is practical, but it requires careful testing. A visibility rule determines whether an element is displayed; it is not a complete security boundary for confidential information. The following guide explains how to configure Elementor conditional visibility, select suitable criteria, combine rules with AND or OR logic, use template conditions and investigate cache-related problems before publishing.
What Elementor Display Conditions Do
Display Conditions can be applied directly to a regular Elementor element. You select the element in the Elementor Editor, open the relevant Display Conditions control in its settings, add a rule and select the criterion and value that should determine visibility. The element is then shown or hidden according to the current page, visitor, date and time context, or another supported condition.
For example, a notice can be limited to content associated with a particular author, a message can be displayed only to logged-in visitors, or an element can be placed in a defined page or archive context. The condition does not take effect merely because it was configured in the editor. The page must be saved or published before you evaluate the result on the live page.
This mechanism is designed for presentation and content targeting. It should not be treated as the sole protection for private material. If content is confidential or access-restricted, use appropriate WordPress permissions, membership controls, server-side access controls or another purpose-built protection method. Also consider whether role-based, referral-based or URL-related visibility could disclose information that should remain private.
How to Add a Condition to an Elementor Element
Start with the element whose visibility should change. It may be a text block, notice or another regular element already placed on the page. In the Elementor Editor, select that element and open its Display Conditions control in the element settings. Add a condition, choose the relevant type and then select the value or values that define a matching context.
Some condition fields allow multiple values within one rule. For instance, an author condition can include several selected authors. This can be clearer than creating separate entries when the same visibility requirement applies to more than one author. The available choices depend on the context in which the rule is being configured, so distinguish regular page elements from global templates when planning the setup.
After configuring the rule, save or publish the page. Then test a matching context and a non-matching context. If the rule concerns users, check both logged-in and logged-out views. If it concerns posts, categories, authors or URLs, use representative examples rather than testing only the page currently open in the editor.
- Select the element that should be conditionally displayed.
- Open Display Conditions in the element settings.
- Add a condition and select its criterion and value or values.
- Save or publish the page.
- Test both a qualifying and a non-qualifying context.
Available Elementor Condition Types
Elementor documents condition types covering content, visitors, time and referral context. The suitable choice depends on what should qualify a visitor and where the element is being displayed. A rule based on the current post is different from a rule based on the URL that referred the visitor, even though both can affect what someone sees.
Pages, posts, archives, and URLs
Content-related conditions can use page hierarchy, including a page parent, as well as post or page author. Other documented criteria include categories, tags, publication date and modified date. Archive conditions can target archive categories and tags. These rules are useful when an element belongs to a defined content group rather than to every page.
Elementor also documents the visitor’s referring URL as a condition. This refers to the URL from which the visitor arrived, not necessarily the current page being viewed. Referral-based visibility should be tested carefully, particularly when the visible message could reveal information about a visitor’s source or segmentation.
Global site-part templates have their own targeting contexts. Headers, footers and other documented template locations can use inclusion or exclusion conditions for the entire site, individual pages, singular content, archives, authors, categories and tags. Therefore, the exact list presented in the editor should be interpreted in relation to whether you are editing an element or a template.
Users and time-based rules
User-related criteria include login status, user role and registration date. These can help distinguish a message for logged-in visitors from one intended for visitors who are not logged in. They can also identify a role or registration-date context, but visible role-based output should be checked against the site’s privacy and disclosure requirements.
Time-related criteria include day of the week, time of day and current date. Elementor states that these conditions use the website server’s date and time, not the visitor’s device time. That distinction matters when visitors are in different time zones. Before using a time-based rule for a deadline, promotion or compliance-related notice, account for the server-time assumption and test the intended scenarios.
AND, OR, and Mixed Condition Groups
AND and OR determine how Elementor evaluates multiple conditions. With AND logic, the element is displayed only when all connected conditions are met. This is suitable when several requirements must be true at the same time, such as a specific content context together with a defined author or time-related requirement.
With OR logic, the element is displayed when at least one connected condition is true. Use it when several alternative contexts should qualify for the same element. For example, an element may be intended for visitors arriving from either of two qualifying sources, rather than requiring both sources simultaneously.
Elementor also documents mixed structures in which OR condition groups are combined with AND-connected rules. This allows shared requirements to apply alongside alternatives, but it makes the rule harder to audit. Translate the requirement into plain language before configuring it: first identify what must always be true, then list the alternative situations that should qualify.
Choosing the logic before configuring it
Write the intended audience or context as a short statement. If every requirement must be satisfied, plan an AND relationship. If any one of several alternatives is sufficient, plan OR. If some requirement is shared while other requirements are alternatives, plan a mixed structure. After saving, test at least one positive and one negative case for each logical branch. A visually complex arrangement can appear correct in the editor while producing an unintended audience on the live page.
Using Display Conditions in Elementor Templates
When the same visibility rule must be repeated across several locations, a global site-part template can be more practical than configuring each element instance separately. Elementor documents inclusion and exclusion conditions for templates such as headers and footers. These conditions can target the entire site, individual pages, singular content, archives, authors, categories and tags, depending on the template context.
Template-level targeting is different from applying a condition directly to a regular page element. The template determines where a global site part is included or excluded, while an element condition controls the selected element. Reusing a template can avoid repeating the same setup on every instance, but it does not remove the need for testing.
Before publishing, check whether inclusion and exclusion rules conflict. Verify the intended header, footer or other template in representative page, post, archive, author, category and tag contexts where those contexts are part of the configuration. This helps separate a template-assignment issue from a condition applied to an individual element.
Cache Troubleshooting and Pre-Publishing Tests
Elementor Display Conditions can depend on dynamic information: login state, page or post context, referring URL, server date or time and other request-related details. Caching may store already-rendered HTML or an element’s output and then reuse it for a later request. As a result, a visitor can see stale or contextually incorrect visibility, such as output prepared for another visitor state.
Elementor warns that advanced caching and caching plugins can interfere with dynamic Display Conditions. Its element-caching documentation also warns that cached elements should be static and that elements using dynamic information can cause issues when cached. This is different from treating every page element as safely reusable static output.
Cache troubleshooting is therefore a process to test, not a universal fix. Review the relevant hosting, page-cache, CDN, object-cache and Elementor-related settings available on the site. Clear affected caches where that option exists, consider excluding dynamic pages or elements where appropriate, and test disabling advanced caching if the conditional output remains incorrect. The exact procedure depends on the site’s configuration.
A practical cache-check sequence
Begin by comparing the editor’s expectation with the live page. Test more than one visitor state, including logged-in and logged-out views. Then check the content context, relevant URL and server-time assumption used by the condition. If the result is stale, review each applicable cache layer rather than changing several unrelated settings at once.
- Test a matching and non-matching context on the live page.
- Compare logged-in and logged-out views where login status is used.
- Review relevant hosting, page, CDN and Elementor cache settings.
- Clear affected caches or test an appropriate exclusion.
- Change one cache-related factor and repeat the test.
Clearing a cache may reveal a change, but it does not establish that every cache layer has been addressed. Retest after each change and avoid assuming that one procedure applies to every hosting provider, CDN, caching plugin, theme or third-party extension.
Final visibility checklist
Use a short checklist before publishing conditional content. Confirm the intended rule, logical relationship and scope. Then test both matching and non-matching authors, categories, roles or URLs wherever they are used. Check date and time assumptions against the website server rather than relying on the visitor’s device clock.
- Test logged-in and logged-out states.
- Check representative pages, posts, archives and referral contexts.
- Verify positive and negative cases for AND, OR or mixed logic.
- Repeat the test after clearing or adjusting relevant caches.
- Check representative devices and the live published page.
- Confirm that sensitive content has separate, suitable access protection.
These checks do not prove universal compatibility with every hosting, cache, theme or extension configuration. They provide a disciplined way to identify whether an unexpected result comes from the condition, its scope, the visitor context, server time or cached output.
Conclusion: Make Conditional Content Easier to Audit
Elementor Display Conditions are most useful when the intended context is defined before configuration. Select the element or template, choose the relevant page, post, user, date, time, archive or URL criterion, set the logical relationship, save or publish, and test the live result. For repeated rules, consider the documented template-level inclusion and exclusion approach, while checking for conflicts.
Keep AND, OR and mixed groups readable, and treat cache behavior as part of the implementation rather than an afterthought. Always test the visitor states and content contexts that matter on the site. Conditional visibility can shape presentation, but confidential content still requires appropriate access control. Choose the simplest rule that accurately represents the intended audience and remains easy to verify later.
Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.