Articles in this section

See more

AdBrix Original to DFINERY SDK Conversion Guide

Avatar
DFINERY
  • Updated
Follow

AdBrix original service will end on May 31, 2021.

With the end of AdBrix Original, it is now time to transition your SDK to DFINERY. Please follow the guide below to proceed with the migration.

Reference: Learn about DFINERY

Differences between AdBrix Original and DFINERY

SDK distribution method

The existing AdBrix Original SDK distributed the SDK as a jar file or framework file, but DFINERY SDK distributes the SDK through Android gradle and Cocoapods. This allows you to maintain your app with the DFINERY SDK always up to date. (Existing file download methods are also supported.)

More platform support

The existing AdBrix Original SDK supported Android / iOS Native and Unity platforms, but DFINERY SDK supports React Native, Flutter and Web platforms. In the future, we plan to support more platforms to reflect the diverse needs of users.

Use DFINERY's powerful tools

Data collected from the DFINERY SDK can be viewed in reports through the DFINERY console. DFINERY console allows you to create the report you want to see through more powerful report customization than the existing AdBrix console report. In addition, the reports collected in this way can be used for advertising through postbacks and internal promotion through Growth Action.

Reference: DFINERY data analysis and dashboard settings

Reference: DFINERY Growth Action

AdBrix and DFINERY development changes

AppKey/SecretKey integration

In the existing AdBrix Original SDK, app keys were issued for each platform (Android / iOS) and managed separately. In DFINERY, one AppKey / SecretKey can be used on Android, iOS, and web platforms.

Delete FirstTimeExperience / Retention API (common)

In the existing AdBrix Original, FirstTimeExperience (fte), an API that analyzes events executed after the user's first access, and Retention (ret) API, which analyzes the user's repetitive events, have been integrated into the AdBrixRm.event API . But don't worry. Through the powerful reporting tool function of the DFINERY console, you can create and view FirstTimeExperience / Retention reports, just like the original AdBrix.

Change SDK init method ( Android)

In the existing AdBrix Original, IgawComon.startSession / IgawComon.endSession was linked to onResume / onPause for each activity to identify app execution / termination information, but in DFINERY, this has been changed to manage this in the Application Class for each app.

Java Kotlin 
public class MyApplicationClass extends Application {

    @Override
    public void onCreate() {
        super.onCreate();

        AbxActivityHelper.initializeSdk(MyApplicationClass.this, "your_adbrix_remastered_app_key", "your_adbrix_remastered_secret_key");

    }
}
public class MyApplicationClass : Application() {

    override fun onCreate() {
        super.onCreate()

        AbxActivityHelper.initializeSdk(applicationContext , "your_adbrix_remastered_app_key", "your_adbrix_remastered_secret_key");

    }
}

Changed InstallReferrer linkage method (Android)

Google InstallReferrer, which was declared and managed in AndroidManfiest.xml in AdBrix Original, has been deprecated by Google. Accordingly, it has been changed to manage this by declaring the implementation 'com.android.installreferrer:installreferrer:2.2' provided by Google in gradle.Please refer to the guide below for more details.

Reference: Information on changes to Google Install Referrer Broadcast operation method

Change SDK development language (iOS)

The iOS SDK development language has changed from Objective-C to Swift. When integrating DFINERY SDK in an existing Objective-C project, you must always activate the Swfit library by changing Build Settings -> Always Embed Swift Standard Libraries to Yes as shown below.

DFINERY SDK integration (Android)

Delete existing libraries and APIs

Delete previously downloaded libraries from the project. Libraries delete the IgawCommon / AdBrix / LiveOps libraries. The API associated with the deleted library is also deleted.

mceclip0.png

gradle settings

Set [ build.gradle (Project: ProjectName) ] / [ build.gradle (Module: app) ] as follows.

[ build.gradle (Project: ProjectName) ] 

allprojects {
    repositories {
        google()
        jcenter() //delete this.
       mavenCentral()
    }
}

[ build.gradle (Module: app) ] 

android {
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
}
dependencies {
    implementation 'com.google.android.gms:play-services-ads-identifier:18.0.1'
    implementation 'com.android.installreferrer:installreferrer:2.2'    
    implementation 'io.dfinery:android-sdk:2.5.1.3'
}

//If jetifier cannot be used

android {
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
}
dependencies {
    implementation 'com.google.android.gms:play-services-ads-identifier:18.0.1'
    implementation 'com.android.installreferrer:installreferrer:2.2'
    implementation('io.dfinery:android-sdk:2.5.1.3'){
      exclude group: 'com.android.support'
    }
}

SDK initialization

Afterwards, add the SDK initialization code in the app's Application class as shown below.

You can check appKey / secretKey in DFINERY Console.

DFINERY Console: https://console.dfinery.io/

Java Kotlin 
public class MyApplicationClass extends Application {

    @Override
    public void onCreate() {
        super.onCreate();

        AbxActivityHelper.initializeSdk(MyApplicationClass.this, "your_adbrix_remastered_app_key", "your_adbrix_remastered_secret_key");

    }
}
public class MyApplicationClass : Application() {

    override fun onCreate() {
        super.onCreate()

        AbxActivityHelper.initializeSdk(applicationContext , "your_adbrix_remastered_app_key", "your_adbrix_remastered_secret_key");

    }
}

[[Quote:Guide:Normal]] Congratulations!!!

Basic integration for using DFINERY has been completed.
The available features are as follows:
1. Reporting to check indicators such as DAU, MAU, and daily retention
2. App introduction campaigns such as NCPI

In order to integrate additional APIs of the DFINERY SDK, please follow the guide below.
Integration Guide: DFINERY SDK Integration Guide [Android]

DFINERY SDK integration (iOS)

Delete existing framework and API

Delete the Framework used in the original AdBrix set in the Cocoapods file. After deletion, the API connected to the framework is also deleted.

mceclip2.png

Add DFINERY SDK to Cocoapods

Add DFINERY SDK to Cocoapods. 

platform:ios, '8.0'
target "myXcodeProject" do
pod 'AdBrixRmKit', '2.4.0.3'
end

Activate Swift library

If the project is made in Objective-C, enable it by setting Always Embed Swift Standard Libraries to Yes in Build Settings.

SDK init in AppDelegate

Then, add the SDK initialization code in the app's AppDelegate class as shown below.

You can check appKey / secretKey in DFINERY Console.

DFINERY Console: https://console.dfinery.io/

Swift Obj-C 
import AdBrixRM

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
    //Create AdBrixRM Instance
    let adBrix = AdBrixRM.getInstance

    // Set adbrix appKey & secretKey
    adBrix.initAdBrix(appKey: "your_adbrix_remastered_app_key", secretKey: "your_adbrix_remastered_secret_key")

    return true
}
#import <AdBrixRM/AdBrixRM-Swift.h>

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
    // Override point for customization after application launch.

    //Create AdBrixRM Instance
    AdBrixRM *adBrix = [AdBrixRM sharedInstance];

    // Set adbrix appKey & secretKey
    [adBrix initAdBrixWithAppKey:@"your_adbrix_remastered_app_key" secretKey:@"your_adbrix_remastered_secret_key"];

    return YES;
}

[[Quote:Guide:Normal]] Congratulations!!!

Basic integration for using DFINERY has been completed.
The available features are as follows:
1. Reporting to check indicators such as DAU, MAU, and daily retention
2. App introduction campaigns such as NCPI

In order to integrate additional APIs of the DFINERY SDK, please follow the guide below.
Integration Guide: DFINERY SDK Integration Guide [iOS]

Integration support

If you need support for SDK integration, please contact us at the e-mail address below.

Integration support email: support@adbrixsupport.zendesk.com

Related articles

클릭하여 고객지원팀에게 문의하기

답을 찾지 못하였나요? 걱정하지 마시고, 고객지원팀에게 문의주세요!

INDEX