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.

If-So Dynamic Content

Effortless Personalization, Right Inside Elementor 
Craft personalized experiences for your visitors with ease. Dynamically adapt your Elementor pages based on location, behavior, search terms, and more.
Tailor every interaction to create unique and memorable experiences for each visitor.
<h4>How Simple Is It?</h4>
<ol>
<li>Click an Element</li>
<li>Choose a Condition</li>
</ol>
<h4>Endless Possibilities and Advanced Features</h4>
<ul>
<li>Set fallback content: Define default content for when conditions aren’t met. </li>
<li>Create audiences: Assign users to audiences based on their behavior to ensure personalized content across multiple visits. </li>
<li>User Self-Selection: Give visitors control over their experience by letting them assign themselves to audiences. </li>
<li>Dynamic Keyword Insertion: Personalize content with keywords that dynamically adjust based on user attributes or context. </li>
<li>WooCommerce Integration: Seamlessly integrate with WooCommerce to create targeted product recommendations, promotions, and more. </li>
<li>Conditional Countdowns: Add urgency with countdowns triggered by user behavior. </li>
</ul>
<h4>An All-in-One Geolocation Service</h4>
<ul>
<li>Combined Geolocation: Leverage IP-based location and the HTML5 Geolocation API for precise targeting. </li>
<li>Location-Based Content: Display content by country, state, or city using IP-to-location service and/or HTML5 Geolocation API. </li>
<li>Geolocation Dynamic Keyword Insertion: Dynamically display users’ location details with simple shortcodes. </li>
<li>Automatic Time Adjustment: Automatically adjust event times to match users’ time zones. </li>
</ul>
<h4>Use Cases & Versatility</h4>
Enhance each visitor’s journey: 
– Geolocation: Target visitors by country, state, or city. 
– Time-Based Content: Schedule content for specific times or dates. 
– Returning Visitors: Differentiate content for first-time and repeat visitors. 
– Traffic Source: Customize content based on traffic source (e.g., search engines, social media). 
– Geo-Targeted Offers: Display local deals or region-specific information. 
– Time-Based Promotions: Run targeted sales, events, or countdowns.
<a href="https://www.if-so.com/personalization-examples?utm_source=WordPress&utm_medium=Readme&utm_campaign=ElementorIntegration&utm_term=examples" rel="nofollow ugc">More usage examples >></a>
<h4>Why If-So?</h4>
<ul>
<li>Built for Simplicity: Easy installation, intuitive conditions, and straightforward management. </li>
<li>Powerful Targeting: Choose from a broad list of conditions for unparalleled flexibility. </li>
<li>Caching-Compatible: Fully functional with popular caching plugins. </li>
<li>Advanced Features: Access a wide array of dynamic content tools.</li>
</ul>

If-So Conditional Content for Elementor

Conditional Logic for Elementor. No setup or coding required. Fully compatible with any caching solution.

RenderWhen for Blocks vs If-So Conditional Content for Elementor