Elementor popup conditions and triggers control two different parts of popup delivery. Conditions define where a popup is allowed to appear, while triggers define the user action that opens it. Advanced Rules add another layer, helping restrict delivery by visits, sessions, referring URLs, device type, logged-in status or display frequency.
This distinction matters when a popup appears on the wrong page, repeats too often or fails to open from a button. A reliable configuration starts with page scope, continues with the intended behavior and ends with additional restrictions and testing. Elementor documents these controls, but exact labels and behavior may vary with Elementor product versions, caching configurations, the active theme and other plugins.
What Elementor Popup Conditions, Triggers and Advanced Rules Control
Elementor separates popup configuration into three practical layers. Conditions answer the question “where?” They determine whether a popup may appear across the entire site, on the front page, within archives, in categories or tags, or on selected pages.
Triggers answer “when?” They describe the user action that opens the popup, such as loading a page, scrolling, clicking, becoming inactive or showing behavior associated with leaving the page. A trigger does not define the page scope by itself.
Advanced Rules answer additional questions about delivery. They can add requirements based on page views, sessions, display count, referring URL, arrival source, logged-in status or device type. The practical sequence is therefore straightforward:
- Define where the popup is allowed to appear.
- Choose the user action that should activate it.
- Add frequency, device, visitor or referral restrictions only when they support the message.
The “Where,” “When” and “Who” of Popup Delivery
Think of conditions as location settings, triggers as behavior settings and Advanced Rules as delivery requirements. This framework makes troubleshooting easier. If the popup is available on the wrong page, inspect conditions. If it opens at an unsuitable moment, inspect triggers. If it does not show for a particular visitor or appears repeatedly, inspect Advanced Rules and the browser state.
Set Popup Conditions: Choose Where the Message Appears
Begin by identifying the actual location for the message. Elementor documents conditions for the entire site, the front page, archives, categories, tags and selected pages. Select the scope that matches the content rather than assuming that a trigger will control visibility everywhere.
A site-wide condition may be relevant when the message belongs across the website. A front-page condition limits it to the front page, while archive, category and tag conditions relate the popup to those content contexts. Selected-page targeting is useful when the message belongs only to specific pages.
For a manually opened popup, the condition still matters. The selected conditions must include the page containing the button, link, form or other element that visitors use to open the popup. A correctly assigned selector cannot compensate for a popup whose display conditions exclude the current page.
Match Conditions to the Popup’s Intended Location
Before configuring behavior, write down where the message should be available. Then verify that the chosen conditions cover those pages or templates. Starting with the narrowest practical scope makes it easier to test whether the popup is appearing in the intended context. Expand the scope only when the message genuinely belongs in additional locations.
Choose the Right Trigger for the User Action
The appropriate Elementor popup trigger depends on the purpose of the message. Elementor documents several behavior-based options, but does not establish one universally correct trigger for every website. Choose the setting that corresponds to the action you want to address, then test it on the devices and pages where it will be used.
On Page Load opens the popup after the page loads and allows a delay to be configured. This is suitable when the message should follow the initial page-load event rather than require scrolling or clicking.
On Scroll responds after a visitor reaches a configured scroll threshold. Scroll direction can also be used. On Scroll To Element connects activation with reaching a specific element, which can be more closely tied to a particular part of the page.
On Click is appropriate when the visitor intentionally selects a button, link or other control. For more deliberate activation, Elementor also provides manual workflows through dynamic actions and custom selectors, described below.
After Inactivity responds when a visitor stops interacting for a configured period. It is behavior-based rather than tied to a particular page location. On Page Exit Intent responds when Elementor detects mouse behavior indicating an attempt to leave. This should not be the only route to information that visitors must reliably receive; provide a usable non-popup path as well.
Avoid combining several automatic triggers without testing. Multiple conditions for activation can create repetitive or disruptive delivery. Check the behavior on desktop and mobile, since documented trigger behavior does not establish identical results across every device or site configuration.
Match the Trigger to the Message’s Purpose
Use delayed page load for an initial message, scrolling or scroll-to-element for content-related engagement, inactivity for visitors who stop interacting and exit intent for behavior indicating departure. The choice should follow the message’s purpose, not a general assumption that one trigger is always preferable.
Control Frequency, Devices and Logged-In Users
Advanced Rules help control how often and for whom an automatic popup appears. Page-view and session requirements can make delivery depend on prior visits or sessions. Other rules can use a referring URL, arrival source, logged-in status or device type.
To limit repetition, configure Show up to X times. Elementor documents two counting modes: On Open and On Close. The choice determines when a display is counted according to the selected configuration. This setting is useful when a message should not be shown indefinitely to the same visitor.
Device targeting can distinguish desktop, tablet and mobile audiences when the message requires device-specific delivery. Logged-in-user controls can also be used when the message should be hidden from logged-in visitors. Elementor documents a limitation: the hide-for-logged-in-users rule may not function correctly on cached websites. Test both logged-in and logged-out states with the site’s caching layer.
Understand Display Counts and Browser State
Elementor documents that popup display-count data is stored in the browser’s Local Storage until it is deleted. Consequently, a frequency limit may continue to affect one browser during testing even after the popup configuration changes. When repeating a test, use the relevant browser state and clear Local Storage when necessary.
Do not assume that these automatic frequency controls govern every manually opened popup. Elementor states that when a popup is triggered through a custom selector, its normal Triggers and Advanced Rules are disregarded for that manual-trigger workflow.
Open a Popup from a Button, Link, Form or Custom Selector
Manual popup triggering is a separate workflow for deliberate, user-initiated opening. For an Elementor button or link, use a Dynamic Action with Popup and choose Open Popup. This connects the element’s action directly to the popup rather than waiting for page load, scrolling or inactivity.
For a form, use Actions After Submit and add Open Popup. This creates a workflow in which the popup opens after the form action, subject to the configuration available for that form.
For non-standard elements, Elementor documents the Open By Selector field. Assign a matching CSS class, CSS ID, data-element or anchor selector to the clickable element, then enter the corresponding selector in the popup settings. Elementor’s documented anchor pattern is a[href="#link-popup"]. Use straight quotation marks in selector syntax.
The popup’s display conditions must include the page where the triggering element exists. If a menu item, custom element or script is intended to open the popup on a selected page, verify both the selector match and the condition scope. Compatibility with custom scripts, third-party menu systems or non-Elementor widgets may require site-specific testing.
Manual Trigger Configuration Paths
- Dynamic actions: connect an Elementor button or link to the Popup action and select Open Popup.
- Form actions: add Open Popup in Actions After Submit.
- Custom selectors: match a class, CSS ID, data attribute or anchor selector with the popup’s Open By Selector field.
When using a custom selector, do not rely on automatic Triggers or Advanced Rules to control the manual opening. Elementor states that those settings are disregarded in this workflow.
Troubleshoot and Test a Popup Before Publishing
If a popup is missing, check the configuration in a fixed order. Start with display conditions and confirm that the intended page, archive or template is included. Then verify the selected trigger and reproduce the required action: load the page, reach the scroll threshold, stop interacting, move toward exit or click the assigned element.
Next, review Advanced Rules, including page views, sessions, display limits, device targeting and logged-in status. Check the Avoid Multiple Popups setting when more than one popup may be active. For logged-in exclusions, test the site’s caching behavior because Elementor documents a limitation in cached environments.
For manual triggering, inspect the selector assignment, syntax and matching element. Confirm that the popup conditions include the location of that element. If a frequency test behaves unexpectedly, check browser Local Storage and repeat the test in the relevant clean state.
A Repeatable Verification Order
- Verify page conditions and confirm the intended location.
- Verify the trigger or manual selector and reproduce the required action.
- Review Advanced Rules, display limits, device targeting and login state.
- Check caching and browser storage when the result differs from expectations.
- Test desktop, tablet and mobile interaction before publishing.
Also verify that the popup has a visible and usable close control. Test keyboard and mobile interaction, along with overlay, ESC-key, scrolling and automatic-close behavior according to the content and accessibility requirements of the site. Important information should remain available through a usable non-popup path.
Elementor popup conditions control location, triggers control the user action and Advanced Rules add requirements for frequency, visitors, referrals or devices. Manual selectors follow a separate workflow, so their behavior should be tested independently rather than assumed to follow automatic timing or frequency settings. A careful setup therefore begins with the narrowest suitable page scope, matches the trigger to the message’s purpose and verifies browser, device, login and caching states. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.