Skip to content
Documentation
DropUI homepage
Topics

What data your store shares with DropUI

Want an audience based on purchases or a reminder about an abandoned cart? First check what data is actually reaching DropUI. It determines whether your chosen segment or workflow can work.

Data depends on the connection

Shoper and IdoSell provide full purchase-data integrations. You need a working app connection, data access and the correct store association. A script that displays campaigns does not provide complete purchase history.

On WordPress and WooCommerce, the plugin can supply the context of the current visit, page, product or cart to onsite campaigns. That is different from importing the entire order history into DropUI.

What each type of data supports

DataExample useWhat to check
Products and offersShowing serum in a recommendation or campaignName, price, currency, availability and product address
Orders and line itemsFinding customers who bought a particular productOrder status, date, amount, currency and store association
A contact linked to a purchaseA person's purchase historyWhether the purchase can be linked to a recognized contact
Cart and its activityA reminder about unfinished shoppingLast activity, cart status and whether the customer is recognized
Newsletter decisionsKeeping the correct channel consentSource, store, channel and signup or withdrawal

Shoper supplies email newsletter decisions; IdoSell supplies email and SMS decisions when the app has the required access. Each channel keeps its own decision. An order or a newly created contact is not marketing consent.

Check data before using it

Open Stores -> Stores and installation -> your store -> Overview. Data updates shows products, orders and the last cart activity separately.

DEMO STORE after import: 3 products, 5 orders and the time of the last cart activity.

Here, 3 products means serum, cream and cleanser. 5 orders counts imported records, not five paid purchases: one order is still unpaid. Open the lists to check their contents and statuses.

Then check Products, Orders or Carts in the Stores menu. Select the correct store and filters. Always consider currency when comparing amounts.

Do not assume the first fetch includes history going back indefinitely. The data available in DropUI depends on what the platform supplies and how the import has progressed. Check freshness and import problems.

What the data does not prove

  • Zero orders before the import finishes do not mean the store has made no sales.
  • An unidentified visitor is not someone you can automatically send a message to.
  • A product record does not guarantee a current price when its update has failed.

For example, prepare a campaign for serum buyers after checking products, orders and the consent required by your chosen channel. A first signup form does not need purchase history; you can start with a popup.

If DropUI data differs from your store, give us a specific product or order number, the store, period and update message. That helps identify the missing part.

Have questions after reading this guide?

Get in touch. We’ll answer your questions and help you with setup, free of charge.

Patryk Surmacz

I’ll walk you through the settings, step by step.