Avtomatizacija zapuščenega izdelka

Kako preprečiti, da bi avtomatizacija po ogledu izdelka tekmovala z reševanjem košarice

Posted on July 19, 2026 by

V trenutku, ko kupec ogledani izdelek doda v košarico, preneha biti primer opuščenega ogleda izdelka in postane primer reševanja košarice. Če tečeta oba toka, mora biti ta predaja čista — oseba naj izstopi iz toka ogleda izdelka in vstopi v reševanje košarice, nikoli naj ne sedi v obeh hkrati. Če to zamočite, nekdo, ki je dodal v košarico, dobiva mehke emaile “vas izdelek še vedno zanima?” hkrati z emaili “nekaj ste pustili v košarici”, o istem izdelku, iz iste trgovine. To je zmedeno, videti je pokvarjeno in požira dobronamernost ter dostavljivost. Popravek so izstopni pogoji, prioriteta tokov in logika razdvajanja: opuščeni ogled izdelka samodejno popusti reševanju košarice in noben kupec ni nikoli tarča obeh.

Takole postavite mejo, da tokova sodelujeta namesto trkata.

Zakaj se tokova privzeto zaletita

Opuščeni ogled izdelka in reševanje košarice sta soseda na isti poti. Eden se sproži, ko znan kontakt pogleda izdelek, ne da bi ga dodal; drugi se sproži, ko ga doda in ne zaključi nakupa. Zgrajena ločeno — kar je način, kako ju večina trgovin zgradi, ob različnih časih — nobeden ne ve, da drugi obstaja.

Tako se časovnici prekrivata. Nekdo si ob 14h ogleda jakno in vstopi v tok izdelka. Ob 16h se vrne in jo doda v košarico ter vstopi v tok košarice. Zdaj, razen če ga nekaj potegne ven, gresta ven tako email toka izdelka ob 18h kot večerni email toka košarice, oba o jakni. Kupec je napredoval — naredil je točno to, kar ste hoteli — in je bil za to kaznovan z dvojnim sporočanjem.

To je isti razred težave kot pošiljanje prekrivajočih se opomnikov za košarico in blagajno, disciplina pa je enaka: ena pot, en lastnik naenkrat. Kako se izogniti pošiljanju opomnikov tako za košarico kot blagajno pokriva sorodni primer.

Kateri tok zmaga in zakaj

Reševanje košarice vedno zmaga nad opuščenim ogledom izdelka. To ni tesna odločitev.

Košarica je močnejši, poznejši, dragocenejši signal kot ogled. Oseba se je premaknila od “gledam to” do “to hočem, v košarici je.” Reševanje košarice je tudi bolje konvertirajoč tok — namera je višja in sporočilo bolj neposredno. Ko sta torej v konfliktu, opuščeni ogled izdelka popusti. Celotna naloga toka izdelka je bila premakniti nekoga proti košarici; ko jo ima, je njegova naloga opravljena in naj se umakne s poti.

Prioriteto nastavite izrecno, namesto da bi upali, da bo časovnica poskrbela zanjo. Pravilo je ena vrstica: aktivno ali zaključeno dejanje v košarici zavre in izloči tok opuščenega ogleda izdelka.

Kje vas prekrivanje stane

Strošek dvojnega sporočanja ni le nerodnost. Recimo, da se 200 ljudi na mesec premakne od ogleda izdelka do dodajanja v košarico, medtem ko so še vedno v toku izdelka. (Ilustrativno.) Brez čistega izstopa vsak dobi sporočila iz obeh tokov o istem izdelku.

Tri stvari puščajo. Prvič, konverzija: zmeden kupec je omahljiv kupec in mešana sporočila (“še vedno razmišljate o tem?” proti “dokončajte naročilo”) zameglijo eno jasno dejanje, ki ga želite. Drugič, dostavljivost: dodatni, odvečni emaili dvignejo verjetnost pritožbe ali odjave, ta udarec ugleda pa se razširi na vsak tok. Tretjič, pripisovanje: oba tokova si lastita prodajo, tako da vam poročanje ne more povedati, kateri jo je dejansko zaslužil, in sprejemate slabe odločitve o tem, kam vlagati. Prekrivanje tiho obdavči konverzijo, ugled pošiljatelja in vašo sposobnost merjenja — vse hkrati.

Trije mehanizmi, ki ju ohranjajo ločena

1. Izstopni pogoji na toku izdelka. Tok opuščenega ogleda izdelka potrebuje trd izstop, ki se sproži v hipu, ko kontakt doda ogledani izdelek v košarico (in ločeno, ko kupi). “Dodano v košarico” ga takoj odstrani iz toka izdelka, sredi zaporedja, brez nadaljnjih pošiljanj. To je najpomembnejši nadzor. Brez njega nič drugega ni pomembno.

2. Zaustavitev vstopa na obeh straneh. Reševanje košarice naj ob prevzemu zavre kogar koli, ki je trenutno v toku izdelka, tok izdelka pa naj zavrne vstop komur koli, ki že ima aktivno košarico. Pas in naramnice: izstop poskrbi za ljudi, ki so že notri; zaustavitev poskrbi za robne primere in dirkalne pogoje, kjer dogodki pristanejo blizu skupaj.

3. Omejitev pogostosti med tokovi. Tudi s čistimi izstopi se lahko zaposlen kupec kvalificira za več avtomatizacij v dnevu. Globalna omejitev — strop, koliko avtomatiziranih emailov en kontakt dobi v obdobju — je varnostna mreža, ki ustavi vsako naključno kopičenje, ne glede na vir. Ščiti vas tudi pred zapleti dvojni-ogled-dvojna-košarica, v katere se spusti obravnavanje ponovnih ogledov istega izdelka.

Kaj konkretno avtomatizirati

Izstop iz opuščenega ogleda izdelka: sprožite takojšen izstop, ko kontakt doda kateri koli izdelek v košarico ali zaključi nakup. Brez zamude, brez zadnjega poslovilnega pošiljanja.
Zaustavitev vstopa v reševanje košarice: ko se reševanje košarice začne, odstranite ali zavrite kontakt iz katerega koli aktivnega toka ogleda izdelka, tako da ga ima v lasti samo eden.
Straža vstopa v tok izdelka: blokirajte vstop v tok izdelka za vsak kontakt z aktivno košarico ali blagajno v teku.
Globalna omejitev pogostosti: nastavite največje število avtomatiziranih sporočil na kontakt na dan/teden kot lovilec vsega.
Skupni izstop ob nakupu: oba tokova izstopita v hipu, ko se naročilo zaključi, tako da nihče ni preganjan zaradi nečesa, kar je kupil — ista zaustavitev, ki jo pokriva kako preprečiti emaile o zapuščeni košarici, potem ko stranka kupi.

Pravilno nastavljeno je zaporedje čisto: ogled → tok izdelka → dodano v košarico → tok izdelka izstopi, tok košarice vstopi → nakup → oba izstopita.

Primer iz trgovine

Trgovina, ki prodaja opremo za na prosto, je vzporedno vodila tok opuščenega ogleda izdelka in tridelni tok zapuščene košarice, zgrajena mesece narazen, nobeden se ni zavedal drugega. (Ilustrativno.) Kupci, ki so si ogledali šotor, se nato vrnili in ga dodali v košarico, so v urah drug od drugega dobivali email “še vedno razmišljate o Alpine 2?” in email “vaša košarica čaka” — isti šotor, isti dan.

Popravek je vzel eno popoldne. Toku izdelka so dodali izstop “dodano v košarico”, tako da je vsak, ki je napredoval, v hipu izpadel, in pravilo, da je reševanje košarice zavrlo vsakega, ki je bil še v toku izdelka. Nastavili so tudi globalno omejitev enega avtomatiziranega emaila na kontakt na dan kot varnostno mrežo. Dvojna sporočila so prenehala. Kupec je zdaj dobil eno skladno nit — mehak sunek med brskanjem, neposreden opomnik, ko se je zavezal — namesto da bi dva tokova govorila drug čez drugega.

Kaj meriti

Stopnja prekrivanja — koliko kontaktov je (ali je bilo) v obeh tokovih hkrati. Ciljajte na nič; karkoli nad tem pomeni, da se izstop ne sproža.
Emaili na kontakt na dan — pazite na vsakogar, ki presega vašo omejitev, kar signalizira puščanje v zaustavitvi.
Stopnja odjav in pritožb na obeh tokovih — padec, potem ko dodate izstope, je popravek dvojnega sporočanja, ki se pokaže.
Jasnost pripisovanja — s čistimi predajami je vsaka prodaja pripisana enemu toku, tako da vaše številke prihodka na tok končno nekaj pomenijo.

Kako se Omnisend prilega

Kar to potrebuje: izstopne pogoje, ki jih lahko nastavite na toku (dodano v košarico in nakup), zmožnost, da ena avtomatizacija zavre kontakte v drugi, vstopne filtre, ki preverijo aktivno košarico, in globalno omejitev pogostosti po vseh avtomatizacijah. Jasno poročanje po tokovih, da lahko opazite prekrivanje.

V svojih trgovinah uporabljam Omnisend, potem ko sem ga preizkusil proti Klaviyu, deloma zato, ker sem nastavljanje izstopnih pogojev in zaustavitve med tokovi lahko konfiguriral sam, namesto da bi ga moral skriptirati. (Priporočam ga in razkrivam vsako partnersko povezavo; logika upravljanja velja za vsako orodje, ki podpira izstope iz tokov in omejitve pogostosti.) Poštena omejitev: noben sistem ni popolnoma odporen na dirkalne pogoje — če dva dogodka pristaneta v isti sekundi, lahko redko zdrsne dvojno pošiljanje, kar je točno razlog, zakaj je vredno imeti globalno omejitev pogostosti kot varnostno mrežo, namesto zaupati zgolj izstopom.

Vaš naslednji korak

Odprite svoj tok opuščenega ogleda izdelka in preverite eno stvar: ali ima izstop “dodano v košarico”, ki se sproži takoj? Če ne, ga dodajte ta teden — to je edini nadzor, ki ustavi večino prekrivanja. Nato nastavite globalno omejitev enega ali dveh avtomatiziranih emailov na kontakt na dan kot varnostno mrežo in preverite svojo stopnjo prekrivanja v naslednjih štirinajstih dneh; padla naj bi blizu nič. Preden zatesnite predajo, poskrbite, da v tok izdelka sploh vstopa le resnično zanimanje — kako izključiti oglede izdelkov z nizko namero pokriva čiščenje sprožilca.

Product Abandonment Automation

Preventing Product Abandonment From Competing With Cart Recovery

Posted on July 10, 2026 by

You prevent product abandonment from competing with cart recovery with three rules: a strict priority order (checkout recovery beats cart recovery beats product abandonment — the stronger the intent signal, the higher the flow ranks), an instant exit from product abandonment the moment a shopper adds anything to cart, and a mutual exclusion window so nobody receives messages from both flows within the same few days. The failure you’re guarding against is specific and common: a shopper views a product, adds it to cart an hour later, and by evening has two emails from you — “still thinking about the jacket?” and “you left the jacket in your cart.” One store, two voices, both about the same item. Here’s how to wire the flows so it never happens.

How the overlap sneaks into well-run stores

Nobody builds this problem deliberately. You set up cart recovery first — everyone does, it’s the highest-converting flow. Months later you add product abandonment to catch the bigger pool of shoppers who never cart at all. Each flow works fine alone. But the shopper’s path runs straight through both: viewing a product is step one of adding it to cart. Without explicit coordination, every carted product view is a double-trigger waiting to fire.

At €50,000 a month in revenue you might have a few thousand flow-eligible shoppers monthly. Even a 10% overlap means hundreds of people a month getting stacked messages — and those are your best shoppers, the ones who progressed from viewing to carting. You’re being most annoying to exactly the people closest to buying.

Why “it still converts” isn’t a good enough answer

The tempting response is to shrug: both flows show revenue in their reports, so why touch them? Two reasons. First, attribution double-counts — when a shopper gets both emails and buys, each flow claims the order, so your reports overstate what the pair earns and you can’t tell which messages actually work. Second, the cost is deferred: stacked messages raise unsubscribes and spam complaints among high-intent shoppers, and every complaint chips at the deliverability that all your email — campaigns included — depends on. Adding a discount to one flow to “win” the overlap makes it worse: now the shopper gets a full-price nudge and a 10% code for the same product on the same day, and learns which email to wait for.

The cost of the collision, in numbers

Illustrative figures, invented for the example. Say 500 shoppers a month add to cart after a product view, and without coordination 300 of them receive messages from both flows — up to four emails in 48 hours about one product. Suppose the stacking pushes even 2% of those 300 to unsubscribe: 6 lost contacts a month, 72 a year, drawn specifically from your highest-intent segment. Meanwhile both flows claim the same ~40 recovered orders, so each looks roughly twice as effective as it is — and the next time you decide where to invest flow work, you decide on inflated data. The fix costs you one focused hour and removes both problems.

Fix it in this order

Write down the priority order first: checkout abandonment > cart abandonment > product abandonment > browse abandonment. Intent rises left to right through a shopper’s session; message priority should follow it. Everything below implements this one line.
Add the exit condition: product abandonment must eject a contact immediately on “added to cart” (and on “placed order”). This is the single highest-impact change — the cart flow takes over mid-conversation, cleanly.
Add entry exclusions both ways: product abandonment doesn’t accept anyone who entered cart or checkout recovery in the last 7 days; cart recovery entry needs no product-flow exclusion (higher intent always wins), but its send should suppress any queued product abandonment email.
Set a global frequency cap across automated messages — e.g. no contact receives more than one automated email per day and three per week, whatever combination of flows they qualify for.
Later, once clean: differentiate the flows’ jobs. Cart recovery talks about the specific items and checkout friction; product abandonment talks about fit, proof and alternatives. When the messages sound different, an occasional edge-case overlap does less damage. Cleaning entry signals helps here too — excluding low-intent product views shrinks the population that could ever collide.

The exact coordination spec

Product abandonment trigger: product viewed, no add-to-cart in session; delay 4–24 hours; exit conditions: added to cart, placed order, entered checkout.
Product abandonment audience filter: not in cart/checkout recovery within 7 days; hasn’t received cart recovery messages within 7 days.
Cart recovery trigger: cart abandoned; unchanged — it owns the highest-priority conversation and never yields.
Mutual exclusion window: 7 days is a sensible default; shorten to 3 for fast-moving, low-ticket catalogs.
Channel note: if you run SMS on cart recovery, the frequency cap must span channels — an email from one flow plus a text from another still reads as pestering. Combining product abandonment email and SMS covers cross-channel pacing in detail.
Goal: every shopper hears exactly one automated storyline at a time, matched to their strongest intent signal.

Example: one shopper, before and after

An illustrative walkthrough. Tuesday 10:00 — Maja views a €180 pair of boots. 14:00 — she adds them to cart, gets distracted, leaves. Before coordination: 14:00 product abandonment email (“Still eyeing the Verona boots?”), 15:00 cart recovery email (“Your cart misses you”), Wednesday 10:00 product abandonment email 2, Wednesday 14:00 cart recovery email 2. Four emails, 24 hours, one product. After: the add-to-cart at 14:00 ejects her from product abandonment before it ever sends; she receives only the cart sequence — one email at 15:00, one the next day. If she buys, one flow gets credit, and the number means something. This kind of rule belongs on your standing setup review — it’s one of the items on the product abandonment automation checklist.

Metrics that prove the flows now cooperate

Contacts entering both flows within 7 days — build this segment once; after the fix it should sit near zero. It’s your alarm if a platform update resets an exit condition.
Combined revenue of both flows — judge them as a pair; total should hold roughly steady while per-flow numbers become honest.
Unsubscribe rate among cart-flow recipients — the stacked-message victims; this should ease within a month.
Cart recovery conversion rate — often ticks up once its message isn’t arriving second in a pile.

Wiring it in Omnisend

Running email, SMS and push from one platform is a large part of why I chose Omnisend for my own stores over Klaviyo — cross-flow and cross-channel rules like these only work when one system sees every message a contact receives, and I wanted to manage that myself without stitching tools together. Concretely: exit conditions live in each workflow’s settings (add “added product to cart” and “placed order” to product abandonment), audience filters handle the 7-day mutual exclusion, and frequency capping controls total automated pressure per contact. Fair warnings: exit conditions rely on your store integration reporting cart events promptly, the audit takes an hour of clicking through settings you probably haven’t opened since setup, and coordination only pays if both flows are worth running at all — if you’re unsure, start with whether product abandonment is worth setting up for your traffic level.

Your next step

Open your product abandonment workflow right now and read its exit conditions. If “added product to cart” isn’t there, add it today — it’s a two-minute change that ends the worst version of this collision immediately.