Newsletter Signup
Ask for the email address where the reason to give it is
Your store's own newsletter signup, placed in the page as a bar, a card or a band across the page, with a line that says why to subscribe. The visitor gets Magento's answer under the form, without leaving the page.

Use cases
Where shops put it
The first-order discount under a category
A bar at the foot of a category page, "Get 10% off your first order" on the left and the field on the right, one line on a desktop and stacked on a phone.
A signup card next to the story
A card with a picture in a column beside an article or a lookbook, with a consent box that links to your privacy policy.
The band above the footer of a campaign page
A full-width band over a campaign photograph, with larger controls, white words on a tinted overlay, and a message of your own after subscribing.
- Three appearances
- A bar in one line, a card with a picture, or a band across the page.
- The words
- A heading with its level, an incentive in rich text, the field label, the button label and an optional line of small print.
- A consent box
- In your own words, with a link to your privacy policy. The form will not send until it is ticked.
- After subscribing
- A success message of your own, or Magento's words.
- The look
- Square, rounded or pill-shaped field and button, two sizes, an accent colour for the button and the tick box, the text colour and the alignment.
- The background
- A colour, a picture and a tint over it.
Shown in the demo store

The bar: an address typed, Subscribe pressed, and Magento's thanks under the emptied field, with no page load.

The bar: the offer on the left, the field and the button on the right.

Two cards, one with a picture and a consent box, one centred.

The answers in place: Magento's thanks, and a consent box nobody ticked.

The bar and the band on a phone, the button under the field.
Native and honest
Your content is written in Magento's own format
The page stores a real form that sends the address to your store's own newsletter subscription, and to nothing else. The element has no backend, no list and no table of its own, and it has no field that could point the form anywhere else. Without the module it is still a plain form that subscribes the visitor.
Where the promise stops: if your store switches on Google reCAPTCHA for the newsletter, Magento refuses this form and the element subscribes nobody; keep the footer form in that case. Without JavaScript Magento refuses it too, for a missing form key, exactly as it refuses its own footer form. The consent tick is not recorded anywhere: for a record of consent, use Magento's own double opt-in.
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_PageBuildermodule 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
Conversion & trust
More in Conversion & trust
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.