Usage:Custom App Experiences

From Fuseboxx Wiki
Jump to: navigation, search

Custom App Experiences allow you make changes to your app without the need for iterative, time consuming updates. It also allows you to target these changes at existing cohorts for granular testing.

NoteBubble.png

For more information on App Parameters, if you are developing on iOS Click Here, or if you are developing on Android Click Here. You can also view our custom app experience guide Here

To create a Custom App Experience, open the Custom Experiences section (Toolboxx Tab > Custom Experiences) and press the Add/Edit Subsection. From here implementing the Custom Experience is simple (if you know what you want to change), input a Name for the experience and a Description if necessary, then select which Cohorts are to receive this Custom Experience (you can select one, many, all cohorts or all users). Now you just need to chose and edit the App Parameters that you wish to change for this Custom Experience (if you have a custom experience already set up you can load the Key-Value pairs from that experience, or from the standard experience).

Creating CEs.png

Once you have created the experience you can read data from the users in these experiences in two ways, first you can view All Custom Experiences and see the basic data (users, retention and revenue info) or you can Compare multiple experiences, to do this open the Compare section. In the compare section you can choose any number of cohorts to be displayed, you can then select what you want to be the y-axis (the data you are comparing), this is just another way to view the same data displayed on All Custom Experience subsection, but it is easier to view as you can compare one statistic at a time directly.

Once the Custom Experience no longer serves a purpose you can delete it from the All Custom Experiences subsection. Once the Experience is deleted there is no way to view the data from the experience.

A very basic example of how to use Custom App Experiences would be disabling ads for paying players. You could implement this by having a parameter which controls if the user sees ads, and switch the parameter for players in a cohort with IAP spend >0.