Skip to main content

Hide popups on certain pages

Use a saved targeting rule or a campaign's own targeting to keep popups off certain pages.

Written by Rob D

You might not want popups on some pages, such as certain product pages, your account pages, or a landing page. You can hide them in two ways:

  1. A saved targeting rule, which you can add to as many campaigns as you like. Best when several campaigns should skip the same pages.

  2. A campaign's own targeting, which only affects that campaign.

Method 1: Use a saved targeting rule

With a saved rule, you list the pages once and add the rule to each campaign that should skip them. When you update the rule, every campaign using it updates too.

Step 1: Create the rule

  1. Go to Campaigns > Targeting rules.

  2. Click Create rule and give it a clear name, such as "Hide on these pages".

  3. Click Select a filter and choose Is not on page(s).

  4. Choose By path only, then Contains.

  5. Enter each page path you want to exclude, such as /products/123, /pages/about, or /account.

Changes on the Targeting rules page save automatically.

Step 2: Add the rule to your campaign

  1. Go to Campaigns and click Targeting on the campaign's card.

  2. Click Select a filter and choose In targeting rule or campaign.

  3. Choose your "Hide on these pages" rule.

  4. Click Save.

Repeat Step 2 for each campaign that should skip these pages.

šŸ’” Tip: To exclude more pages later, just edit the saved rule. Every campaign using it updates automatically.

Method 2: Use a campaign's own targeting

To hide only one campaign's popup on certain pages:

  1. Go to Campaigns and click Targeting on the campaign's card.

  2. Click Select a filter and choose Is not on page(s).

  3. Choose By path only, then Contains, and enter each page path, such as /sale-landing-page.

  4. Click Save.

šŸ’” Note: If you have a long list of pages, or several campaigns should skip them, use Method 1. It saves time and keeps your campaigns consistent.

Contains or Exact match?

  • Contains matches any page whose path includes what you enter. Use it unless you need one exact page. Product URLs often have extras like ?variant= that make an exact match fail.

  • Exact match matches only that path. Use * as a wildcard, for example /products/*.

Paths are case sensitive. A trailing slash doesn't matter.

šŸ’” Tip: You can also ask Lia, Alia's built-in AI assistant, to do this for you. In Edit targeting, describe what you want in the chat beside the conditions, such as "Don't show this on account pages." Lia's change appears as an unsaved edit, so check it before you click Save. You can also ask Lia to create or change a saved targeting rule, and nothing changes until you click Publish. See How to set up targeting with Lia.

Popups and the Shopify checkout

Popups can't open on Shopify's checkout pages, because Shopify doesn't let apps run there. You don't need to exclude /checkout from your campaigns. Embedded forms can't be used on checkout either.

Stopping popups from competing on the same page

Only one popup can be open at a time. If more than one campaign matches a visitor on the same page, the first popup to trigger opens, and the others can open once it closes. This can also make a popup's view rate look low.

To make sure a specific popup is the one that shows on a page, exclude your other campaigns from that page with the methods above, or add Not in targeting rule or campaign to keep two campaigns from reaching the same visitors.

Waiting between popups

Don't trigger if another popup viewed in last... is set in each popup's Triggers. It makes the popup's triggers wait a set time after any other Alia popup was closed. New popups start with this on at 15 seconds. Lengthen it in a popup's triggers if visitors see two popups too close together. This setting only knows about Alia popups, not popups from other tools. Smart Trigger doesn't use it.

Hiding only the floating button on some pages

Campaign targeting applies to the whole popup, including its floating button. To hide or move only the floating button on certain pages, use a Static Prism. See Move the floating button on specific pages with Prism.

Hiding a popup based on a cookie

To hide a popup when a specific cookie is present, add a Custom code condition that checks for the cookie. Your code must return true for the visitor to match.

If you use Shopify's cookie banner, use the Cookie consent allowed targeting condition rather than custom code. See How to set up GDPR compliance with Alia.

If you use a different consent tool, a Custom code condition that checks your tool's consent cookie is an option. Either way, holding the popup until consent is answered means fewer popup views and signups. It's only worth doing if showing the popup needs consent where you sell, which is a question for your legal team.

Excluding in-app browser traffic

You can exclude visitors from in-app browsers, such as Instagram or Facebook, with UTM source is not or UTM medium is not conditions. This only works when those links carry UTM parameters. Visitors who arrive without UTM parameters still see the popup.

Test your changes

Visit the excluded pages in a private window to check that the popup doesn't appear.

Still have questions?

Start a chat from inside the Alia app, or use the chat in our Help Center.

Did this answer your question?