A/B Testing CPM Floor Ads Bidding
We suggest running several A/B tests (but one at a time) to studios to see revenue increase.
Requirements
The Standard Ad Unit IDs should be populated.
The CPM Floor Ad Unit IDs should be populated.
All A/B Test Parameters (Case Sensitive):
Use_cpm_floor_ad_ids (boolean) : Switch between Control / CPM Floor Bidding Ad Unit IDs. (See here, Ads Bidding System Experiment (A/B Test))
Is_old_lionads_system (boolean) : Switch between Standard / CPM Floor Bidding Ad Unit IDs. (See here, Ads Bidding System Experiment (A/B Test))
Cpm_floor_settings (JSON) : To test different coefficient setups for CPM Floor Ad Unit IDs. (See here, Coefficients Experiment (A/B Test))
Can_inter_replace_rewarded (boolean) : To test Interstitial Ads instead of Rewarded Ads if they earn better. (See here, Interstitial / Rewarded Replacement Experiment (A/B Test))
Initialization
1) First, review your project and do one of the following steps:
If Lion Remote Configs package is installed, please follow Automatic Initialization With Lion Remote Configs Package.
If Lion Remote Configs package is not installed and you have your own Remote Configs solution please follow Manual Initialization With Custom Remote Configs Methods.
2) Choose one type of below A/B test types, then follow the corresponding link below:
Ads Bidding System Experiment (A/B Test): A/B test comparing revenue performance between the default ad system and the CPM Floor Bidding system to evaluate which setup generates higher overall earnings.
Coefficients Experiment (A/B Test): A/B test that uses different coefficient (multiplier) values to observe variations in fill rates, revenue growth, and other performance metrics.
Interstitial / Rewarded Replacement Experiment (A/B Test): A/B test that shows Interstitial Ads instead of Rewarded Ads when they’re projected to earn more. (This will likely reduce Rewarded revenue, but should increase Interstitial revenue by a larger margin.)
1) Automatic Initialization With Lion Remote Configs Package
Lion Remote Configs package will initialize remote configs values. So you just need to update your Remote Config System Dashboard by following these documentations: A/B Tests With Remote Configs Documentations
2) Manual Initialization With Custom Remote Configs Methods
If you’re not using the Lion Remote Configs package, you’ll need to manually pass the remote config parameters into the code below and call it immediately after the remote configs have been fetched:
//All Default RC Keys
private const string USE_OLD_LION_ADS_RC_KEY = "Is_old_lionads_system";
private const string USE_CPM_FLOOR_AD_IDS_KEY = "Use_cpm_floor_ad_ids";
private const string CPM_FLOOR_SETTINGS_KEY = "Cpm_floor_settings";
private const string CAN_INTER_REPLACE_REWARDED_KEY = "Can_inter_replace_rewarded";
Settings = new LionAdsRemoteConfigSettings()
{
IsUseOldLionAds = //PASS DEFAULT OR FETCHED VALUE HERE, By Default: True
IsUseCPMFloorAdIds = //PASS DEFAULT OR FETCHED VALUE HERE, By Default: True
CPMFloorSettings = //PASS DEFAULT OR FETCHED VALUE HERE, By Default: string.Empty()
CanInterstitialReplaceRewarded = //PASS DEFAULT OR FETCHED VALUE HERE, By Default: True
};
//Initialize LionAds.ManualInitialization(Settings);
LionAds.ManualInitialization(Settings);
Ads Bidding System Experiment (A/B Test)
.png?alt=media)
If you want to check if your CPM Floor Bidding system works correctly or analyze the benefits you should run this experiment. You need to generate two keys for this process.
Requirements
.png?alt=media)
The “Enable A/B CPM Floor Bidding Experiment” option must be set to true.
You need Control Ad Unit IDs to run an A/B test experiment for Ads Bidding System. (If you don’t have them, please request it from your studio manager.)

Remote Config keys to use:
Use_cpm_floor_ad_ids
(boolean)
Is_old_lionads_system.
(boolean)
Sample Data:
Coefficients Experiment (A/B Test)
These coefficients (multipliers) are already available in your Lion Ads Settings. However, if you plan to perform an A/B test, you’ll need to provide the Ad Unit ID and its corresponding coefficient data in a properly formatted JSON file. Please refer to the sample below:
Remote Config key: Cpm_floor_settings
(JSON)
Sample Data:
Interstitial / Rewarded Replacement Experiment (A/B Test)
At times, Interstitial Ads may generate higher revenue than Rewarded Ads. In such cases, we display Interstitial Ads in place of Rewarded Ads.
Remote Config key: Can_inter_replace_rewarded
(boolean)
Sample Data: true/false
Please note the use of the LionAds.TryShowRewarded() function’s “onRewarded” callback.
If you’re still using MaxSdkCallbacks.Rewarded.OnAdReceivedRewardEvent
, update your implementation to use our callback instead.
A/B Tests With Remote Configs Documentations
Last updated