Countdown Timer

Give the offer an end, and the shopper a reason to decide today

Days, hours, minutes and seconds down to a deadline you type in your store's time zone — counting correctly for a shopper in Warsaw, in Los Angeles, or on a laptop whose clock is wrong.

Urgency with a real date behind it

A deadline a shopper can see beats "limited time only", and it beats it most in the last day. This is the element that turns a promotion into a decision.

Right in every time zone

You type "1 October, 12:00" in your store's own clock and the moment is stored in universal time. Nobody in another country sees a timer that is four hours out.

You decide what happens at zero

Hide the timer, swap it for a message, or send the visitor to another page. Set it once, when you build the campaign, rather than remembering to take the banner down on Sunday night.

Use cases

Where shops put it

The end of a promotion

"Sale ends in 2 days 06:14:22" at the top of a campaign page, set to show a message when it runs out — so the page that stays indexed does not lie about an offer that has closed.

A launch or a pre-order opening

Counting down to the moment the product goes on sale, with the timer redirecting to the product page the second it does.

The delivery cut-off before Christmas

"Order within 09:12:44 for delivery before the 24th" on the basket page or in a category description. The one deadline shoppers genuinely want to know.

What you control

Every field in the form, in plain words

Deadline
A date and a time, typed in the store's time zone and stored in universal time.
Which units to show
Days, hours, minutes, seconds, in any combination.
Your own labels
For the four units, in your own language.
Digit size
(S, M or L), digit colour and tile background colour.
What happens at zero
Hide the timer, show a message in rich text, or redirect to a URL, a CMS page, a category or a product.
Appearance
Simple (digits alone), Boxed (tiles) or Flip (tiles that turn as they change).
Alignment, margins, padding, border and CSS classes
From the native Advanced tab.

Shown in the demo store

Native and honest

Your content is written in Magento's own format

This is the one element whose content cannot be a finished state — a moment is never over with. So the page stores a sentence instead, and the script swaps it for the digits.

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

What happens when JavaScript is off?
Can I count down to a specific second?
Will the redirect throw me out of the editor?
Is Flip a real flap clock?

Conversion & trust

More in Conversion & trust

Auto Popup

The same window with no trigger: it opens itself after a delay you set.

Comparison Table

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

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.