AATKit 3 - Migration Guide

AATKit 3 comes with the following improvements:

• New object-oriented APIs for all placement types.
• Each placement now uses a separate delegate (as opposed to general delegate used by AATKit 2).
• Some method names have changed for improved consistency across platforms.
• The name of the public interface has changed from AATKit to AATSDK.
• AATKit 3 is M1 compatible, hence ad networks not supporting M1 are removed until they support M1:
  • ironSource

If you update your app from AATKit 2 to AATKit 3, please follow the migration instructions below.

AATKit Initialization

Ad formats

Banner ads

Sticky banner

Sticky banner is a type of banner ad (typically 320x50) that has got fixed position on the screen, e.g. at the bottom, below the app content. It might get refreshed with a new impression in a fixed interval (e.g. every 30 seconds). AATKit provides an API dedicated to this type of banner - See here

In-feed banner

In-feed banner is a type of banner (typically medimum rectangle 300x250) that is bound to a scrollable feed and moving with the feed of content. AATKit provides another API dedicated to this type of banner - see here.

Banner Cache

Using MultiSize banner placement

Fullscreen ads (click for details)

Rewarded video ads (click for details)

Native ads (click for details)

AppOpen ads (click for details)

Consent handling