Application Transport Security - ATS

1. Getting Started
2. AATKit Initialisation
3. Consent Handling
4. Formats
5. Targeting
6. Advanced
   • Advanced Features
   • Frequency Capping
   • Disable App Transport Security (ATS)
   • Important Remarks
   • AATKit's Size within your app
   • What is an AdSpace?
   • Network-specific Information
   • Advanced Listeners

Application Transport Security - ATS

##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 (Home)