Elementor popup not working: check the rules

A popup is attached to pages through its display conditions, and those conditions can name a single page, a set of pages or a whole template. A blog built on one template can ignore a popup built for another, even when the two look identical to the owner. The reader arriving from a search lands on an article, not on the home page where the popup was tested, so the popup never gets its chance. They read to the end, see nothing, and leave with no sign that an offer existed.

• Display conditions: the pages or templates the popup is attached to, compared with the article's address.
• The article's template, which can differ from the home page the popup was first built on.
• Timing: a delay or a scroll point that a short article may never reach before the reader leaves.
• Repeat rule: a setting that hides the popup after one view in the same browser.
• A cookie notice or a second popup that opens first and takes the place of the offer.

Display conditions are the first thing to check, and the easiest to skip. In Elementor they decide which pages the popup may open on, and a condition can name the entire site, a list of pages, or a template type. A popup created while you were editing the home page often keeps that narrow scope. Open an actual article address, not the one you test with, and confirm the popup is on the list of allowed places. A popup attached to nothing looks fine in the editor and never appears to anyone.

Article templates are the usual gap. A blog post, a case study and a resource page can each use their own template, and a rule that covers one may not cover the others. The check is simple: list the templates your search traffic lands on, then confirm the popup covers each one. Use a private window for the check, since the editor preview can show a popup that a public reader never gets.

A popup waits for its trigger. A delay counts time on the page, a scroll trigger waits for a set depth, and a click trigger waits for a link the reader presses. A long page gives a scroll trigger room to fire, but a short article can end before the reader reaches the depth you chose. The reader is done and leaves without ever getting close enough for the offer to matter. A delay set too short has the opposite problem: the offer opens before the reader has read anything, and they close it at once.

Test the timing with the page you actually publish. Scroll to the end of a real article on a phone, then on a laptop, and note the point where the popup should have appeared. If it opens on the laptop after the scroll and not on the phone, the difference is in a setting or a device rule. If it opens on neither, the threshold sits past the end of your articles, and no change to the copy will help.

Repeat rules stop a popup from showing again in the same browser after it has been seen or closed. That is right for readers, but it makes a popup look dead to whoever tests it. An owner who has already seen the offer in this browser sees nothing on the next article and assumes the popup is broken. Check the repeat rule by hand in one private window: open a first article, close the popup, then open a second one in the same window and see whether it stays hidden as the rule intends.

Once the rule is confirmed, send a simulated reader to the first article. It arrives the way a search reader does, reads down the page, and reports whether the offer opened at the trigger point. The run does not measure sign-ups from the popup, so the numbers that matter after it appears come from your own form reports and analytics.

Popups follow templates and addresses, so a redesigned blog, a new case-study template or a renamed resource section can leave the popup attached to nothing. Timing shifts too when an article gets longer or shorter. Rerun a real article on a phone and a laptop after any template or layout change, and check the popup before a campaign sends readers to that article.