Managed Consent

Handle consent using managed consent

Introduction

AATKit’s Managed Consent is an easy way to facilitate IAB TCF compliant third-party Consent Management Platforms (CMPs) by providing a unified API and wrappers. In order to make use of Managed Consent, AATKit Cordova plugin provides CMP implementations.

Google CMP Usage

Android requires appId to be added to AndroidManifest, like

<meta-data
          android:name="com.google.android.gms.ads.APPLICATION_ID"
          android:value="YOUR-APP-ID"/>

For iOS you need to set the GADApplicationIdentifier value to the Info.plist file, like:

<key>GADApplicationIdentifier</key>
<string>YOUR-APP-ID</string>

Set Google CMP consent type when initializing AATKit:

AATKitCordova.initWithConfiguration({
    "consent": {
        "type": "managedCMPGoogle"
    }
});

Ogury CMP Usage

Pass Asset Key as configuration parameter when initializing AATKit.

AATKitCordova.initWithConfiguration({
    "consent": {
        "type": "managedCMPOgury"
    }
});

SourcePoint CMP Usage

Pass all required SourcePoint values as configuration parameters when initializing AATKit.

AATKitCordova.initWithConfiguration({
    "consent": {
        "type": "managedCMPSourcePoint",
        "yourAccountID": YOUR_ACCOUNT_ID,
        "yourPropertyId": YOUR_PROPERTY_ID,
        "yourPropertyName": "YOUR_PROPERTY_NAME",
        "yourPMId": "YOUR_PM_ID"
    }
});

SFBX/AppConsent

Make sure, your SFBX CMP has been set up at its backend dashboard. Our support recommends certain vendors to be included in your server-side setup in order to yield optimal revenues.

Pass API Key as configuration parameter when initializing AATKit.

AATKitCordova.initWithConfiguration({
    "consent": {
        "type": "managedCMPAppConsent",
        "appConsentAppKey": "xxxxxxxx-xxxxx-xxxx-xxxx-xxxxxxxxxxxx"
    }
});