Understanding Logical Conditions and Datasets #

Before we dive into the practical aspects of configuring “When to Display,” let’s understand two key concepts:

1. Datasets
2. Logical Conditions

Datasets #

Datasets are sets of logical conditions that you can use to further refine when your dynamic blocks should appear.

Think of them as collections of rules that add an extra layer of precision to your conditions, ensuring that your blocks are displayed to the right audience at the right time.

For example, you can use datasets to specify that a block should only be displayed to users who have visited a certain number or type of pages or have added items to their cart.

This level of granularity allows for even more precise targeting.

Logical Conditions #

Logical Conditions are rules that you define to trigger the display of your dynamic blocks.

These rules can be based on various factors, such as user behavior, user roles, browser and device specifications, date and time, screen size, URL source, metadata, WooCommerce-specific parameters, or even specific pages on your website.

With over 150 logical conditions at your disposal, you can create highly customized triggers.

To explore all available datasets and logical conditions and how to implement them effectively, refer to our detailed guide on Datasets & Logical Conditions.

Configuring “When to Display” Trigger #

Now, let’s get into the practical steps of configuring the “When to Display” trigger for your dynamic blocks.

In your Dynamic Blocks Plugin, navigate to the “When to Display” section.

3. Access the “When to Display” Tabs
4. Choose Datasets
   First, you’ll choose from a range of datasets that best align with your goals.
   Datasets are collections of logical conditions that add an extra layer of precision to your triggers, ensuring that your dynamic blocks are displayed to the right audience at the right time.
5. Select Logical Conditions
   Within your chosen dataset, select the logical conditions that should trigger the display of your dynamic blocks.
   These conditions can be based on a variety of factors, from user behavior and roles to device specifications, date and time, and more.
6. Test and Monitor
   Before making your trigger live, it’s a good practice to test it thoroughly.
   Ensure that your logical conditions and datasets are working as intended.
   Additionally, monitor the performance of your dynamic blocks over time and make adjustments as necessary.
7. Save and Activate
   Once you’re satisfied with your trigger settings, save and activate them.
   Your dynamic blocks will now display according to the conditions you’ve set.

Examples of Effective “When to Display” Scenarios #

1. Limited-Time OffersDisplay time-sensitive promotions during specific dates or hours.
2. User EngagementTrigger interactive content after users spend time on your site or visit multiple pages, improving the user experience.
3. Add Badges for Increased ConversionsUse dynamic blocks to display badges like “New Arrival,” “Bestseller,” or “Top Rated” on product pages.
   These badges boost perceived product value and encourage conversions.
   Automatically add or remove badges based on criteria like product availability or customer ratings.
4. Badges for Payment MethodsDisplay badges such as “Secure Checkout” or “Multiple Payment Options” next to payment methods during checkout.
   Increase customer trust and confidence, encouraging completed purchases.
5. Upselling and Cross-sellingSuggest related products on specific product or category pages.
   Increase average order value and offer a personalized shopping experience.

These scenarios showcase the power of “When to Display” for customizing user experiences, improving conversions, and enhancing your website’s overall appeal.

What’s Next? #

In the next guide, we’ll explore How to Configure General Settings to add custom CSS and JavaScript, as well as UTM parameters for Google Analytics tracking.

These techniques will take your content personalization to the next level and allow you to closely monitor your content’s performance.