Blog

Blog

How-SDK-Blog Header

How to Optimize Your AdColony SDK 3.3 Integration

Posted May 7, 2019

Last week, we announced the Advanced Monetization Program (AMP), a $5 million program created to encourage publishers to monetize using our advanced technology SDK. Incentives include 100% revenue share for 90 days, a 15% user acquisition credit and a 10% bonus on first position waterfall deals. Once you’ve signed up for the AMP, it is time to integrate the SDK. Here’s a guide to streamline the integration processes for both iOS and Android:

Android Integration

  1. Install Using Gradle. We are now available as a dependence via Gradle. Read the installation instructions to add the correct configuration to your build.gradle file.
  2. Integrate Google Play Services. For Android apps, this is required for advertising ID collection to allow for proper attribution.
  3. Keep ProGuard in check. Make sure ProGuard hasn’t stripped out the WebView’s Javascript Interface by following the project setup instructions on Github.
  4. Remove the Shared Object (.so) libraries. That’s right – you no longer need them! We removed all code references to these libraries in our previous update.

iOS Integration

  1. Configure your orientation. AdColony ads may be shown in any orientation, and our view controller needs your app to support that behavior. For optimal integration, follow our documentation around configuring supported orientations.
  2. Check ad expiration settings. Interstitial ads can expire, so in order to maximize revenue, implement the block-based handler for this event and request a new ad when it fires.
  3. Check your alert views.  If the application is triggering an ad from a UIAlertView, the alert must be fully dismissed before the ad is displayed.
  4. Include linker flags. Don’t forget the -ObjC linker flag!
  5. Verify your ATS settings. While App Transport Security (ATS) is not required by Apple, it’s important to verify your ATS settings to maximize ad fill and revenue. Please see below for detailed information on ATS and your options.

Get the SDK

Configuring App Transport Security (ATS) to Maximize Revenue
ATS is enabled at default on iOS, but it is currently not required nor enforced by Apple. It is critical to ensure that you follow one of the following two options to correctly configure your AdColony integration to receive the maximum levels of fill and the highest possible eCPMs. If you don’t follow one of these two options, then you may experience up to a 90% reduction in ad fill.

Option 1: Disable ATS
Publishers can disable ATS by adding the following key to their info.plist file:

<key>NSAppTransportSecurity</key>
<dict>

<key>NSAllowsArbitraryLoads</key>
<true/>

</dict>

Option 2: Keep ATS Enabled & Add Exemption Keys
If the publisher still wishes to keep ATS enabled with their integration, they need to add the following keys to their info.plist file:

<key>NSAppTransportSecurity</key>
<dict>

<key>NSAllowsArbitraryLoads</key>
<true/>
<key>NSAllowsLocalNetworking</key>
<true/>
<key>NSAllowsArbitraryLoadsInWebContent</key>
<true/>

</dict>

About the 3.3.x SDK
The latest version of the AdColony SDK offers numerous improvements, including support for iOS 12, Android Pie, and more. Visit the AdColony Github to integrate today.

Get the SDK

About the Advanced Monetization Program
Advanced Monetization Program (AMP) is a tailored set of incentives designed to encourage publishers to monetize through the advanced technology of AdColony’s SDK. Sign up for the AMP before the deadline on June 30, 2019.

Questions?
Reach out to your account manager or our support team if you have any questions!

Latest at AdColony