Auto Popup

Make the offer once, to the people who have not seen it yet

A window that opens by itself after a delay you set, as often as you allow — and stops showing itself to a visitor who has already had it. It holds real Page Builder content, and it sets no cookie of any kind.

A campaign that does not wear out its welcome

Once per session, or once every so many days. The visitor who has already seen the offer carries on shopping instead of closing the same window again.

Nothing to declare in a cookie policy

No cookie is set, no visitor identifier is created and nothing is sent anywhere. The fact that a window has been shown is a flag in the visitor's own browser, under a name you chose.

Careful with phones by default

A window covering the content of a phone screen is a ranking problem, so the default is not to show one. Switching it on is a decision you make, not one you inherit.

Use cases

Where shops put it

A discount code for a first order

Three seconds into the visit, once per session, with the code and a button that sends the shopper into the catalogue rather than away from it.

A newsletter sign-up that is not in the footer

The form in a window, shown once every seven days, so the shopper who ignored it last week is not asked again today.

Dispatch deadlines before a holiday

"Order by the 18th for delivery before Christmas", on every page view for the fortnight it matters, and then one change of setting to stop.

What you control

Every field in the form, in plain words

The delay
From nothing to two minutes, counted from the moment the page is ready.
How often
Every page view, once per session, or once every so many days.
Whether it may appear on narrow screens
Which is off until you say otherwise.
An identifier of your own
Which names the memory — change it and the campaign starts again for everyone.
A window title
Optional, and it is what names the window for a screen reader.
Window width
In four steps, and whether pressing the dimmed background closes it.
Anything inside
Text, headings, images, buttons, dividers, video, banners, sliders, maps, product lists and every other Wrizu element.

Shown in the demo store

Native and honest

Your content is written in Magento's own format

The window's content is stored as ordinary content types in the place you put them, so with the module switched off it reads as a plain section of the page. The memory is functional and nothing else: a flag or a timestamp in the visitor's own browser, written when the window opens rather than when it is closed.

Two things we will not pretend about. The memory belongs to the browser, not to a person — the same visitor on a second device, or in a private window, sees the window again, and the only way around that would be to identify people, which this element does not do. And a window that opens by itself takes the visitor's focus; that is what the pattern is, which is why the defaults here are the cautious ones.

Every element saves itself the way native Page Builder saves its own: a plain <div data-content-type="wrizu_…"> with its settings in data-* attributes, stored with the page. There is no proprietary database table, no shortcode, no second editor and nothing that has to be converted later.

That has a practical consequence. Disable the module and the storefront keeps serving those pages: headings, copy, images, links and buttons stay visible and clickable, and the styling you set per element — alignment, colours, spacing — stays with them, because it lives in a <style> block stored with the page rather than in our stylesheets. What you lose is what our CSS draws: the layouts, the borders and shadows, the button variants and the bundled icons.

One honest warning

With the module switched off, do not open and save a page that contains Wrizu elements — Page Builder flattens any page holding a content type it does not know into a single HTML Code block, and that save cannot be undone. It behaves that way with every unknown content type, not only with ours, and the storefront is unaffected either way; the rule is simply to leave those pages alone until the module is back on.

Works with any Luma-based theme

The elements are built on the same front-end stack the native Page Builder uses: jQuery and the libraries Page Builder already loads. They target Luma-based themes — Magento Blank, Luma, and the custom themes shops build on either of them.

Buttons use Luma's own button mixins, so a Wrizu button looks like a button from your theme rather than like a button from a plug-in. All of the module's CSS is scoped to [data-content-type^="wrizu_"], so it styles our elements and nothing else in your theme.

Requirements

  • Magento Open Source or Adobe Commerce 2.4.6 or newer, with the Magento_PageBuilder module enabled
  • PHP 8.1 to 8.5 — whichever your Magento version supports
  • No other extension, no external icon font, no CDN dependency

Questions about this element

Does it set a cookie?
Can I show the same campaign again?
What happens with several of them on one page?
Is there an exit-intent trigger?

Conversion & trust

More in Conversion & trust

Comparison Table

Two to five things side by side, a row per feature, one column recommended.

Countdown Timer

Days, hours, minutes and seconds down to a deadline you set.

Coupon Code

A discount code on a ticket, in a line or on a banner, with a button that copies it.

CTA Box

A call-to-action band with a heading, a subheading and up to two buttons.

CTA Popup

A button or a text link that opens a window holding real Page Builder content.

Logo Cloud

A row of brand, partner or payment marks, as a grid or a carousel — or a row of social icons.

Newsletter Signup

Your store's own newsletter subscription as a bar, a card or a full-width band.

Pricing Table

Columns of plans with feature lists and a call to action in each.

Star Rating

A score in stars — to a tenth of a star, out of five or ten — with the number and a caption.

Testimonials Slider

A carousel of customer quotations with photographs and star ratings.

Thirty-five conversion elements for the Page Builder you already have

Wrizu Page Builder Extensions adds them to the native Magento 2 Page Builder — no second editor, no proprietary format, no content held hostage.