Abhishek Kumar

RenderWhen for Blocks adds conditional visibility to every block in the WordPress block editor. Decide who sees what, and when, with a panel that reads exactly how you’d say it out loud:
<blockquote>
Show this block when the user is logged in. 
 Show this block when the date is between March 1 and March 31. 
 Show this block when the device is mobile.
</blockquote>
RenderWhen is built around two ideas that set it apart from other visibility plugins:
<ul>
<li>Server-side rendering only. When a block is hidden by a condition, it is not rendered into the page output at all. No CSS <code>display: none</code>, no DOM bloat, no leaked content in view-source. Search engines, screen readers, and your page weight all benefit.</li>
<li>Public Conditions API. The three built-in conditions are registered through the same public API your plugin or theme can use to add your own. No hacks, no internal-only code paths.</li>
</ul>
In the editor, a subtle dashed border marks every block that carries a visibility rule, so a rule-bearing block never disappears from the published page as a surprise. A “Preview as audience” sidebar lets you simulate a logged-out visitor, a specific role, or a different device class right in the editor — blocks whose rule would hide them fade out with a clear badge, no save-and-reload cycle required.
<h4>Built-in conditions (v1.0)</h4>
<ul>
<li>User state — show to logged-in users, logged-out users, or specific roles</li>
<li>Date range — show between two datetimes, timezone-aware</li>
<li>Device type — show on desktop, tablet, or mobile</li>
</ul>
<h4>Designed for</h4>
<ul>
<li>Agencies and freelancers building client sites who want a clean, predictable visibility tool</li>
<li>Developers who need an extension point, not another walled garden</li>
<li>Anyone who cares about page weight and SEO hygiene</li>
</ul>
<h4>What this plugin deliberately does NOT do</h4>
It does one thing well rather than ten things adequately. Out of scope in v1.0:
<ul>
<li>Multi-condition AND/OR groups (planned for v1.1)</li>
<li>URL / cookie / referrer / geolocation conditions</li>
<li>WooCommerce, ACF, or membership integrations</li>
<li>A settings dashboard</li>
</ul>
If you need those today, <a href="https://wordpress.org/plugins/conditional-blocks/" rel="ugc">Conditional Blocks</a> and <a href="https://wordpress.org/plugins/block-visibility/" rel="ugc">Block Visibility</a> are excellent and well-established choices.
<h4>For developers</h4>
Register a custom condition in three steps. Implement the interface, add it to the registry, ship.
<pre><code>add_action( 'renderwhen_register_conditions', function ( $registry ) {
 $registry->register( new My_Plugin\\Conditions\\Country_Condition() );
} );
</code></pre>
Your condition class implements <code>RenderWhen\Conditions\Interface_Condition</code>:
<pre><code>namespace My_Plugin\Conditions;

use RenderWhen\Conditions\Interface_Condition;

class Country_Condition implements Interface_Condition {
 public function get_id(): string {
 return 'country';
 }

 public function get_label(): string {
 return __( 'Visitor country', 'my-plugin' );
 }

 public function get_schema(): array {
 return array(
 'type' => 'object',
 'properties' => array(
 'countries' => array(
 'type' => 'array',
 'items' => array( 'type' => 'string' ),
 ),
 ),
 );
 }

 public function evaluate( array $settings, array $context ): bool {
 $current = my_plugin_detect_country();
 return in_array( $current, $settings['countries'] ?? array(), true );
 }
}
</code></pre>
The full set of public filters:
<ul>
<li><code>renderwhen_register_conditions</code> — register your conditions here</li>
<li><code>renderwhen_evaluate_{condition_id}</code> — last-mile override of any condition’s result</li>
<li><code>renderwhen_render_block_hidden</code> — fires when a block is hidden, useful for cache busters and SEO tools</li>
<li><code>renderwhen_device_type</code> — swap in your own device detection</li>
</ul>
The plugin is developed openly on GitHub. Issues, PRs, and architecture discussions welcome: https://github.com/abhishekfdd/renderwhen

RenderWhen for Blocks

Show or hide any block when conditions match. Developer-first API and true server-side rendering — hidden blocks never reach the browser.

BuruhDev

LogicKit for Elementor turns Elementor into a dynamic marketing engine. It adds a “LogicKit Rules” panel to the Advanced Tab of every Elementor Widget, Container, and Section.
Stop showing the same static content to everyone. Personalize your site based on who the user is and what is in their shopping cart.
Top 6 Use Cases
<ol>
<li>B2B / Wholesale Portals: Hide “Add to Cart” buttons for guests. Show bulk pricing tables only to users with the “Wholesale” role.</li>
<li>Cart Upsells: If a user has a Camera in their cart, automatically show a banner for SD Cards.</li>
<li>Scarcity Marketing: Automatically hide sale banners when the offer expires (Date/Time logic) or show “Low Stock” warnings when inventory < 5.</li>
<li>Ad Tracking: Personalize landing pages based on UTM parameters (e.g., show specific content for visitors from Facebook Ads).</li>
<li>VIP Loyalty: Show exclusive content to customers who have a total lifetime spend of over $500.</li>
<li>Mobile Optimization: Show “Call Now” buttons only on mobile devices and “Download App” buttons only on iOS/Android.</li>
</ol>
Why use LogicKit for Elementor?
<ul>
<li>Native Integration: Works seamlessly in the Elementor Advanced Tab.</li>
<li>Zero Bloat: Elements are removed from the PHP render cycle (not just hidden with CSS), keeping your site fast.</li>
<li>WooCommerce Ready: Deep integration with Cart Totals, Stock Status, and Purchase History.</li>
</ul>
<h3>The 25+ Logic Conditions</h3>
User & Role
<ul>
<li>User is Logged In / Guest</li>
<li>Specific User Role (Admin, Customer, Shop Manager, etc.)</li>
<li>Specific User ID</li>
<li>User Meta (Custom Field Check)</li>
</ul>
Cart Intelligence
<ul>
<li>Cart is Empty / Has Items</li>
<li>Cart Total > Amount (Great for Free Shipping nudges)</li>
<li>Cart Item Count > X</li>
<li>Cart Item Count < X</li>
<li>Cart Weight > X (For shipping warnings)</li>
<li>Specific Product in Cart</li>
<li>Specific Category in Cart</li>
<li>Coupon Code Applied</li>
</ul>
Customer History
<ul>
<li>Total Lifetime Spend (High value targeting)</li>
<li>Has Purchased Product (Post-purchase support)</li>
<li>Days Since Last Order (Win-back campaigns)</li>
</ul>
Product Context
<ul>
<li>Stock Status (In Stock, Out of Stock, Low Stock)</li>
<li>Is On Sale</li>
<li>Product Type (Virtual, Downloadable)</li>
<li>Product Price > Amount</li>
</ul>
Date & Time
<ul>
<li>Specific Date Range (Start/End)</li>
<li>Day of Week (Recurring)</li>
<li>Time of Day (Business Hours)</li>
</ul>
Device & Marketing
<ul>
<li>Device Type (Mobile, Tablet, Desktop)</li>
<li>Operating System (iOS, Android, Windows, Mac)</li>
<li>URL Query Parameter (UTM tags)</li>
<li>Referrer Domain</li>
</ul>

LogicKit for Elementor

Add powerful visibility rules to Elementor. Hide or show widgets based on User Role, Cart Total, Date/Time, and more.

RenderWhen for Blocks vs LogicKit for Elementor