Magento 2 Banner Slider Extension

Business Value

Turn any page of your store into a promotion slot you can schedule, target, and measure.

• Opportunity: A promo banner is the strip, box, or pop-up that announces an offer: free shipping today, ten percent off a second item, a brand you are clearing out. It is the cheapest way to push shoppers toward whatever you want to sell next.
• Problem: The offer changes every week, but the banner does not. Someone has to open each page, edit it, remember to take the promotion down afterwards, and then guess whether it did anything at all. Magento's own tools keep it that way: Page Builder, the drag-and-drop page editor, puts a banner inside one page, and Adobe Commerce adds Dynamic Blocks on top for audience targeting. Both of them edit page content, so the banner belongs to the page. Neither starts and stops a campaign on a schedule, and neither tells you whether anyone clicked.
• Solution: Promo Banners treats a banner as a campaign instead of page content. Each banner exists on its own, decides which pages and which shoppers it appears for, runs between the dates you set, and reports its own impressions and clicks in real time.

Promote products and services wherever they work best

You work with two things. A placeholder is a slot on the storefront: you decide which page it sits on and how it behaves. A banner is what appears in that slot. One placeholder can hold several banners, and each banner carries its own schedule and its own rules about who gets to see it.

From there, the extension works in five ways:

• Place a banner anywhere on any page of your store
• Show it only to the customer groups, categories, products, or cart contents you pick
• Run it between the dates and times you set
• Choose how it appears: rotator, pop-up, lightbox, or slider
• Track impressions and clicks for every banner, in real time

Choose how each banner appears, one setting per placeholder

Rotator shows one banner at a time, picked at random on every page load. Refresh the page and a different banner appears. Use it when you have several offers of equal weight and simply want them shared out.

Pop-up opens on top of the page once it loads. You choose the corner it appears in, the delay before it shows, and how many hours pass before it returns. Set it to appear only once and it never comes back for that shopper.

Lightbox covers the whole page behind a dimmed mask. You control the mask color, the close button text, the delay, and the same re-appear interval.

Slider also holds several banners, but where a rotator swaps them only when the page reloads, a slider cycles them in front of the same visitor. Turn on autoplay and set the interval between slides, loop back to the first one, show previous and next buttons with your own labels, and add the row of dots underneath. Slides load only as they are needed, so a slider further down the page costs nothing until someone scrolls to it.

If none of the four fits, add a fifth. Any banner template your developer drops into the theme shows up in the Display mode list on its own, without hooking into the extension at all. The user manual walks through a slider setup step by step.

Match the offer to the shopper instead of showing it to everyone

Every banner carries its own set of conditions, and they go deeper than a page match. Target by page (its type, or its address), by category, by product attributes, and by what is already in the cart. A banner can appear only for shoppers who have one item in their basket, or only on products from a single brand, or only on URLs that contain a search term.

On top of conditions, each banner is limited to the store views and customer groups you select: store views are the separate storefronts you run, usually one per country or language, and customer groups are the buyer types you have set up, such as retail and wholesale. That is how one placeholder serves a different message per region, per language, and per price group, and how a wholesale offer stays invisible to retail shoppers.

Cart conditions are the ones worth planning around: they pair naturally with a cart price rule, Magento's own discount mechanism, so the banner that advertises the discount appears exactly when the rule is about to apply.

Write it once in the Magento editor and let the numbers fill themselves in

A banner can be a graphic, a line of text, or both in one block. You build it in the default Magento content editor, and if you would rather write the markup yourself, the Show / Hide Editor button drops you straight into HTML and CSS.

Content can also be dynamic. Write a placeholder for a number into the text and it fills itself in per shopper. Type "You are {{var freeShippingLeft}} away from free delivery" once, and a shopper who is $12 short reads exactly that, while the next one reads their own figure. The cart subtotal and the free shipping threshold work the same way, as does every standard Magento variable.

Not just the home page, the catalog, and the cart

You choose where each placeholder sits. Pick the page from the Display on list, then the spot on it: header, main content, sidebar, footer, and so on. Magento 2.4 comes with 95 page types and every one of them is on that list, each offering several spots of its own. Modules you install add their own page types, so the list grows with your store.

That includes places most stores never use. A banner can greet customers before they even sign in, because the login form is a page type like any other. So are the sign-out page and the password recovery form. So are contact, about us, and delivery pages, alongside the usual home page, catalog, and shopping cart.

If the spot you need is not on the list, it can be defined by hand: your developer points the placeholder at an exact position in the page layout and it renders there. Each placeholder also takes its own CSS, which is usually enough to fit a banner into a custom theme.

Different regions often need different slots as well. Placeholders respect store views, so a store running on geolocation-based store switching can carry a separate set of banners per country without duplicating campaigns.

See it running in the frontend demo.

Start and finish a promo campaign without being at the keyboard

Set Active from and Active to for every banner, down to the hour. A flash sale that opens at 09:00 and closes at 23:00 does that on its own, and nobody has to remember to switch the banner off afterwards.

Because the schedule belongs to the banner rather than to the page, a campaign can be prepared weeks ahead and left alone. Placeholders keep serving whichever banners are in season at that moment.

Decide what wins when two campaigns claim the same slot

Give each banner a priority. When several banners match the same conditions at the same time, the highest priority is displayed first, so a seasonal campaign can override an evergreen one for a week and hand the slot back afterwards.

Impressions and clicks per banner, not guesses

The banner grid shows how many unique visitors saw each banner and how many of them clicked, with the click-through rate alongside. Numbers update in real time, with no cron job to configure, so a change made this morning can be judged this afternoon.

Two placements for the same offer stop being a matter of opinion: run each for a week and compare the click-through rates in the grid. Collection can be switched off entirely if you would rather not store the data.

Hyvä, headless, multi-language, and multi-admin stores

The rest of this section is for whoever looks after your store's code. If your storefront is a standard Magento theme and one person runs the admin, everything above already covers you.

Hyvä. The extension works on Hyvä storefronts. If your banners use a schedule or cart price rule conditions, install the free companion package that ships with the module: it swaps the default loader for a fetch-based one so those placeholders render. Without it they stay empty on Hyvä.

Headless. A GraphQL API returns placeholders with their banners in the context of the current page, product, category, or cart, and two mutations report impressions and clicks back, so a PWA storefront keeps the same analytics as a Luma one. A REST API covers banners and placeholders for scripted or scheduled updates. Both are documented in the user manual.

Languages. The storefront and admin interface ship translated into 16 languages, so a multi-language store does not need a glossary to run campaigns.

Permissions. Banners, placeholders, and the extension settings are three separate admin role resources. A marketing team can create and edit banners while configuration stays with whoever owns the store.

Page speed. Banners are built to stay out of the way of Core Web Vitals. Placeholders that load over AJAX are told not to fill your cache with single-use entries, and a placeholder above the fold can be given a fixed height so it does not shift the layout while it loads.