Spletna potisna obvestila

Kako uporabljati spletna potisna obvestila v spletni trgovini

Posted on July 18, 2026 by

Spletna potisna obvestila so kratka sporočila z gumbom, ki jih vaša trgovina pošlje neposredno v brskalnik obiskovalca — na namizju ali na Androidu, na iPhonu pa le, če je vašo stran dodal na začetni zaslon. Obiskovalec se prijavi z enim klikom na pozivu brskalnika; njegovega e-naslova sploh ne potrebujete. Da jih boste v spletni trgovini uporabljali dobro, potisna obvestila obravnavajte kot kanal za obnovitev in opozorila, ne kot kanal za obveščanje na pamet: najprej vklopite avtomatizacije, ki se sprožijo glede na vedenje (opuščena košarica, znižanje cene, ponovna zaloga), ročne kampanje pošiljajte redko in le, kadar so resnično nujne, vse skupaj pa merite po naročilih, ne po klikih. Ta vodnik pokrije celotno nastavitev po vrsti — kako kanal deluje, komu se sploh splača, kaj avtomatizirati najprej in kako ugotoviti, ali prinaša denar.

Težava, ki jo potisna obvestila rešujejo: plačani obiskovalci, ki ne pustijo nič za sabo

Za promet plačujete. Večina obiskovalcev si ogleda nekaj izdelkov in odide, edino orodje, s katerim te ljudi lahko pripeljete nazaj, pa je remarketing — kar pomeni, da Meti ali Googlu drugič plačate za obiskovalca, ki ste ga enkrat že kupili.

E-pošta del tega reši, a le za tisti delček obiskovalcev, ki so pripravljeni svoj naslov vtipkati v pojavno okno. Vsi drugi odidejo neznani. Prav to vrzel zapolnijo spletna potisna obvestila: prijava zahteva en klik na izvornem pozivu brskalnika, brez obrazca, brez tipkanja, brez potrebe po e-poštnem predalu. Obiskovalec, ki vam e-naslova ne bi dal nikoli, bo poziv za obvestila pogosto sprejel, ker je vprašanje veliko manjše.

Če še tehtate, ali ta kanel sploh zasluži mesto ob e-pošti, je primerjava razložena v e-pošta ali spletna potisna obvestila za spletne trgovine. Na kratko: potisna obvestila si mesto prislužijo s tem, da dosežejo ljudi, ki jih e-pošta ne more, najbolje pa delujejo ob e-pošti, ne namesto nje.

Zakaj “pa jih remarketiraj” neha delovati

Običajen odgovor na neznani promet so remarketing oglasi in ti res delujejo — po ceni, ki se ves čas premika. Oglasne platforme vam zaračunajo prav vsakič, ko istega človeka znova dosežete, in to za vekomaj. Omejitve pri sledenju so te občinstva pomanjšale in zabrisale, vaši konkurenti pa se potegujejo za iste pare oči.

Naročnik na potisna obvestila vas po prijavi ne stane nič na sporočilo. Ko nekdo sprejme vaš poziv, ga lahko neposredno dosegate, dokler naročnina živi. To je enaka logika, kot naredi e-poštni seznam dragocen, uporabljena na obiskovalcih, ki vam e-naslova nikoli niso dali — lasten kanal opravlja delo, ki ga zdaj najemate pri oglasnih platformah.

Preden se preveč razveselite, en pošten pridržek: seznam naročnikov na potisna obvestila je bolj krhek od e-poštnega. Naročnina je vezana na en brskalnik na eni napravi. Če obiskovalec izbriše podatke strani, zamenja telefon ali znova namesti brskalnik, naročnina tiho umre — brez dogodka odjave, brez obvestila vam. Vaš seznam se osipa tako, kot vam nadzorna plošča ne bo pokazala, in prav zato potisna obvestila najbolje delujejo kot hiter kanal za bližnjo prihodnost, ne kot sredstvo za dolgoročen odnos.

Kje denar dejansko odteka

Naredite hitro ilustrativno računico na svojih številkah. Recimo, da ima vaša trgovina 20.000 obiskovalcev na mesec in da vaše e-poštno pojavno okno pretvori 2 % teh — 400 novih naslovov. Preostalih 19.600 ljudi je izgubljenih, razen če plačate za njihov remarketing.

Zdaj pa recimo, da dobro postavljen poziv za potisna obvestila pripravi vsaj skromen delež preostalih obiskovalcev do prijave. Vsak od njih je oseba, ki jo lahko zdaj brezplačno prikličete nazaj v trgovino — nekdo, ki je opustil košarico, si je trikrat ogledal izdelek ali čakal, da se razprodana številka vrne na zalogo. To so trenutki največje nakupne namere v vaši trgovini in za obiskovalce brez e-pošte trenutno ne prinesejo nobenega nadaljnjega stika. To je tista puščanje. (Zgornje številke so ilustrativne — vstavite svoj promet in svoje stopnje prijav.)

Nastavitev spletnih potisnih obvestil, korak za korakom

Naredite jih po vrsti. Prva in drugi korak sta infrastruktura; denar je v tretjem in četrtem koraku.

1. Izberite orodje, ki potisna obvestila poveže z vedenjem v trgovini. Samostojni pripomoček za potisna obvestila zna pošiljati sporočila, ne vidi pa košaric, naročil ali ogledov izdelkov. Potisna obvestila želite imeti znotraj iste platforme kot svojo e-poštno avtomatizacijo, da en sistem sledi vedenju in sproža vse kanale. (V svojih trgovinah za to uporabljam Omnisend — več o tem spodaj.)

2. Nastavite poziv za prijavo — previdno. Ta korak ima past: če obiskovalec na izvornem pozivu brskalnika klikne “Blokiraj”, ga brskalnik ne bo več vprašal. Ta odgovor je praktično dokončen, razen če se obiskovalec sam poglobi v nastavitve strani. Zato izvornega poziva ne sprožite v trenutku, ko nekdo pride na stran. Zamaknite ga ali uporabite dvostopenjski poziv, kjer mehko vprašanje pride pred pravim. Celoten priročnik je v kako pridobiti naročnike na spletna potisna obvestila — to uredite, preden nanj usmerite promet.

3. Najprej vklopite avtomatizacije, ki se sprožijo glede na vedenje. Opuščena košarica, opuščeno brskanje, znižanje cene, ponovna zaloga. Te se sprožijo ena za drugo, za enega človeka, v trenutku resnične namere. Prinašajo prihodek od prvega dne in jih je nemogoče pretiravati, ker jih vsak naročnik prejme le, kadar je nekaj storil.

4. Ročne kampanje dodajte nazadnje in redko. Bliskovita razprodaja, ki se konča nocoj, je dobra potisna kampanja. “Poglejte našo novo objavo na blogu” ni. Potisno obvestilo zmoti — sporočilo skoči čez to, kar človek počne — zato je lestvica za kampanjo precej višja kot pri e-pošti. Presoje o časovni razporeditvi so v kdaj naj trgovina pošlje potisno obvestilo.

5. Merite naročila, nato izboljšujte. Kliki potisna obvestila prikazujejo lepše, kot so. Naročila so semafor.

Kaj avtomatizirati: potisno obvestilo o opuščeni košarici, razčlenjeno

Tu je prva avtomatizacija, ki bi jo zgradil, v celoti:

Sprožilec: obiskovalec doda v košarico, a ne zaključi nakupa.
Segment: naročniki na potisna obvestila brez naročila v seji. Če je nekdo hkrati naročnik na potisna obvestila in na e-pošto, se odločite, kateri kanal vodi — ne sprožite obeh s polno močjo.
Zamik: približno 30–60 minut. Potisna obvestila so po naravi takojšnja; potisno obvestilo o košarici naslednji dan deluje zastarelo na način, kot e-poštno sporočilo o košarici naslednji dan ne.
Kanal: eno potisno obvestilo. Če je oseba tudi na vašem e-poštnem seznamu, e-pošta sledi pozneje z obsežnejšo ponudbo.
Vsebina: slika izdelka, njegovo ime, ena vrstica (“Vaša košarica vas še čaka”) in klik naravnost na blagajno — ne na domačo stran.
Cilj: obnovljeni zaključki nakupa, merjeni na poslano obvestilo.

Ena tehnična podrobnost, ki spremeni, kako pišete ta sporočila: potisno obvestilo je vidno le, če prispe, medtem ko brskalnik teče, nedostavljena obvestila pa potečejo. Za razliko od e-pošte ne čaka potrpežljivo v predalu. Zato mora potisno sporočilo imeti smisel v trenutku, ko pristane, in mora preživeti, tudi če ga oseba popolnoma zgreši — nikoli v potisno obvestilo ne dajte ničesar, kar mora kupec videti.

Primer iz trgovine

Vzemimo trgovino z obutvijo, ki ima 50.000 € na mesec. Znaten delež njenega prometa pristane na strani izdelka za priljubljeno supergo, ki je v pogostih številkah razprodana. Pred potisnimi obvestili so ti obiskovalci bodisi pustili e-naslov v obrazcu za ponovno zalogo (nekaj jih je) bodisi izginili (večina).

Ko potisna obvestila tečejo, razprodana stran ponudi poziv “Obvesti me, ko bo spet na zalogi” z enim klikom. Ko zaloga prispe, vsak naročnik dobi obvestilo s fotografijo čevlja v trenutku, ko je na voljo — verjetno popolno sporočilo, saj ga je kupec prosil zanj. Ta posamezni sprožilec je pogosto najlažja zmaga v vsem kanalu; svoj lasten vodnik dobi v uporaba potisnih obvestil za opozorila o ponovni zalogi. (Primer je ilustrativen, ne trditev o rezultatu.)

Kako izmeriti, ali si potisna obvestila prislužijo svoje mesto

Štiri številke, preverjene mesečno:

Stopnja prijav — ogledi poziva glede na sprejete naročnine. To pogojuje vse, kar sledi.
Stopnja klikov na avtomatizacijo — presoja o ustreznosti in besedilu.
Naročila in prihodek na poslano obvestilo — pravi semafor in številka, ki odloči, ali kanal ostane.
Izguba naročnin — pričakujte tih osip; upadanje števila aktivnih naročnikov ob nespremenjenem prometu običajno pomeni, da se je spremenila postavitev poziva ali da vas pogostost sili v utišanje.

Pripis prihodka pri potisnih obvestilih ima svoje posebnosti — klike je lahko šteti, vpliv ne. Ko boste pripravljeni poglobiti, je to pokrito v kako izmeriti prihodek od spletnih potisnih obvestil.

Kje se vključi Omnisend

K potisnim obvestilom sem pristopil skeptično — imela so sloves najbolj nadležnega kanala na spletu, večinoma prislužen s strani novičarskih strani, ki so bombardirale z naslovi. Kar me je spremenilo, je bilo, da sem jih zagnal sproženo glede na vedenje znotraj istega orodja kot svoje e-poštne tokove. V Omnisendu so potisna obvestila kanal znotraj urejevalnika avtomatizacij: isti tok za opuščeno košarico, ki pošlje mojo e-pošto, lahko najprej pošlje potisno obvestilo, naročnik, ki opravi nakup, pa hkrati zapusti cel tok čez vse kanale. Prav ta zadnji del je pomembnejši, kot se sliši — s samostojnim pripomočkom za potisna obvestila, prilepljenim ob vašo e-poštno platformo, kupca nič ne ustavi, da bi potisno obvestilo o košarici dobil potem, ko je že naročil.

Omnisend ne bo popravil slabe ponudbe in njegova potisna obvestila še vedno v celoti visijo na tem, kako dobro vodite poziv za prijavo. A če ga za e-pošto že uporabljate, je dodatni strošek nastavitve potisnih obvestil skoraj enak nič.

Vaš naslednji korak

Preden se dotaknete kakršne koli nastavitve, preverite eno številko: kolikšen odstotek obiskovalcev preteklega meseca vam je dal e-naslov? Vsi zunaj te številke so trenutno nedosegljivi brez plačevanja za oglase. Nato pravilno nastavite poziv za prijavo — začnite z kako pridobiti naročnike na spletna potisna obvestila, ker skvarjen poziv zapravi obiskovalce, ki jih ne morete znova vprašati.

Web Push Notifications

How to Use Web Push Notifications for Ecommerce

Posted on July 17, 2026 by

Web push notifications are short, clickable messages your store sends straight to a visitor’s browser — desktop or Android, and on iPhone if they’ve added your site to their home screen. The visitor opts in with one click on a browser prompt; you never need their email address. To use them well in ecommerce, treat push as a recovery and alert channel, not a broadcast channel: turn on behavior-triggered automations first (abandoned cart, price drop, back in stock), keep manual campaigns rare and genuinely urgent, and judge everything by orders, not clicks. This guide covers the full setup in order — how the channel works, who should bother with it, what to automate first, and how to tell if it’s earning money.

The problem push solves: paid visitors who leave nothing behind

You’re paying for traffic. Most of it looks at a few products and leaves, and the only tool you have to bring those people back is retargeting — which means paying Meta or Google a second time for a visitor you already bought once.

Email fixes part of this, but only for the slice of visitors willing to type their address into a popup. Everyone else walks out the door anonymous. That’s the gap web push fills: subscribing takes one click on a native browser prompt, no form, no typing, no inbox required. A visitor who would never give you an email will often accept a notification prompt, because the ask is so much smaller.

If you’re still weighing whether this channel deserves a place next to email at all, the comparison is laid out in email vs web push for online stores. Short version: push earns its place by reaching people email can’t, and it works best alongside email rather than instead of it.

Why “just retarget them” stops working

The usual answer to anonymous traffic is retargeting ads, and it does work — at a price that keeps moving. Ad platforms charge you every single time you re-reach the same person, forever. Tracking restrictions have made those audiences smaller and fuzzier, and your competitors are bidding on the same eyeballs.

A push subscriber costs you nothing per message after the opt-in. Once someone accepts your prompt, you can reach them directly for as long as the subscription lives. That’s the same logic that makes an email list valuable, applied to visitors who never gave you an email — an owned channel doing a job you currently rent from ad platforms.

One honest caveat before you get excited: a push list is more fragile than an email list. The subscription is tied to one browser on one device. If the visitor clears their site data, switches phones, or reinstalls their browser, the subscription dies silently — no unsubscribe event, no notice to you. Your push list decays in ways your dashboard won’t show, which is why push works best as a fast-acting channel for the near term, not a long-term relationship asset.

Where the revenue actually leaks

Run a quick illustrative calculation on your own numbers. Say your store gets 20,000 visitors a month and your email popup converts 2% of them — 400 new addresses. The other 19,600 people are gone unless you pay to retarget them.

Now suppose a well-placed push prompt gets even a modest share of those remaining visitors to opt in. Every one of them is a person you can now recall to the store for free — someone who abandoned a cart, browsed a product three times, or was waiting for a sold-out size to come back. Those are the highest-intent moments in your store, and for non-email visitors they currently produce zero follow-up. That’s the leak. (Numbers above are illustrative — plug in your own traffic and opt-in rates.)

Setting up web push, step by step

Do these in order. Steps one and two are infrastructure; the money is in steps three and four.

1. Pick a tool that ties push to store behavior. A standalone push widget can send messages, but it can’t see carts, orders, or product views. You want push inside the same platform as your email automation so one system tracks behavior and fires all channels. (I use Omnisend for this in my own stores — more on that below.)

2. Set up the opt-in prompt — carefully. This step has a trap: if a visitor clicks “Block” on the browser’s native prompt, the browser won’t ask them again. That answer is essentially permanent unless they dig into site settings themselves. So don’t fire the native prompt the second someone lands. Delay it, or use a two-step prompt where a soft ask precedes the real one. The full playbook is in how to collect web push subscribers — get this right before you drive traffic at it.

3. Turn on behavior-triggered automations first. Abandoned cart, browse abandonment, price drop, back in stock. These fire one at a time, to one person, at a moment of real intent. They produce revenue from day one and they’re impossible to overdo, because each subscriber only receives them when they’ve done something.

4. Add manual campaigns last, and sparingly. A flash sale ending tonight is a good push campaign. “Check out our new blog post” is not. Push interrupts — a message pops over whatever the person is doing — so the bar for a campaign is much higher than for email. The judgment calls on timing live in when should a store send a push notification.

5. Measure orders, then iterate. Clicks flatter push. Orders are the scoreboard.

What to automate: the abandoned cart push, spelled out

Here’s the first automation I’d build, in full:

Trigger: visitor adds to cart, doesn’t check out.
Segment: push subscribers without an order in the session. If someone is both a push and email subscriber, decide which channel leads — don’t fire both at full strength.
Delay: roughly 30–60 minutes. Push is immediate by nature; a next-day cart push feels stale in a way a next-day cart email doesn’t.
Channel: one push. If they’re also on your email list, email follows later with the fuller pitch.
Content: the product’s image, its name, one line (“Your cart’s still here”), and a click-through straight to checkout — not the homepage.
Goal: recovered checkouts, measured per notification sent.

One mechanical detail that changes how you write these: a push notification is only seen if it arrives while the browser is running, and undelivered notifications expire. Unlike an email, it doesn’t wait patiently in an inbox. So a push message has to make sense at the moment it lands, and it has to survive being missed entirely — never put anything in a push that a customer must see.

A store example

Take a shoe store doing €50,000 a month. A meaningful share of its traffic hits a product page for a popular trainer that’s sold out in common sizes. Before push, those visitors either left an email in a back-in-stock form (a few did) or vanished (most did).

With push running, the sold-out page offers a one-click “Notify me when it’s back” prompt. When stock lands, every subscriber gets a notification with the shoe’s photo the moment it’s available — arguably the perfect message, because the customer asked for it. That single trigger is often the easiest win in the whole channel; it gets its own walkthrough in using push notifications for back-in-stock alerts. (Example is illustrative, not a claimed result.)

How to measure whether push is earning its place

Four numbers, checked monthly:

Opt-in rate — prompt views to accepted subscriptions. This gates everything downstream.
Click rate per automation — judges relevance and copy.
Orders and revenue per notification sent — the real scoreboard, and the number that decides whether the channel stays.
Subscription loss — expect quiet decay; a shrinking active-subscriber count with stable traffic usually means your prompt placement changed or your frequency is driving mutes.

Attribution for push has its own wrinkles — clicks are easy to count, influence is not. When you’re ready to go deeper, that’s covered in how to measure revenue from web push notifications.

Where Omnisend fits

I came to push skeptical — it had a reputation as the spammiest channel on the internet, mostly earned by news sites blasting headlines. What changed my mind was running it behavior-triggered inside the same tool as my email flows. In Omnisend, push is a channel inside the automation builder: the same abandoned-cart workflow that sends my email can send a push first, and a subscriber who buys exits the whole flow across every channel at once. That last part matters more than it sounds — with a separate push widget bolted on next to your email platform, nothing stops a customer from getting a cart push after they already ordered.

Omnisend won’t fix a weak offer, and its push still depends entirely on how well you run the opt-in prompt. But if you already use it for email, the marginal setup cost of adding push is close to zero.

Your next step

Before touching any settings, check one number: what percentage of last month’s visitors gave you an email address? Everyone outside that number is currently unreachable without paying for ads. Then set up your opt-in prompt properly — start with how to collect web push subscribers on an ecommerce website, because a botched prompt burns visitors you can’t re-ask.