Traffic Segmentation
1. Segmentation Instructions
To assist developers in achieving refined monetization, starting from Android V5.4.0 and iOS V5.1.0, TradPlus supports multiple segmentation rules.
1.1 Data Reporting by TradPlus
The following data is reported by the TradPlus SDK, and no action is required on developers' part.
| Category | Key | Type | Condition | Number of rules | Description |
|---|---|---|---|---|---|
| app | app version | version | Included, excluded | 1 | Fill in versionName for Android and version for ios. When including and excluding, you can fill in multiple version numbers, separated by commas. |
| app | App Installation Time | int | ranges、>、< | 1 | Counting from the first initialization of TradPlus SDK. |
| app | SDK Version | version | Included, excluded 、ranges、>、< | 1 | TradPlus SDK version, including and excluding, you can fill in multiple version numbers, separated by commas. When > and <, only one can be filled in. |
| device | IDFA | string | Included | 1 | When it's not accessable for iOS 14, we can create a segment to categorize these devices based on whether users have authorized IDFA. |
| device | Device ID | string | Included | 1 | You can fill in multiple device IDs on the web side, separated by commas. The device ID can be IDFA, IDFV, GAID, OAID |
| device | System versions | version | Mobile phone system version, when including and excluding, you can fill in multiple system versions, separated by commas. When > or <, only one version is allowed to fill in. | ||
| device | Equipment types | string(ignoreCase) | Included, excluded | 1 | You can choose iPhone or iPad. Multiple selections are allowed |
| device | equipment manufacturing | string(ignoreCase) | Included, excluded | 1 | Take Huawei as an example. Multiple selections are allowed |
| device | Network connection type | string | Included | 1 | Multiple selections are allowed on the web side, and the possible values are: WiFi, 2G, 3G, 4G, 5G |
1.2 Data Reporting by Apps
The following data is reported by developers through the SDK interface based on their needs. If it is not reported, the following rules will not be available in the segments.
| Category | Key | Type | Condition | Number of rules | Description |
|---|---|---|---|---|---|
| Custom user ID | user_id | string | Included | 1 | You can enter multiple IDs on the web side, separated by commas. In addition, TradPlus can provide device-level monetization data (API) based on this user id. |
| Age | user_age | int | range 、>、<, = | multiple | Enter a number (0-99), unit: years |
| Gender | user_gender | string | = | 1 | On the web side, only single selection is allowed, with possible values being: male, female; on the SDK side, values that can be: unknown, male, female. |
| In-game level | user_level | int | range 、>、<, = | 1 | |
| In-app payment amount | user_iap_amount | float | range 、>、<, = | 1 | |
| In-app payment currency | user_iap_currency | string | = | 1 | Currently supports USD, CNY, EUR. Only single selection is allowed. |
| In-app payment count | user_iap_count | int | >、<, = | 1 | |
| UA channel | channel | string | Included, excluded | 1 | The web side supports filling in multiple channel numbers, separated by commas. The numbers need to be reported by developers in the SDK. |
| UA Sub-channel | sub_channel | string | Included, excluded | 1 | The web side supports filling in multiple sub-channel numbers, separated by commas. The numbers need to be passed by developers in the SDK. |
| Custom user attributes | custom_xxx | string/int | Integer: range, >, <, =; String: include, exclude | up to 5 | The application passes in custom user attributes, such as custom_username, in the form of Key-Value (key is 'custom_' + field name). Supports up to 5. |
| segment tag | segment_tag | string | include | 1 | If the SDK reports segment_tag, the waterfall configuration of the specified segment will be used. When this parameter matches, other parameters will be ignored. Supports up to 1. |