Popup Maker is about as simple and low-risk as integrations get. Its show/hide rules, frequency capping, and targeting logic run entirely as client-side JavaScript driven by cookies and localStorage in the visitor's own browser, so that logic keeps working unchanged once it's captured in a static build — no WordPress round trip involved for any visitor, ever. Open and conversion tracking work the same way, firing straight from the browser.
Fully Static
Popup display, show/hide rules, frequency-based suppression, targeting logic, and open/conversion tracking are all served from the static release exactly as built.
Nothing — every feature covered here is static or admin-only.
None needed — Popup Maker declares no public routes of its own. If a popup on this site embeds a real form, that form's own plugin (Contact Form 7, Gravity Forms, Mailchimp for WordPress, etc.) is what determines whether a bridge is needed — Popup Maker itself never processes submissions, no matter what's inside the popup.
No special setup — detected automatically once active.
If the static build is captured using a browser session that already has Popup Maker's display cookies set — for example, a crawler that previously dismissed a popup — the captured HTML could reflect that stale state rather than what a genuine first-time visitor sees. Building with a clean, cookie-free session avoids this. Beyond that, this classification is rule-derived from Popup Maker's known architecture, not from an automated end-to-end test.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp