Content:
You can create different audiences using Hybe Console based on various events such as installs, in-app registrations, in-app purchases, and many others.
Once you have created a new app and integrated it with an MMP, a data cloud is automatically created for your app to generate and serve your audiences.
1. MMP audience
To start, first of all, you need to go to the left sidebar and select "Data Clouds".
Here you will see Cloud Name (it will be the same as your App Name), the ID of your data cloud and the number of audiences you have created.
Click the Cloud Name and you will see the next page where you can create a new audience.
Choose "MMP Audience" and go next.
On the next page, you will see the Audience Settings.
Here you should enter your audience name. After that you can change some settings:
1. You can set a duration of a lookback window (from 1 to 90 days). It's a specific period during which the type of event specified below (install, registration, in-app purchase, or something else) will be taken into account and attributed to your ad. On the base of the chosen event, the user will be included in the audience. The specified duration of the lookback window starts from the moment of the audience collection. Let's see some examples:
If you want to set the duration of lookback window from 1-st to x-th days inclusively, then you need to choose an option "less than x+1", in other words, "less than 8" means that you want to include events only from 1-st to 7-th days inclusively.
If you want to set the duration of lookback window from x-th (more than 1) to y-th days, then you need to choose "between x and y". For instance, the setting "between 14 and 35" means that you want to include events only from14-th (inclusively) to 35-th days (inclusively).
Also, if you want to set the duration of lookback window from x-th day to 90-th, then you need to choose "more than x-1". That is the option "more than 62" means that you want to take into account only those events which happened from 63-th to 90-th days.
2. Next, you can set the frequency. In this case, frequency means how many times the user completed the specified event during the Lookback window with all additional settings and filters you have set. Here you pick any of four options: "any", "greater or equal", "less or equal", "is". Let’s take some examples:
"Any" option means that frequency is not set.
If you want to take into account only users made the chosen event no more than five times during the lookback window, you should set "less or equal 5".
If you want to count only users, who made the chosen event an exact number of times( e.g. 3) during the lookback window, you need to pick "is 3".
In case want to take into account only those users, who performed the chosen event, for instance, no less than two times during the lookback window, you need to set "greater or equal 2".
3. Then you can set the total revenue. Total revenue allows you to include in your audience people who completed some events and their total revenue matches the required one (only during set lookback window). Here you have five options: "any", "more than", "less than", "between", "is".
Learn more by the following examples:
"Any" – total revenue is not set.
If you select "purchase" and want to collect in your audience only users reached in total more than $10, making purchases in your app, select "more than 10" option.
If you set "subscription" and want to collect only users who spent in total less than $5, buying a subscription in your app, select "less than 5".
If you set "buy_a_pack_of_gold" event and want to collect users, who spent between $4 and $10, buying packs of gold in your app, select "between 4 and 10" option.
And if you set "buy_a_pack_of_diamonds" event and want to collect users, who spent $20, buying packs of diamonds in your app, select "is 20" option.
4. Also, you can include or exclude users, who completed the event you set; to do that – switch a specific toggle.
5. Then you need to select an appropriate event based on which you will collect users in your audience, for example, "server_start_trial".
6. Last available option is filter. It allows you to choose specific Country/City/Language or some other parameter and sort users, who completed the selected event and subject to this parameter. For example, if you want to collect only people from the USA, you need to set the following filter and save it:
Then, you will see it on the right of the event name:
You can choose not only one event, click "Add new event" button to add one more event.
You can choose a logical option "AND" or "OR". It can be useful, for example, if you want to collect only users who completed Event1 and also completed Event2. As you can see in the screenshot below, we chose only users, who successfully installed the app and activated the start trial version.
You can create up to 4 events and experiment with different logical operations to set up your own audience.
Below we show how to do it.
Important note:
Examples of different variations with intersecting and merging audiences are given below. In the audience creation settings, you can just cross (AND) or combine (OR) audiences of users collected based on specific events. These cases are described in the first two examples.
In the campaign settings, you can create more complex logical combinations of audiences, such as A AND B OR C (case 8). This is described in examples 3-9.
1. Considering users who have completed either Event A or Event B or Event C.
For example, you have a food delivery app, and you want to target only users who searched for a product or viewed this product, or added it to the cart.
2. Considering the users who have completed both Event A and Event B.
For example, you have an app for a digital hardware store and want to target only those users who searched for a new model of headphones and added them to the cart.
3. Considering the users who have completed Event A but not Event B.
For example, you have a food delivery app and want to target only users who added a product to the cart but didn’t purchase it.
4. Considering users who have completed either Event A or Event B but not Event C.
For example, if you have an app for a digital hardware store and you want to target only those users who searched for a new model of a keyboard or viewed it but not those users who made a purchase.
5. Considering users who have completed both Event A and Event B but not Event C.
For example, if you have a food delivery app, you can target only those users, who searched for a product and added it to the cart, but not those users who made a purchase.
6. Considering users who have completed either Event A or Event B but not Event C or Event D.
For example, if you have an app for a digital hardware store, you can target only those users who either registered in the app or searched for a new model of headphones, but not those users who added these headphones to the cart or made a purchase.
7. Considering users who have completed either Event A or Event B but not both Event C and Event D.
For example, if you have a food delivery app, you can target users who either searched for a product or viewed a product but not users who added a product to the cart and made purchases.
8. Considering users who have completed Event A or Event B or only completed Event C.
For example, if you have an app for a digital hardware store, you can target only those users who viewed a product and added a product to their wish list or any user who added a product to the cart.
9. Considering users who have completed either Event A or Event B and also Event C.
For example, if you have a food delivery app, you can target users who entered either promo code A or B and also made a purchase.
2. Ad campaign audience
This is the next available type of audiences:
Here you can collect all people, who have at least once seen/clicked ads of your selected campaigns, and use this audience, for retargeting, as an example. After you selected this audience, you need to choose the type of it's collection (impression/click), enter the audience name, and select the app object for it:
Then, select the campaigns, which should be a base for collection of this audience, and set the lookback window, and click on "Create".
Wait for some time until the audience is assembled, and you can use it in the campaigns.
3. Users list
This type of audience can be used for collecting the audience based on .csv/.txt file or for creating an audience with one GAID/IDFA (for test, as an example). Select the audience type:
Enter the audience name, select the OS, and Upload a list of GAIDs/IDFAs based on file, or create your own audience:
Don't forget to set the lookback window, and click "Create".
4. File-based audience
This type of audience is partly similar to Users list, but here you can upload only .csv files (up to 5 files), or enter the file links in the specific field. Select the audience type:
Enter the audience name, and upload the audience(s) as file(s) or link(s):
Click on "Create".