← Back to modules

nexya popup

Popups composed section by section, opening at the right moment — and able to close the shop and the forms while they are live.

  • Composed like a page Text, paragraph, images, button, spacer and posts from the site: sections are stacked, sizes and colours set, and the preview follows on a computer and on a phone.
  • Opened at the right moment After a delay, on a click on an element, on scroll or when the visitor is about to leave — once, every visit or always, on the pages and devices you choose.
  • The shop closed, then reopened Stocktaking, holidays, closure: the popup closes buying and the chosen forms between two dates, and everything reopens on its own, to the minute.
0:47

Free

Section-built popups with a preview, opened on a delay, a click, a scroll or on exit, frequency, pages, devices and dates

Pro

WooCommerce shop and chosen forms closed while the popup is live, replacement message, reopened on their own at the end date

Get started

nexya popup in three steps

  1. Switch on nexya popup In the nexya hub: the Popup menu appears, open to editors.
  2. Compose the popup Text, image, button, posts: section by section, with the preview on desktop and phone.
  3. Choose when it opens After a delay, on a click, on scroll or on exit — on the pages and between the dates you want.

nexya popup is in the free extension, on as many sites as you want.

Download the free version View pricing

FAQ

Everything about nexya popup

In the Popup menu, add a popup, stack the sections (text, paragraph, images, button, spacer, posts), set the colours and position, then choose when it opens. The preview follows every setting.

Choose the “On click” trigger and give the class shown to any link or button on the site: it opens the popup.

No external service or subscription: the popup is rendered by the site, in its own colours. And with Pro, it can close the WooCommerce shop and the forms while it is live.

With Pro, a closing popup closes buying between two dates: products stay visible, adding to the basket waits, and everything reopens on its own at the end date.

No: it is rendered by the site, with no external library, and follows the frequency you choose so it does not come back on every page.

The suite

Other modules

nexya translate

The site in several languages: every content with its versions, an address per language, and the site’s texts translated in one place.

nexya custom fields

Fields of your own, kept in their own tables — and read in a single query per page.

nexya aris

Audience figures, measured by the site itself — no Google, no Matomo, no IP address kept.

nexya mailya

Newsletters written on the WordPress site, with your posts in them — sent in the background, at the pace your server can hold.

nexya media

Folders to sort the media library, and thumbnail regeneration in the background, in batches, carrying on when you close the tab — and telling you when it is finished

nexya hub

The panel that gathers every nexya plugin. A module you switch on, a module you switch off — and nothing running on the WordPress site while it is off

nexya dashboard

The WordPress admin as the client sees it: menus cut down to what is useful, a tidy admin bar, and the dashboard in your own colours right through to the login page

nexya shortcuts

Duplicate, reorder, add — three gestures placed on the WordPress content lists, so you stop doing them by hand

nexya roles

WordPress capabilities filed under the plugin that creates them, readable at last. And the menu cut down to what the person in front of it actually has to do

nexya activities

Who changed what on the WordPress site, and when. Down to the ACF fields, with the value before and the value after — and the button to put it back

nexya cookie

Cookie consent, and the blocking that goes with it. Nothing runs before the visitor agrees — not the scripts, not the embedded videos, not the remote fonts

nexya seo

What the WordPress site says about itself to search engines — and what it shows when someone pastes its address somewhere. Written once, applied everywhere, checked before publishing

nexya mail

The WordPress site’s emails actually go out — and you know which ones did not, with the exact reason given by the SMTP server

nexya redirects

The 404 errors picked up as visits happen, and the 301 redirect suggested before anyone goes looking for it. With the number of hits, so you know which ones count

nexya security

The HTTP security headers set without breaking the site, the watch on vulnerabilities in the WordPress plugins installed, and the eye on what moves in the files

nexya maintenance

The operations you carry out on the WordPress site rather than in it: closing it for an intervention, slimming its database down, taking a copy

nexya cache

Each page kept as a file and handed to the next visitor before WordPress loads — then thrown away as soon as something changes it.