Skip to content

Black Friday 50% off your first year on all premium plugins and the Suite.

See the deals

Caching reference

Which Divi Smart Popup rules run in the browser, which run while the page is built, and how to set up page caching and script optimisation.

2 min read · Updated 16 November 2026

This is the reference. For the full guide, with the page-speed profile and a five-minute cache check, read Divi popups and page caching: what to check.

Where each rule is decided

Device, frequency and trigger rules run in the visitor’s browser. They are unaffected by any cache, which is why a popup still respects a frequency cap on a fully cached page.

Location, logged-in state, user role and the schedule are decided while the page is being built, and only popups whose rules match are printed into it.

What that means for a page cache

A popup targeted by page, post type, archive, author or term caches cleanly: every visitor to that URL should see the same set.

A popup targeted at a logged-in state or a role is different. If your cache serves one copy of a page to logged-in and logged-out visitors alike, the copy that was stored decides what they get. Configure the cache the way you already do for any other logged-in content — commonly by not caching for logged-in users.

A schedule is decided when the page is built too. Since 2.1.4 the browser checks the end again, so an old cached copy never shows a campaign after it ends, and Divi Smart Popup asks common page caches (TurboCache, WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SiteGround Optimizer, Cache Enabler, Breeze, Hummingbird, Nginx Helper and WP Fastest Cache) to clear at the start and end time, using WP-Cron. It does the same when a live popup is switched on, edited, switched off or deleted. A server, host or CDN cache it does not know still needs clearing by hand, or a developer can hook the d5pe_purge_page_cache action. WP-Cron runs on the next visit after the time, so on a quiet site the start can be a few minutes late.

Previews and test mode send no-cache headers, so a shared cache never keeps them.

Script combining

Divi Smart Popup does not add any marker that tells optimisation plugins to leave its script alone. If a combine, defer or delay step breaks a popup, exclude the plugin’s front-end script (divi5-popup-engine/assets/js/popup.js) by hand in that tool.

We have not tested Divi Smart Popup against optimisation plugins, so we cannot tell you which ones need it.

Did this answer the question? No — open a support request