Skip to content
Documentation
DropUI homepage
Topics

Show a campaign based on cart or customer data

Want an offer to appear at a particular cart value or for a selected product? Use store-data conditions. First confirm that the integration supplies the information needed for that decision.

Check the platform and data

In Campaign settings, inspect Store platform, then open Cart & customer. Available conditions depend on the platform.

Cart and customer settings for the local Shoper demo campaign.

Do not choose a different platform just to reveal a field. It must match the store running the campaign. Check the connection when data is missing.

Choose a condition suited to the offer

A delivery message may only need cart value and currency. For a complementary cosmetic, check a product or category condition where supported.

Amounts and currencies must match the store's rules. Do not assume values in different currencies are automatically converted for comparison.

A sign-in condition uses available store-session information. It does not replace marketing consent, identify every visitor or give access to private customer orders.

Both screenshot conditions must match: value greater than 200 and currency USD. Exactly 200 does not satisfy “Greater than”. A $149 serum plus $89 cream makes a $238 cart, above the threshold.

Combine it with location and timing

Check how the selected criteria are combined. A product condition does not replace page restrictions, and reaching a threshold does not remove frequency limits.

Use the overview to inspect the entire configuration when several restrictions are enabled.

Example: an offer appears above $200. Test a $149 basket, then increase it to $238. With other conditions unchanged, the first should be below the threshold and the second above it. Check whether the chosen value includes only products or additional costs; it must use the same basis as the offer.

Test in the store

Prepare a cart that fails the condition, then change it so the condition matches. Compare both cases on the intended page.

Historical orders in the dashboard and a current browser cart are separate data sources. A correct design preview does not prove that the cart can be read. If the result differs, record the platform, page, amount, currency and test time.

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.