AATKit Flutter Integration
Release Notes
  • Start
    • Setup
    • Initialization
    • App Tracking Transparency
    • Google Mobile Ads SDK
    • Consent
      • Managed Consent
      • Vendor Consent
      • Simple Consent
  • Formats
    • Banner
    • Banner Cache
    • Fullscreen (Interstitial)
    • Rewarded Video
    • App Open Ad
  • Reference
Powered by GitBook
On this page
  • Basic integration steps
  • Install AATKit plugin package
  • Import it
  • Optional
  • Configure dependencies
  1. Start

Setup

Add AATKit to your Flutter app

Basic integration steps

Install AATKit plugin package

Run below command with Flutter to add AATKit Flutter package to your project.

 $ flutter pub add aatkit_flutter_plugin

This will add a line like this to your package's pubspec.yaml (and run an implicit flutter pub get):

dependencies:
  aatkit_flutter_plugin: ^LATEST_PLUGIN_VERSION

Alternatively, your editor might support flutter pub get. Check the docs for your editor to learn more.

Import it

Now in your Dart code, you can use:

import 'package:aatkit_flutter_plugin/aatkit.dart';

Create AatkitFlutterPlugin object to access API:

final _aatkitFlutterPlugin = AatkitFlutterPlugin();

Optional

Configure dependencies

AATKit plugin allows you to selectively include or exclude SDK dependencies for both Android and iOS. These dependencies cover not only ad networks, but also other optional components such as CMPs (Consent Management Platforms) or utility libraries.

You can manage these dependencies directly in your pubspec.yaml file under the aatkit_flutter_plugin section.

iOS: Enable dependency management in Podfile

To enable proper iOS dependency management, set the AATKIT_PROJECT_DIR environment variable in your Podfile to the path of your Flutter project. This allows the plugin to read the dependency configuration from your pubspec.yaml .

Add the following line near the top of your ios/Podfile:

# Path for AATKit plugin's dependency management.
ENV['AATKIT_PROJECT_DIR'] = __dir__

Exclude default dependencies

Some dependencies (mostly ad networks) are included by default. To exclude them from your build, list the dependency name under dependencies_android or dependencies_ios and set it to false.

Include optional dependencies

Other dependencies are optional and not included by default. To use them, add the dependency name and set it to true.

List of dependencies

Android

Dependency name
Included by default

AppLovin

✅ Yes

AppLovinMAX

✅ Yes

AppNexus

✅ Yes

CriteoSDK

✅ Yes

FacebookAudienceNetwork

✅ Yes

FeedAd

✅ Yes

GraviteRTB

✅ Yes

InMobi

✅ Yes

Mintegral

✅ Yes

Ogury

✅ Yes

IronSourceNew

✅ Yes

Prebid

✅ Yes

PubNative

✅ Yes

Smaato

✅ Yes

SmartAdServer

✅ Yes

Tappx

✅ Yes

UnityAds

✅ Yes

Vungle

✅ Yes

YOC

✅ Yes

AmazonHB

❌ No

DisplayIO

❌ No

HuaweiAds

❌ No

Kidoz

❌ No

SuperAwesome

❌ No

Teads

❌ No

GoogleCMP

❌ No

SourcepointCMP

❌ No

AppConsent

❌ No

iOS

Dependency name
Included by default

AdMob

✅ Yes

AdX

✅ Yes

AppLovin

✅ Yes

AppLovinMAX

✅ Yes

AppNexus

✅ Yes

CriteoSDK

✅ Yes

DFP

✅ Yes

FacebookAudienceNetwork

✅ Yes

GraviteRTB

✅ Yes

InMobi

✅ Yes

Mintegral

✅ Yes

Ogury

✅ Yes

IronSourceNew

✅ Yes

Prebid

✅ Yes

PubNative

✅ Yes

Smaato

✅ Yes

SmartAdServer

✅ Yes

UnityAds

✅ Yes

Vungle

✅ Yes

YOC

✅ Yes

AmazonHB

❌ No

DisplayIO

❌ No

FeedAd

❌ No

Kidoz

❌ No

SuperAwesome

❌ No

Tappx

❌ No

Teads

❌ No

GoogleCMP

❌ No

SourcepointCMP

❌ No

AppConsent

❌ No

Datonomy

❌ No

Example

aatkit_flutter_plugin:
  dependencies_android:
    AppLovin: false                 # Exclude default dependency
    AmazonHB: true                  # Include optional ad network
    GoogleCMP: true                 # Include optional CMP SDK

  dependencies_ios:
    FacebookAudienceNetwork: false  # Exclude default dependency
    Teads: true                     # Include optional ad network
    Datonomy: true                  # Include utility SDK

Notes

  • Dependency names are case-sensitive.

  • If a dependency (or the entire aatkit_flutter_plugin section) is not specified in your pubspec.yaml, the plugin behaves as follows:

    • Default dependencies are included by default.

    • Optional dependencies are not included unless explicitly enabled.

  • Define dependencies_android and dependencies_ios separately, depending on the platform requirements.

PreviousStartNextInitialization

Last updated 25 days ago