Display Rules

Display Rules let you configure when and to whom your campaigns appear. They are divided into three sections: Audience Targeting, Triggers, and Safeguards.

Note

If you enable one or more rules at a time, all conditions must be met for the campaign to show.

AUDIENCE TARGETING

Audience Targeting lets you show or hide campaigns based on whether a visitor belongs to a specific audience segment in your CRM/ESP integration (such as Voyado or ActiveCampaign).

To use this feature, you need a connected integration that supports audience segments. Once configured, Fluentos checks the visitor’s audience membership in real time and displays the campaign only if the condition is met.

The following strategies are available:

• In audience: Show the campaign only to visitors who belong to the selected audience.
• Not in audience: Show the campaign only to visitors who do not belong to the selected audience.

Use Case

Show an exclusive loyalty discount campaign only to visitors who are part of your “VIP Members” audience in Voyado or ActiveCampaign.

TRIGGERS

1. Landing

Enabling this trigger means the campaign will appear on the website as soon as the user loads the website page.

2. New Customers

If you want to target first-time visitors only, you can enable this trigger.

Use Case

You can enable the above two triggers at the same time if you want to target new customers/first-time visitors upon landing on your website.

3. Returning Customers

Enable this trigger if you want to target returning customers (who have visited your website in the past).

Note

An end-user who visited the website in the past but cleared their cache will be treated as a new user/customer rather than as a returning customer.

No Display Situation

You cannot enable the New Customers and the Returning Customers triggers at the same time for a campaign because these two cases conflict. If you enable both of these triggers for a campaign, it will not be displayed on the website.

4. Exit Intent

If enabled, it will trigger the campaign to run and display the popup on the website when the end-user’s mouse moves outside the browser’s bounds. For example, when the user attempts to move the cursor to open a new tab or switch to another tab.

Desktop Only

Exit Intent works only on Desktop.

5. Visited Page Count

If enabled, this trigger runs the campaign only when certain page count conditions are met. You can configure this trigger with the following two types of settings. Only one of the following can be selected at a time for a campaign. Use the Value dropdown to choose the page count. The minimum value allowed is 1, and the maximum value can be 20.

• Is Equal to a Page Count: This option is used when the visited page count exactly matches the defined number. For example, if the page count value is 4, then the campaign will appear on the website when the user has visited exactly four pages of the website or visited the same page four times (by refreshing the page).

  Note

  The campaign will disappear once the page count exceeds the defined limit. For example, on the fourth-page visit, the campaign appears, but when the user refreshes the page or navigates to another page of the website, it ceases to appear.

• Is More than a Defined Page Count: The campaign appears only when the visited page count exceeds the defined value. For example, if the defined page count value is 4, the campaign will appear when the user visits the fifth page or the same page a fifth time (by refreshing/reloading).

  Note

  In this case, the campaign will continue appearing on every page the user navigates after the defined page count is reached.

Use Case: Feeling Lost?

This trigger can be used to offer help to the end users as they navigate across the website. For example, if their visited page count reaches 10, you can display the popup asking if they are looking for anything specific and direct them to the help pages or the contact page.

6. Scroll Position

Using this trigger, you can configure the campaign behavior more discreetly by allowing the campaign to be displayed only when the user has scrolled through the website by a certain percentage.

Use Case

Configure the trigger with a 50% value such that the campaign will be displayed only when the user has scrolled more than 50% of the website page or on a specific page of the website (in combination with the Website URL trigger).

7. Time Spent

Using this trigger, you can control the campaign’s display timing. So, instead of launching the campaign right away when the website is loaded, you can time it to appear, let’s say, 10 seconds after the user loads the website or the website page. It can be configured for minutes and seconds in the following two ways.

• Session Start: Configuring the minutes/seconds for this option will display the campaign on the website when the defined time has passed after starting the website session, i.e., when the user enters the website.

  Note

  In this case, the campaign will keep appearing as the user navigates through the website until or unless the user closes it explicitly.

• Page Start: This option allows you to configure the campaign display behavior at the page level instead of the session level. For example, if you set the time spent to 10 seconds with this option, the campaign will appear exactly after 10 seconds on the website page.

  Note

  In this case, the campaign appearance timing is applied to each page of the website. It disappears when the user navigates to another page and reappears on the new page as per the configured minutes/seconds settings.

Tip

Displaying a campaign upon website landing is annoying for end users. For the best results, use 8-10 seconds.

8. Geo Location

This trigger allows you to launch your campaign in specific countries using the Include option. Similarly, you can choose to target the whole world with the exception of a few countries that you can keep out using the Exclude option.

9. Localized Page Only

If enabled, the campaign popup will be launched only for the localized pages i.e., it will not be displayed on the non-localized pages of the website.

10. Website URL

Using this trigger, you can specify the pages of your website on which the campaign should appear. For example, you may want to display a campaign only when the users are on their cart page. You can use the following parameters to specify the URL for which the campaign should run.

• Contains: Use this option to define the word the website URL should contain. For example, “cart”.
• Does Not Contain: Use this option to specify a page that you want to exclude. For example, if you don’t want to display the campaign on the About Us page, you can enter a term that appears in the About Us page URL; let’s say it’s “about-us.”
• Is Exactly: Use this option to specify the exact URL of the web page. When you select this option, enter the part of the URL that appears after the domain. For example, if the page URL is https://demo.fluentos.com/details/6, enter /detail/6 in the Value field.

If you want to run it on multiple web pages, you can use a combination of AND/OR operators.

11. Website Cookie

Using this trigger, you can run a campaign only for users with specified cookie data stored on their browsers. For example, if you want to display a campaign only for the website’s beta testers, you can define a cookie with a specific value for them.
Using the AND/OR operators, you can combine different conditions for the website cookie to be evaluated for running the campaign.

The following matching strategies are available:

• Contains: The cookie value contains the specified text.
• Does Not Contain: The cookie value does not contain the specified text.
• Is Exactly: The cookie value exactly matches the specified text.
• Has any value: The cookie exists on the browser, regardless of its value.
• Is not set: The cookie does not exist on the browser.

Use Case

Use the cookie-based trigger to control campaign visibility for specific user types - logged-in or guest.

• Logged-In Users: Use Has any value on a session cookie to show exclusive offers only to logged-in users.
• Guest Users: Use Is not set on the same cookie to display signup prompts exclusively to guest users.

12. Website Global Variable

This trigger lets you show or hide campaigns based on JavaScript variables defined on your website. For example, you can target users based on a window.isLoggedIn or window.customerTier variable set by your site’s code.

Using the AND/OR operators, you can combine multiple variable conditions.

The following matching strategies are available:

• Contains: The variable’s value contains the specified text.
• Does Not Contain: The variable’s value does not contain the specified text.
• Is Exactly: The variable’s value exactly matches the specified text.
• Has any value: The variable is defined on the page, regardless of its value.
• Is not set: The variable is not defined on the page.

Use Case

Use Has any value on a variable like customerTier to show loyalty offers only to customers with an assigned tier. Use Is not set to show a generic welcome campaign for anonymous visitors.

13. Referring Website

Using the Include option, you can run your campaign only for users landing on your website through a specific website, such as those coming from Google, Yahoo, and Bing. You can select multiple referring websites from the Referring Website List.

Or, if you want to exclude the users being referred through the specific website(s), you can use the Exclude option and select the unwanted websites from the list.

Use Case

Show specific promos for users coming from organic searches.

14. Device Type

There may be campaigns that you want to run only for desktop or mobile users. You can use this trigger to select the desired device type based on marketing/business needs. Available options to choose from are:

• Desktop Only
• Mobile Only

If this trigger is disabled, the campaign is launched for both types of devices by default.

Use Case: Install App

Prompting mobile users to download the mobile app.

15. HTML Element

This trigger lets you show or hide campaigns based on whether a specific HTML element is present on the page. Enter a CSS selector (such as a class name or ID) to target.

The following matching strategies are available:

• Element Exists: The campaign is shown when the specified element is found on the page.
• Element Does Not Exist: The campaign is shown when the specified element is not found on the page.

Use Case

Show a campaign only when a .cart-items element is present — meaning the user has items in their cart.

16. Browser Agent

You can use this trigger to control the campaign appearance based on the end-user’s browser agent details. For example, if you want to display it to the users using the app that embeds the browser and not using the native application, then you can configure it here.

The embedded browser will have a specific browser signature that you can enter in the Value field to specify the application, and select “Contains” under the Select Matching Category. This way, you will allow the campaign to be displayed only on the application when it is opened in the embedded browser.

The following matching strategies are available:

• Contains: The user agent string contains the specified text.
• Does Not Contain: The user agent string does not contain the specified text.
• Is Exactly: The user agent string exactly matches the specified text.

17. DataHub

DataHub requires defining trigger values and pushing them from your website using JavaScript.

Using this trigger, you can personalize the user experience by displaying the campaign based on their use case. For example, you want to display a free shipping campaign to the user when the order value reaches a specific limit.

Learn how to configure the DataHub.

SAFEGUARDS

18. Limit Opens per Session

Prevents repeated popups on multi-page sites by limiting how many times a campaign can open per session. After reaching the limit, the campaign will not open again until a new session starts.

19. Re-Engage

If enabled, this allows you to increase the chances of customer interaction or engagement with the campaign. In other words, if the user closes the campaign upon their first encounter with it, then by default, it will not be displayed to them even if they refresh the page. However, if this is enabled, you can display the campaign to the end-user again after a specific time. The following options are available:

• Select the Time in: Select from minutes, hours, or days to define the time measuring unit.

• Time: Select the time value from 1 - 60. This digit will identify the delay time between the first and the next display, for example, after 1 minute.

• Limit To: Using this setting, you can limit the number of times the campaign should be displayed to the user. To limit, you can define a number from 1 - 20. For example, if you set it to 2, the campaign will be displayed only two more times after it was first closed by the user, according to the time delay settings.

  Setting it to No Limit will display the campaign to the end user each time they load the webpage.

Limit Counter

The limit counter has nothing to do with a user session but relates to the browser cache. It resets to zero (0) when the user clears their browser cache.

Use Cases

1. Asking the users to subscribe to the newsletter again in 14 days, two more times.
2. If you have something like free shipping on the basket, then it’s unlimited with a 1-day delay.

Recommendation

We recommend re-engaging at most five times, as this will annoy users when it comes to newsletter subscriptions.

AND / OR Operators

AND

This operator combines two or more conditions so that the trigger runs only when all of the conditions are true.

For example, if you consider the image below, the campaign will be launched on the website page if its URL contains the keyword “products” and does not contain the word “test”.

OR

This operator is used to combine two or more conditions in such a way that the trigger will run even if one of the conditions is true. For example, if you want to run the campaign for three website pages using the Website URL trigger, then you will use the OR operator. In this case, even if one website page is taken down, the campaign will run for the remaining two pages defined.

For example, in the image shared above, three different website URLs are specified using two OR operators.

In short, the campaign will run even if one of the conditions is true for the trigger.