You've created your lifecycle project! Now we need to work through the steps to build up the lifecycle with events and player engagement.

When you create a new lifecycle, the project will open in In Dev status with Version 1 of your lifecycle ready and waiting.

Version 1
Version 1

Info: Here's a summary of the information you can see in the image above;

  • Lifecycle version ID (485)

  • Lifecycle version Name (Version 1)

  • Lifecycle Type (Failed Deposit Intervention)

  • Number of Active Players (0)

  • Total Players who entered the lifecycle (0)

  • Total Number of Players who exited the lifecycle (0)

  • Percentage of Players who exited the lifecycle (N/A)

โš™๏ธ Lifecycle Statuses

Here's a quick recap of the lifecycle statuses and what they represent.

In Dev

This stands for In Development and is the status where we keep all inactive lifecycle versions. This is where we build the lifecycles and prepare all the player engagement.

In Dev
In Dev

QA

Quality Assurance is where a member of your team can closely check the structure and content of our lifecycle. Here is it either approved and moved to Ready or rejected and moved back to In Dev for editing.

QA
QA

Ready

Lifecycles that have been approved are moved to Ready. Here you can assign a control group to your version and prepare to launch. The lifecycle is not active at this stage until it has been launched into Production.

Ready
Ready

Prod

Production is where we keep lifecycle versions that are signed-off, activated and live. Players are able to move inside the lifecycle.

Prod
Prod

You can read more about Lifecycle Statues .

๐Ÿ“– Getting Started

Now we're ready to start building. Click to open Version 1 to be directed to the builder view.

Opening Version 1
Opening Version 1

Open version 1 to see that the template is already set-up. We have a pretty good idea of what a lifecycle should look like, so we already set it up a basic structure for you. But donโ€™t worry, you can completely customise it to your liking.

Workflow

There are two phases to building your lifecycle; Define Structure and Define Activities. We can switch freely between each overview but it makes sense to define the structure first and then add in the action groups and actions later.

You can move between the two and perform different actions in each mode, just make sure to save as you go.

๐Ÿงฑ Define Structure

We start by defining the structure;

  • Adding/removing during events

  • Adding/removing ending events

  • Splitting the audience

๐Ÿšฃ Define Activities

Once you have set up the triggers and segments, you are ready to define the activities. This works the same way as before, only now the firing conditions, trigger and segment are already prepared.

So, the only thing you need to do in this stage is;

  • Add/import action groups

  • Define the actions

โœ๏ธ Editing Entry Conditions

The entry conditions (trigger and segment) are defined when you create a new lifecycle. As you work on the lifecycle from In Dev, it may become necessary to make changes to the entry trigger and/or segment.

You can make edits to the entry conditions from In Dev status from either Define Structure or Define Activities tab.

From inside the lifecycle version, select the entry conditions to open a new panel. Here you can preview and edit the entry trigger and/or segment.

Select Save and Update Configuration to ensure the new changes are applied.

Edit Entry Conditions
Edit Entry Conditions

Note: It is also possible to edit the entry conditions of the lifecycle when launching the lifecycle to go live. This happens from Ready status once the lifecycle has been QA'd and is ready for Production.

Let's get started with define structure;

/lifecycles/building-lifecycles/define-structure