Player Origins In Use
Once you have set up the Player Origins, you will notice some additional options available inside Activities, Lifecycles, and email templates.
🚀 Activities
Once Player Origins is enabled and set up correctly, you can select, on an Activity level, which origin to include in each player engagement you send to your players.
Any set-up and enabled origins will be visible and available to be included when you create a new Activity. From inside a new Activity, click to select which Player Origins you want to enable for the player engagement you're about to set up. This will result in the Activity being triggered to any player that belongs to the selected origins.
Segments
With Player Origins selected, the Segment will display a Segment count that is broken down into each origin. This is to let you know the number of players that fall into each origin.
In the background, the Segment builder will automatically add the OR condition for each selected Player Origin to your selected Segment.
📧 Email Templates
When setting up an email Action inside an Activity, it is only possible to select an email template that has been enabled for all of the Player Origins that you've selected to include in the Activity.
If an email template has not been enabled for one or more of the Player Origins selected in your Activity, the template will not appear on the dropdown menu.
On the image below, on the right-hand side, you can see the icons of the origins that have been enabled for each available email template in the dropdown menu.
Assigning email templates to be available for Player Origins is handled in the Email Templates page of the CRM menu. Simply select the Player Origin tab at the top of the page, locate your email template and Add Player Origin.
Content Blocks & FT Conditions
Take advantage of the content blocks and FT conditions functionality inside the email template builder to be able to set up email templates that display dynamic content for multiple audiences.
Learn more here.
✅ Quality Assurance
When creating player engagement for multiple Player Origins, it is important to have full visibility of what will be sent and how it will look for each audience. For this reason, each targeted Player Origin is required to be thoroughly QA'd and signed off.
As you can see from the image below, the first few sections are common factors for the Player Origins and will be signed off simultaneously for all of them, whilst the Action Groups, Actions, and the Control Group for each Player Origin are grouped into Action Per Origin.
Simply select the button for each Player Origin. A new panel will open displaying any Action Groups, Actions, and a potential Control Group that needs to be QA'd.
Read more about the Quality Assurance process here.
💜 Lifecycles
Once Player Origins is enabled and set up correctly, you can select, at a Lifecycle project level, which Player Origin to include in the player engagements you send to your players.
Any enabled Player Origins will be visible and available to be included when you create a new Lifecycle.
Entry Conditions
Player Origins are assigned during the Entry Conditions set-up process and specifically when defining the Lifecycle entry Segment.
Lifecycle projects come in a variety of different formations: automated, set up for a specific date and time, built from scratch, or originating from a pre-defined template. Player Origins can be assigned regardless of these variations and will look as in the image below:
The rest of the Lifecycle building process looks the same as before, taking into account the same considerations mentioned in the above sections with regards to Activities, Activity segmentation, and email templates.
If you would like more information about how to build and manage Lifecycle projects, you can find some extra reading here.
Launch Lifecycle
With Player Origins enabled, there is an extra step of the launch Lifecycle process that requires you to confirm the selected Player Origins.
It is also possible to make a change to the Player Origin selection at this point. You can select to add a new Player Origin and/or remove an Player Origin from the selection that was made when defining the Entry Conditions.
Note: Please be aware that making changes to the Player Origin selection at this stage may result in problems launching the Lifecycle.
For example, You select to add a Player Origin that is not associated with the selected email template used inside the Lifecycle Activities. In this instance, you will receive an error message that will prevent the Lifecycle from being launched.
Here you need to move the Lifecycle version back to the development stage and make changes to the email set-up (select an appropriate email template), QA the Lifecycle version again and launch to production.
Last updated
Was this helpful?