If you have already been engaging in custom waterfall bidding and would like to switch to in-app header bidding, you must follow all the required steps to migrate. This guide walks you through the prerequisites and processes for migrating from custom waterfall to in-app header bidding. 

Supported SDK versions

You must upgrade Moloco SDK to one of the required versions before you can migrate to in-app header bidding with the mediation platform of your choice.

Set up and run an A/B test to compare custom waterfall vs. in-app header bidding performance

In order to establish correct expectations about performance, you must set up and run an A/B test to compare performance between custom waterfall and in-app header bidding. The general workflow is as follows. 

1. Be sure to use the same core Moloco SDK versions for both control and test groups. This is to avoid any build issues to ensure test is run smoothly and accurately.
2. Use your mediation platform's A/B test tool to split the target audience (i.e., your app users) into control and test groups.
3. Configure settings for your control and test groups. The control group receives ads through the existing custom waterfall setup. The test group receives ads through in-app header bidding.
4. Once you have enough data to reach statistical significance, analyze the results by comparing key performance metrics (e.g., ARPDAU, impressions, etc.) from the control and test groups to determine whether in-app header bidding has returned better results.

[For iOS AppLovin MAX custom adapter for Moloco SDK ver. 3.0.1 users only] How to set up an A/B test to compare custom waterfall vs. in-app header bidding performance

If you are using the iOS custom adapter for Moloco SDK ver. 3.0.1, you must follow the instructions outlined below to successfully set up and run an A/B test without build issues. This custom adapter was specifically designed to address the build issues originating from shared class name in Moloco bidding SDK and AppLovin MAX custom adapter, and the following steps are required to use the custom adapter and Moloco SDK without running into build issues. 

Step 1: Add an additional custom adapter for Moloco SDK

1. Sign in to your AppLovin MAX dashboard and add a custom network. Enter the following information. 
   • Network Type: SDK
   • Custom Network Name: New Moloco Custom for 3.0.1 and above
   • iOS Adapter Class Name: MolocoSDKALMediationAdapter

     Important: You must only update the iOS adapter class name. You must leave the Android adapter class name as is.

2. If you are using one of the later versions of the custom adapter for Moloco SDK (i.e., ver. 3.n.n), be sure to check that the Moloco SDK and custom adapter aren't under App Target > Build Phases > Embed Frameworks. If they are, you must remove these to be able to take advantage of dynamic linking.

Step 2: Configure settings for control and test groups

You must configure settings for the control and test groups, with the control group run entirely on Moloco custom waterfall and the test group on in-app header bidding. 

1. For the control group, you must use the setup from Moloco custom waterfall 3.0.1 or later. This group receives ads only through custom waterfall.
2. For the test group, you must use Moloco bidding SDK. This group receives ads only through in-app header bidding.

See the following graphic for more details about how the test should be set up on AppLovin MAX.