Email marketing za WooCommerce

Katere podatke WooCommerce Omnisend sinhronizira in kaj preveriti po nastavitvi

Posted on July 18, 2026 by

Ko povežete Omnisend z WooCommerce, ta prenese podatke iz trgovine, na katerih tečejo avtomatizacije: vaše stike (stranke in naročnike s statusom njihovega soglasja), vaš katalog izdelkov ter dogodke naročil in košaric — kdo si je kaj ogledal, kdo je dodal v košarico, kdo je oddal naročilo, kdo je kupil in koliko je porabil. To je surovina za vsak tok, ki ga boste zgradili. Zank je v tem, da “povezano” in “pravilno sinhronizirano” nista isto, tok, zgrajen na podatkih, ki so prišli le napol, pa bo tedne tiho podpovprečno deloval, preden to opazite. Ta stran zajema, kaj se dejansko sinhronizira, in — kar je bolj uporabno — konkretne stvari, ki jih je treba preveriti po nastavitvi, da ne gradite na pesku.

Če ju še niste povezali, najprej storite to z kako povezati Omnisend s trgovino WooCommerce; ta vodnik nadaljuje v trenutku, ko vtičnik sporoči, da je povezan.

Zakaj “piše, da je povezano” ni dovolj

Zelena kljukica na zaslonu integracije vam pove, da je stik prek API deloval. Ne pove vam, da je vsako naročilo prišlo čez, da se je status soglasja pravilno preslikal ali da se slike izdelkov pravilno prikazujejo v vaših blokih s priporočili. To so ločene stvari in vsaka lahko odpove neodvisno.

Videl sem, da je povezava poročala o dobrem zdravju, medtem ko so pretekla naročila pri velikem katalogu zaostajala več ur, in videl sem, da se je soglasje uvozilo tako, da je nenaročnike pometlo v segment za pošiljanje — vrsta napake, ki je nevidna, dokler ne pošljete in ne pridejo pritožbe. Rešitev ni nezaupanje do orodja. Rešitev je kratek preverjalni pregled, opravljen enkrat, takoj po nastavitvi, preden se na karkoli od tega zanesete.

Kaj se sinhronizira, po domače

Iz WooCommerce v Omnisend se premakneta trije koši podatkov in dobro je vedeti, kaj vsak od njih napaja.

Stiki in soglasje. Vaše stranke in naročniki pridejo čez s svojimi kontaktnimi podatki in, kar je pomembno, s statusom svojega marketinškega soglasja — ali so se dejansko prijavili na e-pošto ali SMS. To so podatki, ki odločajo, komu sploh smete pošiljati sporočila. Če to zgrešite, je vse navzdol bodisi nezakonito za pošiljanje bodisi pristaja pri ljudeh, ki se nikoli niso strinjali.

Katalog izdelkov. Vaši izdelki se sinhronizirajo, da lahko Omnisend gradi bloke s priporočili, e-pošte o košarici in brskanju napolni z resničnimi izdelki ter ohranja cene in razpoložljivost sveže. To omogoča, da e-pošta o opuščeni košarici prikaže dejanski izdelek, ki ga je nekdo pustil, s pravo sliko in ceno namesto nadomestnega mesta.

Dogodki: naročila, košarice in brskanje. Tok vedenja — ogledi izdelkov, dodajanje v košarico, začeto plačilo, oddano naročilo, vrednost naročila — je tisto, kar sproža avtomatizacije in gradi segmente. Tok za opuščeno košarico se sproži ob “dodano v košarico, a ni kupil”. Tok za ponovno aktivacijo potrebuje “datum zadnjega naročila”. Segmentacija po porabi potrebuje skupne zneske naročil. Vse to je odvisno od natančnega pretoka teh dogodkov.

Koliko zgodovine se natančno uvozi ob prvi sinhronizaciji in kako sprotni v realnem času so trenutni dogodki, je odvisno od velikosti vaše trgovine, različice vtičnika in nastavitve [VERIFY — globina uvoza zgodovine in zakasnitev sinhronizacije se razlikujeta glede na trgovino in različico vtičnika; potrdite v trenutni dokumentaciji Omnisend, namesto da domnevate]. Prav ta spremenljivost je razlog, da preverjate, namesto da domnevate.

Preverjalni pregled: kaj preveriti in po kakšnem vrstnem redu

To storite enkrat, premišljeno, takoj po povezavi. Dvajset minut zdaj vam prihrani mesec pokvarjenega toka pozneje.

1. Število stikov in status soglasja

Primerjajte število naročenih stikov v Omnisend s tem, kar bi pričakovali iz WooCommerce. Velik razkorak v katero koli smer je opozorilo — premalo pomeni, da je sinhronizacija nepopolna, preveč pa običajno pomeni, da so se vmešali stiki brez soglasja.

Nato preverite soglasje neposredno na vzorcu. Izberite nekaj stikov, za katere veste, da se niso prijavili na trženje, in potrdite, da niso v stanju, primernem za pošiljanje. To je posamično najpomembnejše preverjanje na seznamu. Pošiljanje ljudem, ki se nikoli niso naročili, škoduje dostavljivosti, krši pravila o soglasju in zapravlja zaupanje. Ne pošljite ničesar, dokler to ni čisto.

2. Nedavno naročilo je dejansko prispelo

Oddajte pravo testno naročilo ali poiščite eno iz zadnje ure in potrdite, da se v Omnisend pojavi pri pravem stiku — s pravilnim skupnim zneskom, pravilnimi izdelki in pravilnim časovnim žigom. To dokaže, da je cev za dogodke danes živa, kar je nekaj drugega kot potrditev, da so se uvozili pretekli podatki. Če se sveže naročilo ne pojavi v razumnem času, se ustavite in popravite povezavo, preden karkoli zgradite.

3. Podatki o izdelkih se pravilno prikažejo

Odprite svoj katalog izdelkov znotraj Omnisend in preverite, da imajo izdelki slike, cene in delujoče povezave. Nato v testno e-pošto spustite blok s priporočili izdelkov ali blok košarice in si oglejte predogled. Pokvarjene slike in manjkajoče cene v živi e-pošti o opuščeni košarici so pogosta, a prepričljiva sramota — in tu, v predogledu, se pokažejo, če pogledate.

4. Vedenjski sprožilci se sprožijo

Izvedite dejansko vedenje na testnem računu. Dodajte izdelek v košarico in jo opustite; oglejte si izdelek in odidite. Potrdite, da se ujemajoči dogodek zabeleži na vašem testnem stiku. Tok, ki se nikoli ne sproži, ker njegov sprožilni dogodek ne prihaja, je najdražja tiha napaka na tem seznamu — v gradniku izgleda živ, a ne ustvari ničesar.

5. Brez podvojenih ali nasprotujočih si pošiljanj

Če WooCommerce še vedno pošilja svoje lastne e-pošte o naročilih, medtem ko Omnisend prav tako pošilja sporočila v zvezi z naročili, lahko stranke dobijo vse podvojeno. Odločite se, kateri sistem je lastnik katerega sporočila, in izklopite prekrivanje. To zapelje več trgovin, kot bi si mislili — rešitev opišem v preprečevanje podvojenih transakcijskih e-pošt WooCommerce.

Kje se skriva izguba, ko preverjanje odpove

Vsako neuspešno preverjanje se preslika v konkretno puščanje, zato je preskočiti pregled drago.

Soglasje uvoženo napačno in bodisi ne smete zakonito pošiljati bodisi rušite dostavljivost s pošiljanjem hladnim stikom — trpi stopnja odpiranja vsakega toka. Naročila se ne sinhronizirajo in vaši tokovi za ponovno aktivacijo in ponovni nakup ciljajo napačne ljudi ali nikogar. Podatki o izdelkih pokvarjeni in vaše e-pošte z najvišjim namenom nakupa (košarica, brskanje) prikazujejo nadomestna mesta in izgubijo klik. Sprožilci se ne sprožijo in tok preprosto ne teče — mislite, da imate program za opuščeno košarico, imate pa izklopljenega.

Kratka ponazoritev. Recimo, da se dogodki opuščenega brskanja ne sinhronizirajo, vi pa ne preverite. Zgradite tok, ta gre v živo in pošilja nikomur, ker sprožilec nikoli ne prispe. Če bi ta tok obnovil vsaj 15 naročil na mesec po 60 € vsako, je to 900 € na mesec, ki se tiho ne zgodijo, gradnik pa ves ta čas prikazuje tok kot “aktiven”. (Ponazoritveno — bistvo je, da ima tiha odpoved sprožilca resnično ceno.)

Preverjanja spremenite v podatke, ki jih dejansko lahko uporabite

Ko je sinhronizacija preverjena, isti podatki postanejo temelj za pravo delo. Podatki o naročilih poganjajo segmentacijo — nedavni kupci, veliki porabniki, enkratni proti ponovnim — kar je tema zase: uporaba podatkov o naročilih WooCommerce za segmentacijo e-pošte. Podatki o izdelkih poganjajo dinamično vsebino in priporočila znotraj e-pošte: kako uporabiti podatke o izdelkih WooCommerce v avtomatiziranih e-poštah. Nobeno ne deluje dobro, dokler ni sinhronizacija pod tem čista, kar je ves razlog, da najprej preverite.

Kako izmeriti, da sinhronizacija ostaja zdrava

Preverjanje ni enkraten dogodek; podatkovne cevi zanašajo. Ohranite rahlo oko na:

Pojavljanje novih stikov, ko se ljudje naročajo — ravna črta običajno pomeni pokvarjeno formo ali sinhronizacijo, ne pa tihega tedna.
Ujemanje dogodkov naročil z resničnostjo — skupno število naročil v Omnisend v tednu bi moralo grobo slediti številu naročil v WooCommerce.
Obseg sprožitev tokov — če število vstopov v vaš tok za opuščeno košarico pade skoraj na nič, se je verjetno ustavil sprožilec, ne pa vaši kupci.
Trend dostavljivosti — nenaden skok zavrnitev ali pritožb zaradi neželene pošte pogosto izvira iz težave s soglasjem ali higieno seznama pri viru.

Če se pozneje samo sledenje zdi napačno — prihodek se ne pripisuje, dogodki se štejejo dvojno — je to ločena zajčja luknja, vredna svoje lastne seje odpravljanja težav, ločeno od tega začetnega preverjanja sinhronizacije.

Kako se v to vključi Omnisend

Vtičnik Omnisend za WooCommerce je zgrajen prav za premikanje teh podatkov, njegova orodja za avtomatizacijo in segmentacijo pa predpostavljajo, da so ti prisotni — zato so tokovi hitro zgrajeni, ko je sinhronizacija preverjena. Uporabljam ga v svojih trgovinah (je partner Shopimationa v pridruženem programu) in preverjalni pregled zgoraj je rutina, ki ji dejansko sledim po vsaki namestitvi, ker vzdrževana domača sinhronizacija še vedno pridobi, če človek pred zagonom potrdi soglasje in živo naročilo. Orodje premakne podatke; vi ste tisti, ki preveri, da so pravi.

Vaš naslednji korak

Blokirajte dvajset minut in danes na svoji trgovini opravite pet preverjanj zgoraj — najprej soglasje, nato živo naročilo, nato bloke izdelkov, nato sprožilce, nato podvojena pošiljanja. Ko je vsako preverjanje zeleno, imate čist temelj in lahko začnete graditi nanj. Naravna prva gradnja so vaši tokovi, ki poganjajo prihodek: začnite z kako nastaviti avtomatizacijo e-poštnega marketinga za WooCommerce in se pomikajte navzdol po prednostnem seznamu.

WooCommerce Email Marketing

What WooCommerce Data Omnisend Syncs—and What to Verify After Setup

Posted on July 18, 2026 by

When you connect Omnisend to WooCommerce, it pulls across the store data that automations run on: your contacts (customers and subscribers with their consent status), your product catalog, and your order and cart events — who viewed what, who added to cart, who checked out, who bought, and what they spent. That’s the raw material for every flow you’ll build. The catch is that “connected” and “syncing correctly” aren’t the same thing, and a flow built on data that’s half-arrived will quietly underperform for weeks before you notice. This page covers what actually syncs, and — more usefully — the specific things to check after setup so you’re not building on sand.

If you haven’t connected the two yet, do that first with how to connect Omnisend to a WooCommerce store; this guide picks up the moment the plugin says it’s linked.

Why “it says connected” isn’t enough

A green checkmark on the integration screen tells you the API handshake worked. It doesn’t tell you that every order came across, that consent status mapped correctly, or that product images are resolving in your recommendation blocks. Those are separate things, and each can fail independently.

I’ve seen a connection report as healthy while historical orders lagged for hours on a large catalog, and I’ve seen consent get imported in a way that swept non-subscribers into a mailable segment — the kind of mistake that’s invisible until you send and the complaints roll in. The fix isn’t distrust of the tool. It’s a short verification pass, done once, right after setup, before you rely on any of it.

What syncs, in plain terms

Three buckets of data move from WooCommerce into Omnisend, and it helps to know what each one feeds.

Contacts and consent. Your customers and subscribers come across with their contact details and, importantly, their marketing consent status — whether they’ve actually opted in to email or SMS. This is the data that decides who you’re even allowed to message. Get it wrong and everything downstream is either illegal to send or landing on people who never agreed.

Product catalog. Your products sync so Omnisend can build recommendation blocks, populate cart and browse emails with real items, and keep prices and availability current. This is what lets an abandoned-cart email show the actual product someone left, with the right image and price, instead of a placeholder.

Events: orders, carts, and browsing. The behavioral stream — product views, add-to-cart, started checkout, placed order, order value — is what triggers automations and builds segments. An abandoned-cart flow fires off “added to cart but didn’t buy.” A win-back flow needs “last order date.” Segmentation by spend needs order totals. All of it depends on these events flowing accurately.

Exactly how much history imports on first sync, and how real-time ongoing events are, depends on your store size, plugin version, and setup [VERIFY — historical import depth and sync latency vary by store and plugin version; confirm against current Omnisend docs rather than assuming]. That variability is precisely why you verify rather than assume.

The verification pass: what to check, in order

Do this once, deliberately, right after connecting. Twenty minutes now saves a month of a broken flow later.

1. Contact count and consent status

Compare the number of subscribed contacts in Omnisend against what you’d expect from WooCommerce. A wild mismatch either way is a flag — too few means the sync is incomplete, too many usually means non-consented contacts got swept in.

Then spot-check consent directly. Pick a few contacts you know did not opt in to marketing and confirm they’re not sitting in a mailable state. This is the single most important check on the list. Mailing people who never subscribed hurts deliverability, breaches consent rules, and burns trust. Don’t send a thing until this one’s clean.

2. A recent order actually arrived

Place a real test order, or find one from the last hour, and confirm it shows up in Omnisend against the right contact — with the correct total, the correct products, and the correct timestamp. This proves the event pipe is live today, which is a different thing from confirming that historical data imported. If a fresh order doesn’t appear within a reasonable window, stop and fix the connection before building anything.

3. Product data resolves cleanly

Open your product catalog inside Omnisend and check that products have images, prices, and working links. Then drop a product-recommendation or cart block into a test email and preview it. Broken images and missing prices in a live abandoned-cart email are a common, avoidable embarrassment — and they show up here, in preview, if you look.

4. The behavioral triggers fire

Run the actual behavior on a test account. Add a product to cart and abandon it; view a product and leave. Confirm the matching event registers on your test contact. A flow that never fires because its trigger event isn’t arriving is the most expensive silent failure on this list — it looks live in the builder and produces nothing.

5. No duplicate or conflicting sends

If WooCommerce is still sending its own order emails while Omnisend also sends order-related messages, customers can get two of everything. Decide which system owns which message and turn off the overlap. This trips up more stores than you’d think — I walk through the fix in preventing duplicate WooCommerce transactional emails.

Where the loss hides when a check fails

Each failed check maps to a specific leak, which is why skipping the pass is expensive.

Consent imported wrong, and you either can’t legally send or you’re tanking deliverability by mailing cold contacts — every flow’s open rate suffers. Orders not syncing, and your win-back and replenishment flows target the wrong people or nobody. Product data broken, and your highest-intent emails (cart, browse) show placeholders and lose the click. Triggers not firing, and the flow simply doesn’t run — you think you have an abandoned-cart program and you have a switched-off one.

A quick illustration. Say browse-abandonment events aren’t syncing, but you don’t check. You build the flow, it goes live, and it sends to nobody because the trigger never arrives. If that flow would have recovered even 15 orders a month at €60 each, that’s €900 a month quietly not happening, and the builder shows the flow as “active” the whole time. (Illustrative — the point is that a silent trigger failure has a real price tag.)

Turn the checks into data you can actually use

Once the sync is verified, the same data becomes the foundation for real work. Order data drives segmentation — recent buyers, high spenders, one-time vs repeat — which is a topic in itself: using WooCommerce order data for email segmentation. Product data powers dynamic content and recommendations inside emails: how to use WooCommerce product data in automated emails. Neither works well until the sync underneath is clean, which is the whole reason to verify first.

How to measure that the sync stays healthy

Verification isn’t a one-time event; data pipes drift. Keep a light eye on:

New contacts appearing as people subscribe — a flat line usually means a broken form or sync, not a quiet week.
Order events matching reality — total orders in Omnisend over a week should roughly track your WooCommerce order count.
Flow trigger volume — if your abandoned-cart flow’s entry count drops to near zero, the trigger likely stopped, not your shoppers.
Deliverability trend — a sudden bounce or spam-complaint spike often traces back to a consent or list-hygiene problem at the source.

If tracking itself looks off later — revenue not attributing, events double-counting — that’s a distinct rabbit hole worth its own troubleshooting session, separate from this initial sync check.

How Omnisend fits

Omnisend’s WooCommerce plugin is built to move exactly this data, and its automation and segmentation tools assume it’s present — which is what makes flows fast to build once the sync is verified. I run it in my own stores (it’s an affiliate partner of Shopimation), and the verification pass above is the routine I actually follow after every install, because a maintained native sync still benefits from a human confirming consent and a live order before launch. The tool moves the data; you’re the one who checks it’s the right data.

Your next step

Block twenty minutes and run the five checks above on your own store today — consent first, then a live order, then product blocks, then triggers, then duplicate sends. Once every check is green, you’ve got a clean foundation, and you can start building on it. The natural first build is your revenue-driving flows: begin with how to set up email marketing automation for WooCommerce and work down the priority list from there.