Skip to main content
Worked examples, framed by what you are trying to achieve rather than by which screen you are on. This is the #2 entry point on purpose: people work trial-and-error rather than read-then-do, so examples belong early, not buried mid-list. Every page here states the goal, draws the canvas as a diagram, lists the segment attributes involved, and ends with the variations that would otherwise have become separate pages.

Build an audience

By product bought

Everyone who bought a given product in a recent window.

By spend in a chain

Customers over a spend threshold in one chain.

By purchase volume

How many items, in one store, over a period.

By profile and frequency

A profile attribute combined with how often someone shops.

Shape the result

Add extra customer data

Attach attributes to the output with the Enrich block.

Split into groups

Divide one audience so each group gets its own treatment.

Feed and run a campaign

Reuse a saved segment

Define an audience once, select it in any campaign.

Use an imported customer list

Seed the campaign from a file of customer IDs.

Reuse a previous result

Chain one campaign’s output into the next.

Schedule and check results

Put it on a schedule, then read Execution History.

Offers

What you can build

Every discount shape the promotion platform supports, with an example of each.
Where this content came from. Eleven pages migrated from the current wiki: ten from Segmentation > User exercises and one from Offers > Offer examples. The twelve source exercise pages became ten — three chain-specific pages collapsed into Find customers by spend in a chain, since they differed only in the chain name.
Still to do in this section.
  • Two planned pages are not written — multi-game priority and attempts interaction, and lapsed-customer win-back. Neither exists in the current wiki, so there was nothing to migrate; both were asked for in client feedback.
  • Orchestration examples are missing. Use Cases was scoped to campaign setup; it needs to widen to orchestration, which is where the sharpest client complaint landed.
  • Screenshots have not been carried over. The source pages leaned on screenshots of the segment builder and the finished canvas. The canvas is redrawn as a diagram on each page; the segment-builder settings are now written out as attribute tables. Neither is a like-for-like replacement for an annotated screenshot.
  • A consolidation call is open. The four “build an audience” pages are the same recipe with different attributes. They could become one page with a variations table. Kept separate here because the gallery needs entries, but it is worth deciding deliberately.
Last modified on August 12, 2026