The first step in integrating the SDK manually is to download the Android SDK itself.
After unzipping the SDK, you will find docs, libraries and the TapjoyEasyApp.
dependencies {
implementation files('libs/tapjoyconnectlibrary.aar')
}
repositories {
maven {
url 'https://maven.google.com/'
name 'Google'
}
}
dependencies {
implementation 'com.google.android.gms:play-services-ads-identifier:17.1.0'
}
The following permissions are needed:
ACCESS_WIFI_STATE
(optional)play-services-ads
v17.1.0 includes the AD_ID
permission which must be removed for members of the Google Play Families Program.
You can exclude the permission by adding the following element to your manifest:
<uses-permission android:name="com.google.android.gms.permission.AD_ID" tools:node="remove"/>
More details are available here.
If you are using the JAR option instead of the AAR, the following permissions and activities are also necessary.
INTERNET
ACCESS_NETWORK_STATE
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
To use Tapjoy’s full functionality for the current SDK version, add these activities to the AndroidManifest.xml file in the Application block:
<activity
android:name="com.tapjoy.TJAdUnitActivity"
android:configChanges="orientation|keyboardHidden|screenSize"
android:hardwareAccelerated="true"
android:theme="@android:style/Theme.Translucent.NoTitleBar.Fullscreen" />
<activity
android:name="com.tapjoy.TJWebViewActivity"
android:configChanges="orientation|keyboardHidden|screenSize"
android:theme="@style/TranslucentTheme"
android:hardwareAccelerated="true" />
You will also need to add the same configChanges to your App’s Manifest activity:
android:configChanges="orientation|keyboardHidden|screenSize"
At this point, it’s a good idea to compile and run your application to ensure that everything in your app is still working. Since we haven’t actually done anything to your application’s code, there should be no errors or changes in how your application functions.
The next step is to add the Tapjoy connect code to your application. This key bit of code "turns on" the Tapjoy SDK in your application.
The Tapjoy connect call is extremely important, as none of Tapjoy’s products or functionality will work if it is not implemented correctly.
To implement the Tapjoy connect call, you will need your Tapjoy SDK Key for the application you are integrating. To find this, navigate to your application in the Tapjoy dashboard, and click the "Settings" button on the top navigation bar. Navigate to "App Settings" and you will find the SDK Key at the bottom of the page.
Now it's time to write some code. Import Tapjoy in to your Activity:
import com.tapjoy.Tapjoy
Then in your main Activity's onCreate() method connect to Tapjoy:
Hashtable<String, Object> connectFlags = new Hashtable<String, Object>();
connectFlags.put(TapjoyConnectFlag.ENABLE_LOGGING, "true"); // Disable this in production builds
connectFlags.put(TapjoyConnectFlag.USER_ID, "USER_ID_GOES_HERE"); // Important for self-managed currency
Tapjoy.connect(getApplicationContext(), "SDK_KEY_GOES_HERE", connectFlags, new TJConnectListener() {
@Override
public void onConnectSuccess() {
}
@Override
public void onConnectWarning(int code, String message) {
}
@Override
public void onConnectFailure() {
}
});
In this code you can see that we connect to Tapjoy (listening for the success, failure, and warning callbacks) and we configure two 'connect flags' (logging and user id). onConnectSuccess
indicates the SDK has successfully connected to the Tapjoy servers. If we connect successfully but there is a non-blocking issue onConnectWarning
will fire first. Currently this feature will only detect issues with UserId when sent in ConnectFlags. If we cannot connect to the servers successfully, onConnectFailure
will fire.
The two most common and useful connect flags for Publishers are ENABLE_LOGGING and USER_ID.
You will use the logging flag in your debug builds but it is important to disable when you are building for production.
Setting the USER_ID flag is crucial when you are using a self-managed currency. Setting it at connect is important as it ensures it is set before any placement is called, preventing potential rewarding issues.
Some other connect flags that are useful to help publishers control how Tapjoy uses the various Android Identifiers supplied by the operating system:
For an explanation of all connect flags, Please see the Java SDK Reference.
Now compile and run your application.
In the Tapjoy Dashboard, if you click on the "Analytics" from the top navigation bar and then "Real-time" tab in the navigation bar on the left, you should see some activity from your application moments after you run it.
Congratulations! You now have Tapjoy working in your application.