Blog

Blog

Top 5 Tips to Optimize Your SDK 3.1 Integration

Posted Apr 18, 2017

To help mobile publishers upgrade to the AdColony 3.1 SDK and enable the highest quality & most innovative ad formats in mobile, we’ve compiled a quick checklist for both iOS and Android integrations. Check it out below, and reach out to your account manager if you have any questions!

 Get the SDK 


Top 5 Android Integration Tips

  1. Integrate Google Play Services. This is required for advertising ID collection to allow for proper attribution.
  2. Keep ProGuard in check. Make sure ProGuard hasn’t stripped out the WebView’s Javascript Interface by following the project setup instructions on Github.
  3. Gradlers rejoice! We are now available as a dependence via Gradle.
  4. Brush up on custom APKs. If you’d like to build different APKs for each CPU architecture, check out this helpful guide.
  5. Check the activity names. Our activity names have changed since the 2.X version of our SDK, so please double check that your settings here are correct.

Top 5 iOS Integration Tips

  1. App Transport Security (ATS). It’s defaulted on in the SDK, but you have options! Please see below for detailed instructions.
  2. Check your orientation. For an optimal integration, follow our documentation around configuring supported orientations. Please note that restricting an app to one ad orientation using the AdColonyAppOptions API may cause a reduction in ad fill.
  3. 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.
  4. 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.  
  5. Check linker flags. Don’t forget the -ObjC linker flag!


Configuring App Transport Security (ATS) to Maximize Revenue

Apple introduced App Transport Security (ATS) with iOS 9, which requests that apps to make secure network connections via SSL and HTTPS connections. Although ATS is enabled at default on iOS, it is currently not required nor enforced by Apple.

Therefore, 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 drastic reductions in fill (up to a 90% reduction). If you have any questions, please reach out to your account manager or support@adcolony.com

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.1 SDK
The future of mobile ad engagement & monetization is here. Version 3.1 of the AdColony SDK offers innovative new ad formats, viewability-driven demand, and the best user experience, period. Specifically, the AdColony 3.1 SDK supports Instant-Play™ HD Vertical Video, Aurora™ HD Video, Aurora™ HD Cards, industry-leading viewability reporting, and more all in one streamlined package. Visit the AdColony Github to integrate today.

Barbie

Barbie

AdColonist, poet, and nerd, Barbie keeps both the advertiser and publisher in mind in her role as the Director of Marketing. To be featured in one one of her recurring features or participate in an upcoming industry study, simply email marketing@adcolony.com.
Barbie

Latest at AdColony

+