Jump to: navigation, search

How to Set Up Segments

Revision as of 16:12, 6 August 2015 by Rfester (Talk | contribs) (IAPs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

How to Set Up Segments

Segments allow you to group your users together based on specific criteria using real time data. When you create an app in the Fuse dashboard we create a set of basic segments for you. These use industry best practice criteria to analyze your data. You can edit these or create custom segments that drill into specific player behaviour for your game. Once you have created these segments, you can use them in conjunction with many features on the dashboard, including push notifications and content block targeting.

Using Segments

Create a Segment

Start by selecting the app in the dashboard. Scroll down to the segments widget on the main dashboard page


Segments Dashboard Widget 1 .png

From here you can review your segments at a high level. To see all metrics tracked by segments click “see all segments”. On this page you can click each column header for more information on the metrics. Segments can be edited here by clicking on the segment name in the table.

To create a new segment, click the “add segment” button. Now, give your segment a name.

A segment with no criteria includes all users. To check the number of users in your segment at any time during the set up process, simply click the refresh button.

To start refining your segment, click “add new criteria”. This example is looking at all users who are level three and above. The criteria chosen is “level”, the comparison “is after or equal to”, and the value is “3”. Clicking save, then the refresh button reveals how many users fit that criteria. Click the save button in the lower right to save the segment and add it to the segment list.

Segments Dashboard Add Segment 2.png

In this example, “test users” was picked as the criteria, and “are” as the comparison. After saving, hit the refresh button and your segment will populate with the test users that have used the app. This is a useful criteria because it will allow you to target and analyze your test users specifically. To learn how to add test users, click here. (link to test wiki)

Segments Dashboard Add Segment 1 .png

NoteBubble.png

Segments require the user to meet all entered criteria to be included.

NoteBubble.png

To edit a criteria, click it in the criteria list.
Comparing Segments

It can be useful to compare two or more segments directly instead of looking at them on the full list. To access the comparison page, click “compare segments” on the dashboard widget or the segments page.

Click in the “select segments” list and a dropdown list of your segments will appear. Scroll through and click, or type in a name to find the segments you are looking for.

Segments Dashboard Compare 1 .png

As you select segments, a chart mapping them will appear. select the metric you would like expressed in the chart with the “select metric” dropdown menu.

Segments Dashboard Compare 2.png

Click the download button to export the information in a .CSV file.

Sources of Segment Criteria

Segment criteria are used to filter a group of users based on data collected by our SDK. Here is a breakdown of each criterion, their meaning and their corresponding SDK calls.

User Types
  1. Paying Users
    Users who spent money on your game. This criteria uses data retrieved from the Register IAP calls. Please see the integration guide for your development platform for more details.
  2. Test Users
    Test users are devices added to your test devices list. For details on how to add a test device under your account, click here. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  3. Cracked Users (iOS Only)
    Cracked users are devices which have a different application signature than the store version. Any device not running the store version of your app (e.g. Jailbroken devices, ad hoc builds) will register as a cracked device. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
User Attributes
  1. Country
    The country the device is connected to the internet from. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  2. Device (iOS Only)
    The type of the device. Can be iPod/iPhone, iPad or Other. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  3. Current Version
    The Game version the user is running. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
Usage
  1. Install Date
    Date of the first time the device started a Fuse Powered session. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  2. Install Date & Time
    Date & Time of the first time the device started a Fuse Powered session. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  3. Hours Since Install
    Hours since the first time the device started a Fuse Powered session. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  4. Days Since Install
    Days since the first time the device started a Fuse Powered session. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  5. Total Sessions
    Total number of Fuse Powered Sessions started by the device. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  6. Total Days Used
    Total number of days a Fuse Powered Session was started by the device. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  7. Days since last session
    Days since the last time the device started a Fuse Powered session. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  8. Date & Time of last session
    Date & Time of the last time the device started a Fuse Powered session. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  9. Days Since Previous Session
    Days since the previous time (second last time) the device started a Fuse Powered session. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
  10. Minute of Install
    Integer corresponding to the minute of the install timestamp (0-59), can be used to create segments of random devices. This data is collected on Fuse Powered Session Start, and does not require any additional SDK calls.
Behavior
  1. Level
    Current player level registered by the registerLevel SDK call.
  2. Balance of 1st Currency
    Current balance of the currency registered by the registerCurrency SDK call with index as 1.
  3. Balance of 2nd Currency
    Current balance of the currency registered by the registerCurrency SDK call with index as 2.
  4. Balance of 3rd Currency
    Current balance of the currency registered by the registerCurrency SDK call with index as 3.
  5. Balance of 4th Currency
    Current balance of the currency registered by the registerCurrency SDK call with index as 4.
IAPs
  1. IAPs Purchased
    The list of items purchased by this device using the registerInAppPurchase SDK call. You can use this criteria to filter devices based on the purchase of a specific item.
  2. Total IAP Spend
    The total amount spent on all IAPs registered by this device using the registerInAppPurchase SDK call.
  3. Total IAPs
    The total number of IAPs registered by this device using the registerInAppPurchase SDK call.
  4. Non-verified IAPs
    The number of IAPs made by a user that were non-verified. A non-verified IAP is an IAP that was completed, but not confirmed by the app store.
First IAP
  1. First IAP
    The name of the first IAP registered by this device using the registerInAppPurchase SDK call.
  2. Amount spent on first IAP
    The amount spent on the first IAP purchase registered by this device using the registerInAppPurchase SDK call.
  3. Date of first IAP
    The date of the first IAP registered by this device using the registerInAppPurchase SDK call.
Second IAP
  1. Second IAP
    The name of the second IAP registered by this device using the registerInAppPurchase SDK call.
  2. Amount spent on second IAP
    The amount spent on the second IAP registered by this device using the registerInAppPurchase SDK call.
  3. Date of second IAP
    The date of the second IAP registered by this device using the registerInAppPurchase SDK call.
Latest IAP
  1. Latest IAP
    The name of the latest IAP registered by this device using the registerInAppPurchase SDK call.
  2. Amount spent on latest IAP
    The amount spent on the latest IAP registered by this device using the registerInAppPurchase SDK call.
  3. Date of latest IAP
    The date of the latest IAP registered by this device using the registerInAppPurchase SDK call.
  4. Days since latest IAP
    Days since the the latest IAP registered by this device using the registerInAppPurchase SDK call.
Virtual Goods
  1. Virtual Goods Purchased
    The list of virtual goods purchased by this device using the registerVirtualGoodsPurchase SDK call. You can use this criteria to filter devices based on the purchase of a specific item.
  2. Total Virtual Goods
    The total number of virtual good purchases registered by this device using the registerVirtualGoodsPurchase SDK call.
  3. Total Currency Spent on Virtual Goods
    The total amount spent on virtual goods registered by this device using the registerVirtualGoodsPurchase SDK call.
First Virtual Good
  1. First Virtual Good
    The name of the first purchased virtual good registered by this device using the registerVirtualGoodsPurchase SDK call.
  2. Date of First Virtual Good Purchase
    The date of the first purchased virtual good registered by this device using the registerVirtualGoodsPurchase SDK call.
  3. Currency Spent on First Virtual Good
    The amount spent on the first virtual good purchase registered by this device using the registerVirtualGoodsPurchase SDK call.
  4. Currency Used on First Virtual Good
    The type of currency used on the first virtual good purchase registered by this device using the registerVirtualGoodsPurchase SDK call.
Second Virtual Good
  1. Second Virtual Good
    The name of the second purchased virtual good registered by this device using the registerVirtualGoodsPurchase SDK call.
  2. Date of Second Virtual Good Purchase
    The date of the second purchased virtual good registered by this device using the registerVirtualGoodsPurchase SDK call.
  3. Currency Spent on Second Virtual Good
    The amount spent on the second virtual good purchase registered by this device using the registerVirtualGoodsPurchase SDK call.
  4. Currency Used on Second Virtual Good
    The type of currency used on the second virtual good purchase registered by this device using the registerVirtualGoodsPurchase SDK call.
Latest Virtual Good
  1. Date of Latest Virtual Good
    The date of the latest purchased virtual good registered by this device using the registerVirtualGoodsPurchase SDK call.
  2. Days Since Latest Virtual Good
    Days since the the latest virtual good purchase registered by this device using the registerVirtualGoodsPurchase SDK call.
  3. Currency Spent on Latest Virtual Good
    The amount spent on the latest purchased virtual good purchase registered by this device using the registerVirtualGoodsPurchase SDK call.
  4. Currency Used on Latest Virtual Good
    The type of currency used on the latest virtual good purchase registered by this device using the registerVirtualGoodsPurchase SDK call.
Ads
  1. Non-Rewarded Ad Impressions
    Total number of Non-Rewarded ads shown to the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  2. Last Non-Rewarded Ad Impression
    Date of the latest Non-Rewarded ad shown to the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  3. Days since last Non-Rewarded Ad Impression
    Days since the latest Non-Rewarded ad shown to the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  4. Rewarded Videos Completed
    Total number of Rewarded videos shown to the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  5. Last Rewarded Video Completed
    Date of the latest Rewarded video shown to the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  6. Days Since Last Rewarded Video Completed
    Days since the latest Rewarded video shown to the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  7. Rewarded Videos Rejected
    Total number of Rewarded Videos rejected by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  8. Days Since Last Rewarded Video Rejected
    Days since the latest Rewarded Video rejected by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
Offers
  1. Total IAP Offers Rejected
    Total number of IAP offers rejected by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  2. Total IAP Offers Accepted
    Total number of IAP offers accepted by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  3. Total VG Offers Rejected
    Total number of Virtual Good offers rejected by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  4. Total VG Offers Accepted
    Total number of Virtual Good offers accepted by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
Latest IAP Offer
  1. Date IAP Offer Rejected
    Timestamp of last IAP offer rejected by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  2. Days Since IAP Offer Rejected
    Number of days since last offer rejected by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  3. IAP Offer Accepted
    The name of the last IAP offer accepted by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  4. IAP Offer Rejected
    The name of the last IAP offer rejected by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  5. Date Last IAP Offer Accepted
    Timestamp of last IAP offer accepted by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  6. Days Since IAP Offer Accepted
    Number of days since last offer accepted by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
Latest Virtual Good Offer
  1. Date Virtual Good Offer Rejected
    Timestamp of last Virtual Good offer rejected by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  2. Days Since Virtual Good Offer Rejected
    Number of days since last Virtual Good offer rejected by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  3. Virtual Good Offer Accepted
    The name of the last Virtual Good offer accepted by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  4. Virtual Good Offer Rejected
    The name of the last Virtual Good offer rejected by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  5. Date Last Virtual Good Offer Accepted
    Timestamp of last Virtual Good offer accepted by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
  6. Days Since Virtual Good Offer Accepted
    Number of days since last Virtual Good offer accepted by the user. This criteria uses data retrieved from the showAdForZoneID SDK call.
Parental Consent
  1. Parental Consent
    This criteria filters users based on the registerParentalConsent SDK Call. The mapping of values in the call to the values on the dashboard are;
    FALSE = Not Granted
    TRUE = Granted
    NULL = not provided
Gender
  1. Gender
    This criteria filters users based on the data retrieved from the registerGender SDK Call. The mapping of values in the call to the values on the dashboard are;
    0 = None
    1 = Male
    2 = Female
    3 = Undecided
    4 = Withheld
Birthdate
  1. Birthdate
    This criteria filters users based on the data retrieved from the registerBirthday SDK call.
  2. Age
    This criteria filters users based on the data retrieved from the registerBirthday or registerAge SDK call. Implementing either one of these calls will give you the ability to use this criteria to filter your users.
Custom
  1. CustomEvent<num> (i.e. CustomEvent_1, CustomEvent_2, etc.) [1-10]
    This criteria filters users based on the data retrieved from the registerCustomEvent SDK call with index 1 through 10 and an integer value. You can rename the criteria to a more user friendly name on Configuration -> Segment Settings tab.
  2. CustomEvent<num> (i.e. CustomEvent_11, CustomEvent_12, etc.) [11-20]
    This criteria filters users based on the data retrieved from the registerCustomEvent SDK call with index 11 through 20 and a string value. You can rename the criteria to a more user friendly name on Configuration -> Segment Settings tab.
  3. CustomEvent<num> Last Update
    This criteria filters users based on the date and time last time the registerCustomEvent SDK call has been called. You can rename the criteria to a more user friendly name on Configuration -> Segment Settings tab.