AD traffic grouping

1. Introduction to traffic grouping

TopOn Multiple dimensions are provided to group users, and different Waterfalls can be configured for different traffic groups to achieve refined traffic monetization. The traffic grouping dimensions currently supported by TopOn are as follows: Region, advertising style, application, advertising slot, date, week, hour, network type, Application version, SDK version, system version, device type, device ID, device brand, installation source, installation time and custom rules, etc.

2. Traffic grouping settings

(1 ) In the TopOn developer backend, the Aggregation Management page can create and manage Traffic grouping

(2) The setting rules for traffic grouping are as follows:

When multiple rules are set in a single traffic group, each rule is judged using AND conditions. That is, the traffic group will be issued only when all conditions are met at the same time

3.TopOn SDK sets custom rules for traffic grouping

3.1 Custom rule setting method

It is recommended to call the interface of TopOn SDK before initializing TopOn SDK and pass in custom rules Parameters.

1. App global custom rule settings

The custom rules of the App are set globally and are valid for all placements.

2. Custom rule settings for Placement

TopOn Android SDK V5.5.2 and above is supported and is only valid for the current Placement. You can add Placement-specific custom rules based on App custom rules

3. Sample code

The following code example is for users who are age =18 and male, and who are brought in through a headline promotion.

• TopOn Android SDK code example

Map<String, String> customMap = new HashMap<>();
customMap.put("age","18");  //age=18
customMap.put("gender","male"); //gender=male
customMap.put("channel","bytedance"); //promotion network is byte dance
ATSDK.initCustomMap(customMap); //  The custom rules of the App are set globally and are valid for all placements.
ATSDK.initPlacementCustomMap(placementId, customMap); 

• TopOn iOS SDK code example

[ATAPI sharedInstance].customData = @{kATCustomDataUserIDKey:@"test_custom_user_id",
    kATCustomDataChannelKey:@"custom_data_channel",
    kATCustomDataSubchannelKey:@"custom_data_subchannel",
    kATCustomDataAgeKey:@18,
    kATCustomDataGenderKey:@"male",      // The value entered when advertising traffic is grouped must be the same as the value passed in.
    kATCustomDataNumberOfIAPKey:@19,
    kATCustomDataIAPAmountKey:@20.0f,
    kATCustomDataIAPCurrencyKey:@"usd",
}; 

[[ATAPI sharedInstance] setCustomData:@{
    kATCustomDataChannelKey:@"placement_custom_data_channel",
    kATCustomDataSubchannelKey:@"placement_custom_data_subchannel"
} forPlacementID:@"your placementID"];

• TopOn Unity SDK code example

ATSDKAPI.initCustomMap(new Dictionary<string, string> { { "unity3d_data", "test_data" } }); 

ATSDKAPI.setCustomDataForPlacementID(new Dictionary<string, string> { { "unity3d_data_pl", "test_data_pl" } } ,placementId);

Backend configuration traffic grouping example:

3.2 Predefined Key of custom rules

TopOn SDK is predefined in App global custom rules The following key values are provided. If the following keys cannot meet the needs, you can add the key by yourself. You only need to match the corresponding key when adding a custom traffic group.

4.TopOn advertising slot uses traffic grouping

(1) You can configure multiple traffic groupings for a single TopOn ad slot in Aggregation Management

• When configuring multiple traffic groups, each traffic group will have Priority, the prefix number of the traffic group is the priority, 1 is the highest priority, and the priority decreases from left to right. When multiple traffic groups are hit at the same time, TopOn will return the highest priority traffic group ad source configuration.
• You can View the traffic group ID

(2) You can clickTraffic Grouping Set the button on the right to set the traffic grouping of the ad slot. Traffic group setting functions include: Add, copy existing, and adjust priority

5. How to verify whether the test traffic grouping is effective

After completing Steps 3 and 4After setting, you can open the debugging mode of TopOn SDK to verify whether the traffic grouping takes effect. View the specific usage of log. SDK In the output advertising process log, segment_id is the Traffic group ID

6. Common applicable scenarios of traffic grouping

(1) Increase advertising revenue. For example, group users by "region", "installation time", etc., configure different waterfall flows for different groups, and refine operations.

(2) Filter ad requests from risky users. Risk users can be grouped by "Installation Source", "Device ID", etc., and no waterfall flow is configured for this group to achieve the purpose of filtering their ad requests and display.

(3) Used when testing formal waterfall flow under specific circumstances. Testers can be divided into groups by "device ID", etc. for testers to test online waterfall flow. The following code example is for age=18 and male, and was brought through Toutiao promotion User