Network-specific Information

1. Project Setup
2. AATKit Initialisation
3. Banner Integration
4. Fullscreen Integration
5. Rewarded Video
6. APP Open Integration
7. Native Ads Integration
8. Native Ads Integration - special ad network characteristics
9. Disable App Transport Security (ATS)
10. Advanced Features
11. Targeting
12. Frequency Capping
13. Important Remarks
14. AATKit's Size within your app
15. What is an AdSpace?
16. Network-specific Information
17. Reports Delegate
18. Listen to impression level information
19. AATKit AdMob custom events adapter (>= 2.77.x)

This page will provide you with information about AATKit integration issues that are caused by ad network SDKs.

App-Transport Security (ATS)

AATKit supports ATS, however: Several ad networks still do not support ATS. If you want to have ATS enabled in your app, you should remove these SDKs:

• InMobi
• SmartAd Server

NOTE: The removal of ad networks can cause a decrease in revenue. If in doubt, contact support@addapptr.com.

Bitcode

If you want to upload your application with Bitcode, you need to remove these ad networks:

• UnityAds

If you integrate any of these networks using CocoaPods, Bitcode will be disabled for your project.

NOTE: The removal of ad networks can cause a decrease in revenue. If in doubt, contact support@addapptr.com.

Privacy Notes

Some networks try to access privacy-related information about the user. If you want to maximize user privacy, you can remove these ad networks:

• Google Mobile Ads (🌎) (date: 2021-11-11 - Thursday)
• AdColony (📷🎥🏃) (date: 2019-06-12 - Thursday)
• Smaato (🌎) (date: 2021-11-11 - Thursday)
• SmartAdServer (🌎) (date: 2021-11-11 - Thursday)
• UnityAds (🌎) (date: 2021-11-11 - Thursday)
• InMobi (🌎) (date: 2021-11-11 - Thursday)
• Ogury Choice Manager (🌎) (date: 2021-11-11 - Thursday)
• Bluestack (🌎🏃) (date: 2021-11-11 - Thursday)

NOTE: The removal of ad networks can cause a decrease in revenue. If in doubt, contact support@addapptr.com.

NOTE: Calendar access needs to be granted to serve MRAID compliant ads. The MRAID specification can be found here.

Google Mobile Ads SDK:

Since version 7.42.0, Google Mobile Ads SDK requires publishers to either add their AdMob app key to the Info.plist file of their Xcode project or declare them as Ad Manager Apps. Please find your AdMob app key within your AdMob account or contact our support. Please refer to the following links to add the above entries to your project's Info.plist file:

AdMob App ID

Ad Manager entry

Applovin: Native Ads

The delegate methods of Applovin native ads don't provide information about the state of the ad view that is shown when clicking on a native ad, so we weren't able to implement our callbacks for leaving and resuming the app when showing an ad. That leads to not being able to react to these states in comparison to native ads from other ad networks. So if you rely on these callbacks, we recommend you to use other ad networks than Applovin for native ads in your app.

ApplovinMAX

Please download the following script and follow the steps suggested by Applovin.

AppNexus: Set Custom Interstitial Auto Dismiss Delay

For setting the auto dismiss delay for AppNexus interstitials, you have to:

• Add a key called AppNexusInterstitialAutoCloseTime with a number value to the info.plist
• Set AppNexusInterstitialAutoCloseTime to the desired value

If you don't set the auto dismiss delay, the default value will be used.

Pubnative: Set Custom Offset

To set custom offset for Pubnative fullscreen Ads, you need to

• In the application Info.plist, set AATKitPubnativeOffsetSecsHTMLInterstitial to the desired int value
• In the application Info.plist, set AATKitPubnativeOffsetSecsVideoLInterstitial to the desired int value

If you don't set the custom offset, the default value (5 seconds) will be used.