There may be times when you don’t want your campaigns to appear on certain pages, such as specific product pages, checkout screens, or landing pages. You can do this easily by creating a "Hide Pages" targeting rule and applying it to your campaigns. In this guide, we'll show you how to manage these exclusions using two different methods.

There are two ways to set the targeting rule to hide popups on certain pages:

This method is ideal if you have a list of pages where you never want popups to show. By creating a global rule, you can apply it to multiple campaigns simultaneously.

Navigate to the Campaigns section in the Alia Dashboard.

Click on Targeting Rules from the top navigation menu.

Click the "Create Rule" button.

Name the rule something recognizable, such as Hide on Pages. This is where you'll define your exclusions.

Click on save.

Under your new "Hide Pages" rule, add the following conditions:

Select "Is not on page(s)" from the dropdown menu.

Choose "By path only".

Select "Contains" and enter the page path you want to exclude (e.g., /products/123).

Click Add to include the path. You can add multiple paths like /checkout, /thank_you, or /account.

Go to the specific campaign you want to edit.

Select "Targeting in new visitors".

Select Add condition > In targeting rule or campaign.

Select the Hide pages rule you just created and click Save.

If you only need to hide a popup on a specific page for one particular campaign, you can set the rule directly within that campaign's settings.

Step 1: Click on "Targeting in new visitors" within the specific campaign dashboard.

Step 2: Add the following conditions:

Select "Is not on page(s)"

Choose "By path only"

Select "Contains" and enter the page path (e.g., /sale-landing-page, /products)

Click Save.

If more than one campaign is eligible on the same page, they can conflict or appear at the same time. When you want a specific popup to run on a page, explicitly exclude your other campaigns from that page using the methods above.

This is also a common reason for a low popup view rate: eligible visitors are counted, but another campaign takes priority and blocks the popup from displaying.

To hide the floating button on specific pages without hiding the popup itself, use a Prism element with page-level targeting rules rather than a campaign-level page exclusion.

A popup can be suppressed when a specific cookie is present. This requires custom code that checks for the cookie and prevents the popup from displaying if it exists.

The same approach can be used to hold a popup until cookie or privacy consent has been accepted, by checking for consent-related cookies (such as _ga, _fbp, or _shopify_y) before allowing the popup to trigger.

Visitors arriving from in-app browsers, such as Instagram or Facebook, can be excluded using UTM parameter conditions like source or medium, but only when those parameters are present in the URL.

Two limitations to be aware of:

Now that you've configured your exclusions, you should test your campaign by visiting the excluded pages in an incognito window to ensure the popup does not appear.