There are four statuses to the lifecycle workflow. You will notice that there is one new addition;

In Dev

Here you will find all inactive lifecycle versions in development. Add new versions, edit, clone, send to QA or delete from here.

From here you can;

  • Create a new version

  • Delete a version

  • Clone a version

  • Edit and work on a version

  • Change the version name

  • Change Lifecycle name

Note: Once the lifecycle version is moved out of In Dev, you will no longer be able to make any edits to the version itself. The only way to get the lifecycle back In Dev is to reject from QA.

QA

Lifecycle versions that are ready and waiting for quality assurance. Sign-off to approve or Reject to send back to In Dev for editing.

Check each activity in the lifecycle individually, approve each component of the activity and sign-off. Then check the lifecycle in its entirety and approve.

‘Reject’ the version to return it back to ‘In Dev’ if changes need to be made or 'Approve' to move the version to 'Active'.

From here you can;

  • Quality assure

  • Sign-off and move to Ready

  • Reject and move to In Dev

  • Clone a version. The cloned version will be found in In Dev

Note: Each activity and event that is signed-off will change colour from purple to green so you can easily keep track.

Read more about how to QA a lifecycle version .

Ready

The new status on the block.

For versions that are ready but not in production. In order to launch the lifecycle to Prod, you need to confirm the audience split and the trigger & segment to move players into your lifecycle.

A lifecycle version will wait in Ready once it has been QA'd. Once all the launch components are confirmed and verified, then it can move to Prod.

From here you can;

  • Clone a version. The cloned version will be found In Dev

  • Verify and move to Prod

  • Amend the lifecycle trigger and segment

  • Modify % split of segment between different versions

Note: Ready lifecycles are not live and have no players inside.

Prod

All lifecycle versions that are signed-off, activated and in production and running. Lifecycles in Prod are the only lifecycles with players inside and that are live.

From here you can;

  • Clone a version. The cloned version will be found In Dev

  • Stop a lifecycle from running. It will be moved back to Ready

  • Modify % split of segment between different versions

  • Check the players inside the lifecycle and choose to remove them or create a new segment with them

Note: When a lifecycle version is running you will see a green panel in each status inside the lifecycle and the green blinking light visible from inside the lifecycle and from the overview page.

Live Lifecycle
Live Lifecycle