Skip to main content

CompetitionLabs Academy · Achievements Advance

Flow Builder

Flow Builder workspace

Flow Builder is a visual configuration tool that allows operators to create and manage promotional flows by connecting different components and defining how members progress between them. It provides a structured way to configure the relationships, conditions, progression and outcomes that determine how a promotional experience behaves.

Using Flow Builder, operators can design more complex promotional experiences while reusing the platform’s existing promotion and reward capabilities within a single connected flow. This makes it possible to visualise the member journey and manage the logic between individual components without treating each part as an isolated configuration.

To build a flow, select the required Achievements from the left-hand side of the section and drag and drop them onto the Flow Builder board. Achievements can be positioned and organised on the board to represent the intended progression and relationship between the different objectives.

Once the required Achievements have been added, use the connection points displayed around each Achievement container to link them together. Each connection can be configured using Must, Should, or Must Not dependency logic. These rules determine how the completion or non-completion of one Achievement affects the availability, qualification or progression of another Achievement within the flow.

By combining multiple Achievements and dependency rules, operators can create anything from simple sequential flows to more complex experiences containing optional objectives, alternative progression routes and exclusion conditions. The visual structure of Flow Builder provides an overview of these relationships, making it easier to understand how the configured logic will affect the member's progression through the promotion.

You can read more about dependency logic and outcomes below.

DEPENDENT ON

You can specify a particular Achievement by name as a requirement for eligibility for another Achievement. A dependency can be Must, Should or Must-not. Dependent Achievements are not visible to the player. This allows you to build complex Achievement trees that support your promotional goals.

Examples:

  • MUST – If “5 free spins if you win once” depends on the Achievement “Register” with a Must rule, the member cannot complete the first Achievement until they have registered.
    Must Achievement dependency example
  • SHOULD – If “5 free spins if you win once” has Should dependencies on “Register” and “Log in”, the member must complete the configured number of those dependencies before completing the main Achievement.
    Should Achievement dependency example
  • MUST-NOT – If “5 free spins if you win once” has a Must-not dependency on redeeming a voucher, members who redeemed the voucher cannot receive the five free spins.
    Must-not Achievement dependency example

MINIMUM SHOULD MATCH

This field only appears when a Should dependency has been selected. The value indicates how many Should Achievements must be completed before the member can receive the main Achievement.

← Return to the Achievements navigation tutorial

Cookie Settings

We use cookies to keep the site working, understand usage, and improve relevance. Read our Cookie Policy and Privacy Policy.