Skip to main content
A campaign wraps activities and an audience into something you can schedule and track. Inside it, the orchestration canvas automates a sequence of actions: something starts it, it works out who it applies to, and it does something to those customers.
Campaigns have three tabs in the Lobyco Admin Portal — Campaigns, Orchestration and Calendar. This section covers all three: the campaign itself, the orchestration canvas inside it, and when it runs.

How a flow fits together

Every flow is the same three things in sequence, whatever it is for:
  1. A trigger starts it — a customer action, an event on an activity, a call from another system, or a clock.
  2. An audience decides who it applies to — a segment built from rules, or a list you upload, optionally reshaped by operators.
  3. An activity does something to them — sends a message, gives them an offer or a game, or exports the result.
Blocks in between control the flow rather than add to it: Delay holds customers for a period, Limit caps how many pass. The order is a real constraint, not just a convention. A block can only use what the block before it hands over, so a step that needs extra customer data has to sit after something that supplies it.

What lives here

Orchestration canvas

Build a flow: add a trigger, connect blocks, set who can edit it, and schedule it to run.

Find and manage campaigns

Find and clone flows, schedule their runs, and read what happened when they ran.

Block reference

Every block in the library — what it does, what it needs as input, and what it passes on.

Where the neighbouring pieces are documented

This section covers the canvas and the blocks on it. Three things a flow depends on are documented elsewhere, deliberately, so they are not written twice:
  • Segments — the rules, rulesets and attributes an audience is built from are in Audiences & Data. This section covers the Member segment block; that section covers what goes inside it.
  • Communications — Push, Email, Banner, Feeds and Prompt behave the same on a canvas as anywhere else, and are documented once in Channels.
  • Activities — Offers, Games and Challenges are documented in Activities.

Worked examples

If you would rather follow a real scenario than read reference material, Use Cases has flows built end to end, including ones that combine several activities.
Last modified on September 17, 2026