Kako meriti pokritost avtomatizacij skozi celotno pot kupca

Pokritost avtomatizacij je delež ljudi na vsaki stopnji poti kupca, ki dejansko prejmejo relevantno avtomatizirano sporočilo — ne pa vprašanje, ali tok za to stopnjo sploh obstaja. Da jo izmerite, naštejte stopnje poti, preštejte, koliko kontaktov je prejšnji mesec vstopilo v vsako stopnjo, preštejte, koliko od njih je vstopilo v tok, in delite. Večina trgovin, ki naredi to vajo, ugotovi isto: zid dejavnih avtomatizacij v računu in dve ali tri stopnje, kjer je resnična pokritost pod 10 %. Tok je lahko vklopljen, dobro zasnovan, celo dobičkonosen, pa vseeno doseže skoraj nikogar. Ta članek vam ponudi zemljevid, izračun in kaj storiti z vrzelmi, ki jih razkrije.

“Imamo vse tokove” ni isto kot biti pokrit

Tu je past. Odprete nadzorno ploščo avtomatizacij in vidite dobrodošlico, opuščeno košarico, opuščeno brskanje, ponakupni tok, ponovno aktivacijo — vse zeleno, vse pošilja. Videti je kot dokončan sistem. Ko rast zastane, zato sklepate, da je avtomatizacija izčrpana, in raje zapravite denar za oglase.

A nadzorna plošča prikazuje tokove, ne ljudi. Ne more vam povedati, da vaša serija dobrodošlice doseže le 3 % obiskovalcev, ki se prijavijo, ali da definicija “neaktivnega” v vašem toku ponovne aktivacije tiho izključuje polovico vaših neaktivnih kupcev, ali da se med prvim in drugim nakupom — v razponu, kjer se za vedno izgubi največ kupcev — po 7. dnevu ne zgodi nič avtomatiziranega.

Obstoj in pokritost sta različni meritvi. Trgovine sledijo prvi in skoraj nikoli drugi.

Zakaj “samo dodaj več tokov” na to ne odgovori

Brez številke pokritosti je dodajanje tokov ugibanje. Zgradili boste, kar je pisalo v zadnjem članku, ki ste ga prebrali, in tako računi končajo s tremi prekrivajočimi se tokovi za obnovitev na prednakupni strani in tišino povsod po potrditvi naročila. Dodajati je lahko; dodajati tam, kjer je največja nepokrita skupina ljudi, pa zahteva meritev, o kateri govori ta članek. Pokritost vam pove, kje graditi. Izračun prihodkov vam pove, koliko je to vredno — ta del pokriva kako razvrstiti avtomatizacije po potencialu prihodkov.

Zemljevid pokritosti: zgradite ga v eni uri

Korak 1: Zapišite stopnje

Omejite se na šest ali sedem. Uporabna privzeta izbira:

  1. Anonimni obiskovalec
  2. Prepoznani obiskovalec (prijavljen ali s piškotkom, brez nakupa)
  3. Aktivni kupec (nedavno brskal po izdelkih ali dal v košarico)
  4. Prvi kupec, 0–60 dni po nakupu
  5. Stalni kupec
  6. Ogrožen (brez interakcije ali nakupa v vašem običajnem oknu za ponovno naročilo)
  7. Neaktiven

Če je ritem vaše trgovine nenavaden — sezonski, visoke vrednosti, naročniški — najprej prilagodite definicije stopenj, preden karkoli drugega. Razmišljanje za zasnovo stopenj je samo zase tema, ki jo pokriva gradnja avtomatizacij okrog poti kupca.

Korak 2: Preštejte, kdo je prejšnji mesec vstopil v vsako stopnjo

Potegnite resnične številke: seje iz analitike za stopnjo 1, nove naročnike za stopnjo 2, prva naročila za stopnjo 4 in tako naprej. Za ogrožene in neaktivne uporabite števila iz svojih segmentov. Natančnost do zadnjega kontakta ni pomembna; velikostni red je.

Korak 3: Preštejte, kdo je vstopil v tok na vsaki stopnji

Vsaka platforma za avtomatizacijo poroča o vstopih v tok. Vsak tok povežite s stopnjo, ki ji služi, in zabeležite vstope prejšnjega meseca.

Korak 4: Delite in strmite v tabelo

Ponazoritveni mesec za trgovino z 10.000 obiskovalci (vaše številke bodo drugačne — potegnite svoje):

| Stopnja | Vstopajočih ljudi | Vstopov v tok | Pokritost |
|—|—|—|—|
| Obiskovalci | 10.000 | 0 | 0 % |
| Novi naročniki | 350 | 350 | 100 % |
| Brskal/dal v košarico | 1.800 | 210 | ~12 % |
| Prvi nakup | 220 | 220 | 100 % |
| Okno za ponovni nakup | 400 | 0 | 0 % |
| Neaktivni | 300 | 90 | 30 % |

V taki tabeli izstopata dve stvari, in izstopata tudi v večini resničnih. Prvič, stopnja brskanja in košarice: tokovi obstajajo, a se lahko prožijo le za prepoznane obiskovalce — ljudi, ki so se prijavili ali kliknili prek e-sporočila, tako da jih platforma prepozna. Anonimni brskalci, velika večina tistih 1.800, so toku nevidni. Avtomatizacija je vklopljena; pokritost je vseeno 12 %. Drugič, okno za ponovni nakup: pokrito z ničimer, čeprav je tistih 400 ljudi vaših najcenejših možnih naročil.

Pri tistem stropu prepoznanih obiskovalcev se je vredno ustaviti, saj spremeni rešitev. Nizka pokritost na stopnji brskanja običajno kaže na težavo z rastjo seznama in prepoznavanjem, preoblečeno v kostum avtomatizacije, ne na manjkajoč tok. Več prijav in več klikov v e-sporočilih dvigne pokritost opuščenega brskanja, ne da bi se dotaknili samega toka.

Branje zemljevida: tri vrste vrzeli

  • Prave vrzeli — stopnja z ljudmi v njej in brez toka. Okno za ponovni nakup zgoraj. Te gredo na vaš seznam za gradnjo, umerjene po potencialu prihodkov, lov nanje pa razširi iskanje manjkajočih tokov prihodkov v vaši spletni trgovini.
  • Vrzeli zaradi stropa — tok obstaja, a strukturno ne more doseči večine stopnje, kot opuščeno brskanje proti anonimnemu prometu. Popravite vhod (prepoznavanje, prijavo), ne toka.
  • Vrzeli zaradi definicije — tok obstaja in bi lahko dosegel ljudi, a so njegovi prožilni pogoji preozki. Tok ponovne aktivacije, ki zahteva “kupljeno vsaj dvakrat”, izključuje vsakega kupca ene same nakupovalne poti, ki je postal neaktiven — pogosto največjo neaktivno skupino, kar jih trgovina ima. Razširite ali razvejite prožilec.

Vsako nizko številko označite z eno od teh treh, preden se za karkoli odločite. Istih 12 % lahko pomeni “gradi”, “razširi seznam” ali “sprosti prožilec”.

Kaj avtomatizirati, ko je prava vrzel potrjena

Vzemimo vrzel okna za ponovni nakup, saj se pojavlja tako pogosto. Razčlenjeno kot je treba:

  • Prožilec: prvo naročilo dostavljeno, čakanje vezano na vaš običajni interval ponovnega naročila (za potrošno blago malo preden izdelka zmanjka; za trajno blago 30–45 dni v lastništvu).
  • Segment: en nakup, trenutno ne v nobenem drugem toku.
  • Kanal: e-pošta; SMS le, če je kupec privolil in je ponudba časovno omejena.
  • Vsebina: sporočilo 1 — pomoč pri uporabi ali iskren “kako gre?”; sporočilo 2 — točno izdelek, ki najpogosteje sledi njihovemu prvemu nakupu; sporočilo 3 — spodbuda z družbenim dokazom, popust neobvezen in zadnji.
  • Cilj: drugo naročilo. Izhod: kakršenkoli nakup.

Ena vrzel, en tok, nato ponovno izmerite. Uprite se skušnjavi, da bi tri vrzeli zapolnili v enem tednu — ustvarili boste težavo s prekrivanjem, ki je še niste imeli, pa ste imeli srečo.

Kako spremljati rezultat skozi čas

Štiri številke, ponovno preverjene mesečno ali četrtletno:

  • Pokritost po stopnjah — zgornja tabela, osvežena. To je glavna metrika.
  • Delež prepoznanega prometa — naročniki plus prepoznani obiskovalci deljeno s skupnimi obiskovalci, saj to omejuje vse pred nakupom.
  • Prihodek po stopnjah iz avtomatizacije — pove vam, ali nova pokritost pretvarja ali le pošilja.
  • Skupni avtomatizirani delež prihodkov iz e-pošte/SMS — počasna, zadovoljujoča črta, ki jo je lepo gledati naraščati.

V mojih trgovinah je tabela pokritosti tisti pripomoček, ki ga dejansko znova uporabljam — je na eni strani in razpravo “kaj naj zgradimo naslednje?” razreši v približno minuti.

Kje se umešča Omnisend

Zemljevid lahko zgradite s katerokoli platformo in preglednico. Omnisend olajša potegniti vhodne podatke: vsaka avtomatizacija na svoji nadzorni plošči poroča o vstopih in prihodkih, segmenti dajejo žive številke za definicije ogroženih in neaktivnih, in ker tokovi e-pošte, SMS in potisnih sporočil živijo na enem mestu, pokritosti ne sestavljate skupaj čez dve orodji. Potem ko sem poleg njega preizkusil Klaviyo, sem se odločil za Omnisend deloma prav zaradi te vrste vzdrževalnega dela — poročila, ki sem jih potreboval, so bila dosegljiva brez izvozov. Česar vam nobena platforma ne da, je imenovalec: ljudje, ki bi jim moralo biti sporočeno, pa ni bilo, se v poročilih o tokovih ne pojavijo nikjer. Ta številka obstaja le, če zgradite to tabelo.

Vaš naslednji korak

Rezervirajte uro, zgradite šestvrstično tabelo za prejšnji mesec in vsako stopnjo pod 50 % označite kot pravo vrzel, vrzel zaradi stropa ali vrzel zaradi definicije. Eno popravite. Če vaja razkrije težave onkraj pokritosti — zastarelo vsebino, prekrivajoča se pošiljanja, tokove, za katere se nihče ne spomni, da jih je zgradil — je čas za popolno razgradnjo: celovit pregled marketinških avtomatizacij spletne trgovine.

Measuring Automation Coverage Across the Customer Journey

Automation coverage is the share of people at each stage of the customer journey who actually receive a relevant automated message — not whether a flow for that stage exists. To measure it, list your journey stages, count how many contacts entered each stage last month, count how many of them entered a flow, and divide. Most stores that run this exercise find the same thing: a wall of active automations in the account, and two or three stages where real coverage is under 10%. A flow can be switched on, well-designed, even profitable, and still touch almost nobody. This article gives you the map, the math, and what to do with the gaps it exposes.

“We have all the flows” is not the same as being covered

Here’s the trap. You open your automation dashboard and see welcome, abandoned cart, browse abandonment, post-purchase, win-back — all green, all sending. It looks like a finished system. So when growth stalls, you conclude automation is maxed out and go spend money on ads instead.

But the dashboard shows flows, not people. It can’t tell you that your welcome series only reaches the 3% of visitors who subscribe, or that your win-back flow’s definition of “lapsed” quietly excludes half your inactive customers, or that between first purchase and second purchase — the stretch where most customers are lost for good — nothing automated happens at all after day 7.

Existence and coverage are different measurements. Stores track the first and almost never track the second.

Why “just add more flows” doesn’t answer this

Without a coverage number, adding flows is guesswork. You’ll build whatever was in the last article you read, which is how accounts end up with three overlapping recovery flows on the pre-purchase side and silence everywhere after the order confirmation. Adding is easy; adding where the biggest uncovered group of people is requires the measurement this article is about. Coverage tells you where to build. Revenue math tells you what it’s worth — that part is how to prioritize automations by revenue potential.

The coverage map: build it in an hour

Step 1: Write down the stages

Keep it to six or seven. A workable default:

  1. Anonymous visitor
  2. Identified visitor (subscribed or cookied, no purchase)
  3. Active shopper (browsed products or carted, recently)
  4. First-time customer, 0–60 days after purchase
  5. Repeat customer
  6. At-risk (no engagement or purchase in your typical reorder window)
  7. Lapsed

If your store’s rhythm is unusual — seasonal, high-ticket, subscription — adjust the stage definitions before anything else. The thinking behind stage design is its own topic, covered in building automation around the customer journey.

Step 2: Count who entered each stage last month

Pull real numbers: sessions from analytics for stage 1, new subscribers for stage 2, first orders for stage 4, and so on. For at-risk and lapsed, use your segment counts. Precision to the last contact doesn’t matter; order of magnitude does.

Step 3: Count who entered a flow at each stage

Every automation platform reports flow entries. Match each flow to the stage it serves and note last month’s entries.

Step 4: Divide, and stare at the table

An illustrative month for a store doing 10,000 visitors (your numbers will differ — pull your own):

| Stage | People entering | Flow entries | Coverage |
|—|—|—|—|
| Visitors | 10,000 | 0 | 0% |
| New subscribers | 350 | 350 | 100% |
| Browsed/carted | 1,800 | 210 | ~12% |
| First purchase | 220 | 220 | 100% |
| Repeat window | 400 | 0 | 0% |
| Lapsed | 300 | 90 | 30% |

Two things jump out in a table like this, and they jump out in most real ones too. First, the browse and cart stage: the flows exist, but they can only fire for identified visitors — people who’ve subscribed or clicked through an email so the platform can recognize them. Anonymous browsers, the large majority of that 1,800, are invisible to the flow. The automation is on; coverage is still 12%. Second, the repeat window: covered by nothing, even though those 400 people are your cheapest possible orders.

That identified-visitor ceiling is worth sitting with, because it changes the fix. Low coverage at the browsing stage usually points to a list-growth and identification problem wearing an automation costume, not to a missing flow. More signups and more email clickthroughs raise browse abandonment coverage without touching the flow itself.

Reading the map: three kinds of gap

  • True gaps — a stage with people in it and no flow at all. The repeat window above. These go into your build list, sized by revenue potential, and the hunt for them is expanded in finding missing revenue flows in your online store.
  • Ceiling gaps — a flow exists but structurally can’t reach most of the stage, like browse abandonment against anonymous traffic. Fix the input (identification, opt-in), not the flow.
  • Definition gaps — a flow exists and could reach people, but its trigger conditions are too narrow. A win-back flow that requires “purchased at least twice” excludes every one-time buyer who lapsed — often the biggest lapsed group a store has. Widen or branch the trigger.

Label each low number with one of these three before deciding anything. The same 12% can mean “build,” “grow the list,” or “loosen the trigger.”

What to automate once a true gap is confirmed

Take the repeat-window gap, since it shows up so often. Spelled out properly:

  • Trigger: first order delivered, wait tied to your typical reorder interval (for consumables, a bit before the product runs out; for durables, 30–45 days into ownership).
  • Segment: one purchase, not currently in any other flow.
  • Channel: email; SMS only if the customer opted in and the offer is time-bound.
  • Content: message 1 — usage help or the honest “how’s it going?”; message 2 — the specific product that most often follows their first purchase; message 3 — a nudge with social proof, discount optional and last.
  • Goal: second order. Exit: any purchase.

One gap, one flow, then re-measure. Resist filling three gaps in one week — you’ll create the overlap problem you were lucky enough not to have yet.

How to keep score over time

Four numbers, revisited monthly or quarterly:

  • Coverage per stage — the table above, refreshed. This is the headline metric.
  • Identified share of traffic — subscribers plus recognized visitors over total visitors, since it caps everything pre-purchase.
  • Revenue per stage from automation — tells you whether new coverage is converting or just sending.
  • Overall automated share of email/SMS revenue — the slow, satisfying line to watch climb.

In my own stores, the coverage table is the artifact I actually reuse — it’s one page, and it settles “what should we build next?” debates in about a minute.

Where Omnisend fits

You can build the map with any platform plus a spreadsheet. Omnisend makes the inputs easy to pull: each automation reports entries and revenue on its dashboard, segments give you live counts for at-risk and lapsed definitions, and because email, SMS, and push flows live in one place, you’re not stitching coverage together across two tools. After trying Klaviyo alongside it, I settled on Omnisend partly for exactly this kind of maintenance work — the reporting I needed was reachable without exports. What no platform gives you is the denominator: people who should have been messaged but weren’t appear nowhere in flow reporting. That number only exists if you build this table.

Your next step

Block an hour, build the six-row table for last month, and label every stage under 50% as a true gap, a ceiling gap, or a definition gap. Fix one. If the exercise surfaces problems beyond coverage — stale content, overlapping sends, flows nobody remembers building — it’s time for the full teardown: the complete ecommerce marketing automation audit.

Leave a Reply

Your email address will not be published. Required fields are marked *