Skip to main content
This page shows you how to build an audience from what customers buy, and count it before anything reaches them. The worked example, spend in a chain, finds customers who spent 500 or more in one chain in the last 7 days. Three more examples change only the rules: buyers of a product, items bought in a store, and frequent shoppers by profile.

What you’ll build

On the campaign’s canvas, a Member segment block picks out the customers. The block after it, such as a Push or an Offer, decides what they get. Every example on this page uses these two blocks. Only the rules in the Member segment change.

Segment rules

Joined by AND, the three rules look at the same purchases. So Amount spent adds up only what the customer spent in that chain, in those 7 days.

Add a Member segment

  1. Open the campaign’s Orchestration view. To start a new campaign there, see Create a campaign.
  2. From Segment in the Block library, drag Member segment onto the canvas.
  3. Double-click the block, then choose From Scratch.
  4. On Add Segment details, enter a Member segment name, such as Spent 500+ in the chain, last 7 days.

Add the rules

Open Segment attributes. All three attributes are in the Purchase category.
  1. Double-click Store chain name. Choose In, then pick the chain from the list.
  2. Double-click Amount spent. Choose Greater or equal and enter 500.
  3. Double-click Purchase date. Choose Between, then Float, and set From 7 and to 0.
  4. Leave the rules joined by AND.
  5. Select Save.
The Segment attributes tab of a Member segment named Spent 500+ in the chain, last 7 days. The Segment builder reads The segment includes customers who … and holds three rules joined by AND badges: Store chain name set to In, with the chain Daily Tasty picked; Amount spent set to Greater or equal, 500; and Purchase date set to Between, with Float selected, from 7 to 0 days ago. Each rule ends with the note Data from today may be incomplete. The chain, spend and date rules, joined by AND Create a segment covers the builder in more detail.

Connect a push or an offer

From Activity, drag the block that acts on the audience, such as a Push. Then connect the Member segment to it. To give them an offer instead, connect the segment to an Offer block before you open it. Its Type list then shows only the types a flow can hand out, such as Gift. See Offer types and Orchestration canvas. Don’t publish the flow yet. Count it first.

Check the result

  1. Open the chevron beside Publish on the Member segment and choose Count. It saves the canvas, then counts the customers at each segment and operator block. Nothing is sent and no one gets an offer.
  2. The canvas switches to History, with the run selected. Wait for it to show Done.
  3. Select the Member segment block. Its Count is the number of customers who spent 500 or more in the chain in the last 7 days.
If the count is much higher than you expect, check that all three rules are joined by AND. A rule joined by OR widens the audience. When the count looks right, publish the flow and set its schedule. Schedule a campaign and check its results shows how.

More examples

Each example uses the same blocks and steps as the worked example. Only the segment’s name and its rules change, in Add the rules.

Buyers of a product

This one finds customers who bought a coffee brand in the last 30 days. Name the segment something like Bought the coffee brand, last 30 days. Without a Purchase date rule, Product looks at the last 90 days. So for a 90-day window, Product on its own is enough. Add the rules like this:
  1. In the Purchase category, double-click Product. The Product picker opens.
  2. Search or browse for the brand. Tick its product group, or tick single products in the column furthest to the right. Then select Add criteria.
  3. Double-click Purchase date. Choose Between, then Float, and set From 30 and to 0.
  4. Leave the rules joined by AND.
  5. Select Save.
The Segment attributes tab of a Member segment named Bought the coffee brand, last 30 days. The Segment builder reads The segment includes customers who … and holds two rules joined by an AND badge. The Product rule has no operator and shows the picked product group by its path: Root, Level 1 Food, Level 2 Beverages, Level 3 Coffee & Tea. The Purchase date rule is set to Between, with Float selected, from 30 to 0 days ago. Each rule ends with the note Data from today may be incomplete. A Product rule and a Purchase date rule, joined by AND The block’s Count is the number of customers who bought the brand in the last 30 days. A count of 0 means the Product picker has the wrong products ticked, or nobody bought them in the window. Open the block and check the Product rule first.

Items bought in a store

This one looks at how many items customers bought, not which ones. It finds customers who bought between 100 and 200 items in one store during September. Name the segment something like 100–200 items in the store, September. Joined by AND, the three rules look at the same purchases, as in the worked example. So Items bought counts only the items bought in that store, in September. Items bought counts items, not purchases. A customer who bought 120 items in 3 visits has an Items bought of 120 and a Receipt count of 3. To find customers by how often they shop, see Frequent shoppers by profile. Add the rules like this. All three attributes are in the Purchase category.
  1. Double-click Store name. Choose In, then pick the store from the list.
  2. Double-click Items bought. Choose Between, then enter 100 in From and 200 in To.
  3. Double-click Purchase date. Choose Between, then Fixed, and pick 1 September as the start and 30 September as the end.
  4. Leave the rules joined by AND.
  5. Select Save.
The Segment attributes tab of a Member segment named 100–200 items in the store, September. The Segment builder reads The segment includes customers who … and holds three rules joined by AND badges: Store name set to In, with the store MegaTasty picked and Manual input left unticked; Items bought set to Between, From 100 To 200; and Purchase date set to Between, with Fixed selected, From 01/09/2026 To 30/09/2026. The sidebar on the left lists the attribute categories, from Membership to App Data. The store, items and date rules, joined by AND The block’s Count is the number of customers who bought 100 to 200 items in the store in September. A Fixed window finds the same customers every time, so this audience suits a single run more than a daily schedule. Schedule and run a campaign covers both.

Frequent shoppers by profile

A profile attribute on its own rarely makes a good audience. Combined with how often customers shop, it does. This one finds women who made 5 or more purchases in the last 30 days. Name the segment something like Women, 5+ purchases, last 30 days. Lobyco Nexus keeps profile attributes, such as Gender and Age, in the Membership category. A Membership attribute isn’t about purchases, so the date rule doesn’t apply to it. Receipt count and Purchase date are Purchase attributes, so together they count the purchases made in the last 30 days. Receipt count counts purchases, not items. A customer who made 5 visits and bought 40 items has a Receipt count of 5. To find customers by how many items they buy, see Items bought in a store. Add the rules like this:
  1. In the Membership category, double-click Gender. Choose Equal, then pick the gender from the list.
  2. In the Purchase category, double-click Receipt count. Choose Greater or equal and enter 5.
  3. Double-click Purchase date. Choose Between, then Float, and set From 30 and to 0.
  4. Leave the rules joined by AND.
  5. Select Save.
The values in the Gender list come from your customer data, so they can read differently from one programme to the next. The block’s Count is the number of customers who match all three rules. Customers with no gender recorded aren’t in the count. A rule only finds customers who have a value for its attribute.

Variations

Each variation changes, adds or removes one rule. The example’s other rules stay as they are.
Last modified on October 21, 2026