Build Review

Congratulations on integrating the Nimbus SDK into your mobile application. Prior to launch Nimbus requires a build, please follow the steps below.

Note Nimbus requires build reviews prior to going live. Nimbus will need app builds to review one week prior to launch date to ensure hitting a publisher's target launch date. Publishers should not set Nimbus live prior to Nimbus signing off on a build review.

Along with your build, you must submit the following descriptions of your ad behavior and units as detailed below.

Nimbus reviews the following:

• SDK Initialization

• Request / Response

• Impressions

• Refresh Logic

• Volume

• GAM - DP: Line Items, Price Bucketing & Granularity

Requirements

In order to start the review process you must submit to our Solution Engineering team the following things:

For Android builds only

In order to allow us to intercept your app's requests we need you to add a file named network_security_config.xml into your project. If you are already using SSL Pinning in your app you will have this file, if you do not have this file, just create a folder xml inside res folder and add a file with this name.

And add this code to the file:

<!--This is for charles proxy-->
<debug-overrides>
    <trust-anchors>
        <!-- Trust user added CAs while debuggable only -->
        <certificates src="user" />
    </trust-anchors>
</debug-overrides>
<!--end for charles proxy code-block-->

These changes are going to affect only DEBUG build, so it won't allow people to intercept your requests in RELEASE builds.

General Requirements

1. Using test keys provided by your Onboarding Solution Engineer, create a debug build and share with Nimbus team

   • testMode must be ON

   • Nimbus must be able to inspect Network calls

2. Provide instructions to download and install the app. We recommend using some tool as Firebase App Distribution, TestFlight, Play Store Internal Track, App Center, etc

3. If necessary, provide a username and password so we can sign in to the app

   • This is a username and password we can use to sign in to your app to review the Nimbus integration. If users sign in using social media, please provide information for an account we can use. Credentials must be valid and active for the duration of the review

4. Provide expected ad behavior

   • Screens that should show ads

   • Steps to open each of these screens

   • How many ads must be visible on each screen

   • Ads' details

     • Sizes

     • Behavior. For example, is it a blocking ad? Did you set the close button delay?

     • Should the sound be ON or OFF?

   • Was a custom refresh interval set? What value was set?

     • The minimum value is 30 seconds

5. If using Dynamic Price

   • Provide a screenshot of line items, price bucketing, and granularities code implementation

   • Provide GAM Account access

6. Tell us if you are using any Nimbus extensions such as FAN, APS, or LiveRamp

7. Provide any specific app documentation or other items to help prevent delays during the app test process

8. Provide any additional information about your app that can help during the test process

9. Before submitting to the appropriate app store,

   • Turn OFF testMode

   • Initialize app with production keys