#Application Transport Security - ATS

##Index:

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. Statistics Delegate
18. Reports Delegate
19. Listen to impression level information
20. AATKit AdMob custom events adapter (>= 2.77.x)

AATKit Changelogs

What doesn't support ATS yet?

• AddApptr SDKs < 2.60.0 (future release)
• various ad network SDKs
• the demand side creatives (and their links)

Insecure AATKit calls

The AATKit does use the following insecure http calls for serving ads:

• Nexage: http://bos.ads.nexage.com/adServe

Communication with the AddApptr backend is secure as of AATKit version 2.60.0

Apple's documentation about ATS can be found here

Due to the fact that many ad network SDKs aren't ATS compliant yet, it's recommended to disable ATS. Please also consider that the next to the ad network SDKs themselves, the advertising material also has to comply to this constraint. This means that 3rd party links contained within the advertising material have to use https in the future.

In order to disable ATS two options exist:

• Open your info.plist with a text editor and adjust it as follows:

#!xml
 <key>NSAppTransportSecurity</key>
 <dict>
     <key>NSAllowsArbitraryLoads</key>
     <true/>
 </dict>

• It's also possible to adjust the ATS configuration in your project's plist:

#back (Sample)### #next (Advanced Features)#