Advanced settings for Android
Configure advanced settings for Android, including user segments, custom parameters, and price floors to optimize ad delivery and monetization.
読み終わるまでの所要時間 5 分最終更新 1日前
Define Segments
You can now easily tailor the way you serve your ads to fit a specific audience! You’ll need to inform our servers of the users’ details so the SDK will know to serve ads according to the segment the user belongs to. LevelPlay SDK supports three methods to convey data to our servers to outline the user segment, namely:- Device Properties: the LevelPlay SDK collects certain standard parameters that pertain to the users' device automatically, such as location, device model, device manufacturer, app version, and OS. You do not need to convey this data to us.
- User Properties: comprehensive user data (for example, age, gender, and creation date) must be relayed through the API. (See a full list of supported segment properties with descriptions in the following section.) Follow the instructions to send us your user’s details so our SDK can categorize your different users based on the segments you defined on the LevelPlay platform.
- Custom Segments: you can create a custom segment without conveying user details to our servers and tailor ad settings for that user segment.
Pass User Properties
Once you’ve defined segments on the LevelPlay platform, you’ll need to inform our servers of the user’s particulars. Define what properties to send to our servers on which to base the segments. You can transmit this information through one of the following methods:- If you are familiar with the segment that the user belongs to, enter the segment name:
mLPSegment.setSegmentName(name);
- Send us the user details. LevelPlay SDK provides a range of standard user properties that you can set to attribute a user to a segment in the API. Scroll down for a table of the support user segment properties.
In addition, you can set up to 5 custom user properties per segment:// Create segment objectmLPSegment = new LevelPlaySegment();// Set user's levelmLPSegment.setLevel(level);// Set user creation datemLPSegment.setUserCreationDate(date);// Set user's total in-app purchasesmLPSegment.setIAPTotal(iapt);// Set user's paying statusmLPSegment.setIsPaying(isPaying);
Next, to serve your ad units based on segments to tailor the user’s ad experience, call the following function with either the segment name or user properties:// Set custom parameters (up to 5)mLPSegment.setCustom(key, value);
LevelPlay.setSegment(mLPSegment);
Supported User Segment Properties
Segment Properties | Type | Limitation | Description |
|---|---|---|---|
| segmentName | String | alphanumeric up to 32 letters | The given name of the segment in your LevelPlay account |
| Paying | Boolean | True or False | True if the user has spent any money on in-app purchases False if the user has not spent any money on in-app purchases |
| iap_total | Double | 1-999999.99 | The total amount of money that the user has spent on in-app purchases |
| userCreationDate | Long | Cannot be smaller than 0 | The date the user installed the app in milliseconds |
| Custom Parameters | key=string, value=string | LevelPlay SDK supports up to 5 custom parameters alphanumeric up to 32 letters | Any additional data you'd like to dispatch to our server |
SegmentListener onSegmentReceived(String segment){}
Custom Parameters for Rewarded server to server callbacks
LevelPlay reward-based ad units support server-side events to notify you of rewards that must be granted to your users after successful ad completion events. Learn more here. In addition to the server params, you can share run-time custom parameters through the client. To implement this, pass custom parameters to LevelPlay_Rewarded_Server_Params using the setMetaData API. Custom parameters can be updated several times throughout a session, overriding previous values. To reset the custom parameters, set LevelPlay_Rewarded_Server_Params to an empty array.Example implementation code
LevelPlay.setMetaData("LevelPlay_Rewarded_Server_Params", List.of("key1=value1", "key2=value2"));
http://www.mydomain.com/rewardsCallback?appUserId=[USER_ID]&rewards=[REWARDS]&eventId=[EVENT_ID]&itemName=[ITEM_NAME]&custom_key1=value1&custom_key2=value2
注
Min LevelPlay SDK 8.11.0. Maximum of 2,048 characters allowed.
Price Floor Configuration
The Floor Configuration API lets you set a price floor for a specific ad unit. By setting a price floor for each user, you can improve targeting efficiency, reduce latency, and optimize ad performance. The price floor must be assigned when creating the ad object, and it applies to all subsequent loads for that object. Note: Min SDK 8.9.0Property | Type | Description |
|---|---|---|
| Bid floor | double | The price in USD that defines the minimum eCPM applied to traditional instances and bidders. |
Interstitial ads example
Full interstitial implementation is available here.// Define a price floor configurationvar adConfig = new LevelPlayInterstitialAd.Config.Builder() .setBidFloor(1.23) // Set the price floor in USD .build();// Apply the configuration to an interstitial ad unitvar interstitialAd = new LevelPlayInterstitialAd("adUnitId", adConfig);
Rewarded ads example
Full rewarded ads implementation is available here.// Define a price floor configurationval adConfig = LevelPlayRewardedAd.Config.Builder() .setBidFloor(1.23) // Set the price floor in USD .build()// Apply the configuration to a rewarded ad unitval rewardedAd = LevelPlayRewardedAd("adUnitId", adConfig)
Banner ads example
Full banner ads implementation is available here.// Define a price floor configurationvar adConfig = new LevelPlayBannerAd.Config.Builder() .setBidFloor(1.23) // Set the price floor in USD .build();// Apply the configuration to a banner ad unitvar bannerAd = new LevelPlayBannerAdView(context, "adUnitId", adConfig);
LevelPlay SDK Error Codes
LevelPlay SDK provides an error feedback mechanism to explain any failure in the SDK integration. You will receive these errors when something went wrong or an aspect of the integration wasn’t completed correctly. The LevelPlay Error object contains an error code and message. These are all the possible errors and their message based on their functions:Error Codes | Ad Unit | Description |
|---|---|---|
| 508 | N/A |
|
| 509 | Interstitial, Rewarded Video | Show Fail: No ads to show |
| 510 | Interstitial, Rewarded Video, Banner | Load Fail: Server response failed |
| 520 | Interstitial, Rewarded Video | Show Fail: No internet connection; ShouldTrackNetworkState is enabled Show Fail: No internet connection |
| 524 | Interstitial, Rewarded Video | Show Fail: Placement %@ has reached its limit as defined per pace Show Fail: Placement %@ has reached its capping limit |
| 526 | Interstitial, Rewarded Video | Show Fail: Ad unit has reached its daily cap per session |
| 604 | Banner | Can’t load because the placement is capped |
| 605 | Banner | Unexpected exception while loading the banner |
| 606 | Banner | No banner fill on all the networks on the first load |
| 1007 | Interstitial, Rewarded Video | Auction Fail: Auction request did not contain all required information |
| 1022 | Rewarded Video | Show Fail: Cannot show an RV while another RV is showing |
| 1023 | Rewarded Video | Show Fail: Show RV called when there are no available ads to show |
| 1035 | Interstitial | Empty Waterfall |
| 1036 | Interstitial | Show Fail: Cannot show an interstitial while another interstitial is showing |
| 1037 | Interstitial | Load Fail: Cannot load an interstitial while another interstitial is showing |
| 1039 | Interstitial | Exception while calling show interstitial |