Elementor Popups

A popup that will not appear is almost always a conditions or trigger problem, not a broken popup. Elementor's popup templates are a Pro template type governed by three independent settings groups, and a failure in any one of them looks identical from the front end: nothing shows up — a form that reports success but never sends hides its own failure the same way.

The three layers, and how they interact

Display Conditions decide where the popup is eligible to appear at all — a specific page, an entire post type, the whole site, or a mix of includes and excludes. This works the same way as conditions on theme templates.

Triggers decide when the popup fires during a visit that already matches its conditions: on page load, after a delay, on click, on scroll to a position or element, after a period of inactivity, or on exit intent.

Advanced Rules decide whether to suppress the popup even when conditions and a trigger both fire — showing it once per session, once ever, only to new visitors, or only on certain devices.

All three must line up. A popup with perfect conditions and a working trigger still will not show if an advanced rule has already marked it as seen. A popup with no frequency restriction still will not show off the pages its conditions cover.

Why the popup does not appear

Caching deserves particular attention: clear the page and object cache after adding or editing a popup, following how to clear WordPress cache, and if changes still do not reflect, work through Elementor changes not showing before assuming the popup itself is broken.

Closing behaviour and cookies

A popup can close through its X icon, a click on the overlay, or the Escape key — each toggled independently in the popup's settings. Closing behaviour interacts with Advanced Rules: a "do not show again" option writes a cookie with a set duration, and once that cookie exists in your browser, the popup will not reappear for you until it expires or you clear cookies for the site. This is the single most common source of "it worked once and now it's gone" reports during your own testing, and it is not a bug — test in a private window to see the popup as a first-time visitor would.

Performance cost

A popup adds its own markup, CSS and JavaScript to every page its conditions cover, whether or not a visitor ever triggers it. Exit-intent and scroll listeners run on every eligible page too. A site running several popups across broad conditions accumulates real weight this way, and it compounds with everything else discussed in how to speed up Elementor. Scope conditions as narrowly as the goal allows, and avoid stacking multiple popups on the same pages.

Accessibility

Focus should move into the popup when it opens and return to the triggering element when it closes, and Escape should close it — check both, since a popup that traps a mouse user visually but not a keyboard user leaves keyboard visitors stuck behind an overlay they cannot dismiss. Give the close control enough contrast and size to find without hunting, and avoid firing a popup within the first few seconds of a page load — an immediate interruption reads as hostile to visitors and to accessibility guidance alike.

Avoiding stacked popups

When a site accumulates more than one popup over time, it is easy to end up with two eligible on the same page — a newsletter prompt on page load and an exit-intent offer, say. If both conditions match, both can trigger, layering overlays and confusing the close behaviour of each — the same stacking-order competition happens between a sticky header and other fixed elements like cookie-consent banners or chat widgets. Keep conditions for each popup mutually exclusive where possible, or add an advanced rule that suppresses one once the other has already shown in the same session.

Common mistakes

• Testing while logged in with a cache or preview showing. Log out and load the actual page.
• Leaving the popup as a draft. Publishing the template is a separate step from saving it.
• Setting conditions too narrow to test. A condition scoped to one specific page is easy to test on the wrong URL.
• Assuming exit intent works on mobile. It generally does not; use a different trigger for mobile traffic.
• Never clearing your own test cookie. You will keep seeing "nothing happens" while every other visitor sees it fine.
• Running two popups with overlapping conditions. They can fire together and stack.

Verify

Open the page in a private browser window, logged out, with caching cleared. Confirm the popup fires on the trigger you configured, closes with each method you enabled, and does not reappear inappropriately on a second visit if a frequency rule is set. Then check the same page on a phone, since triggers like exit intent behave differently there.