Define Activities
Click on each activity and assign the desired action groups and actions.
Now we're ready to build the activities for our lifecycle. As you switch from Define Structure to Define Activities, you'll notice that the event structure and toolkit are replaced with blue activity slots.
It's almost like creating an activity, only now the firing conditions, trigger, and segment are already prepared and automatically managed by the lifecycle builder.
👀 Activity Conversion, Trigger & Segment
Here you can set the activity conversion tracking (and conversion period) and preview the event trigger and segment;
Select the blue activity box
Check Activity Conversion tracking and consider the conversion period
Preview trigger & segment set-up
Preview trigger and segment
Preview trigger and segment
🎬 Add Action Groups
Just like with creating activities, we add action groups and actions into lifecycle events in the same way.
Select Add new Action
Choose the Action Type
Fill in the required fields
Add Translations as required
Add new action
Add new action
➡️ Import Action Groups
Import action groups from existing activities and activities part of existing lifecycle projects into the lifecycle to save you time.
If you already have activities set-up that can form part of the lifecycle, then import them during the define activities stage to save you time.
Import Existing Actions
Import Existing Actions
🛂 Control Groups
Before you go ahead and send your lifecycle version to QA, you need to decide if you want to add a control group to your lifecycle version. With lifecycles, we add the control group to the entire lifecycle version, not per activity or action group inside the version.
Adding a control group to your lifecycle version will perform exactly as it would when you add a control group to an activity - by ensuring that a random selection of players within the lifecycle version will not receive any player engagement.
Adding a control group to your lifecycle version is important for you to be able to test and evaluate if the lifecycle version was successful. In this way, you can compare the results of those players who received the lifecycle engagement against those players who did not receive any engagement.
Example: You want to add a 10% control group to your lifecycle version.
This means that 10% of the players that enter inside the lifecycle version will receive no communication or player engagement but will move through the lifecycle and exit upon meeting the exit event criteria.
Here's how to add the control group;
Navigate to the IN DEV status of your lifecycle version. You can access this from define structure or define activities mode.
Select Control Group from the top-right to switch it to ON.
The % will display 10% by default. Adjust the number until you are happy and Save.
Add a control group
Add a control group
Note: Players inside the control group will still be affected by the lifecycle ending event.
Therefore, if the lifecycle ending event is Successful Deposit, the player inside the control group will still exit the lifecycle version upon Successful Deposit.