The Unity SDK for Tenjin. To learn more about Tenjin and our product offering, please visit https://www.tenjin.com.
- Please see our Release Notes to see detailed version history of changes.
- Tenjin Unity SDK supports both iOS and Android.
- Review the iOS and Android documentation and apply the proper platform settings to your builds.
- For any issues or support, please contact: [email protected].
Note
If you are using Unity SDK v1.12.29 or lower, please follow these steps before completing the SDK integration. To upgrade to v1.12.30 or higher from lower versions, please ensure to remove the Tenjin binaries before installing the latest Unity version.
Warning
If you have libTenjinSDK.a
and/or libTenjinSDKUniversal.a
from older Tenjin SDK versions, please delete them and run pod install
to integrate it on iOS.
- SDK Integration
- Google Play
- Amazon store
- OAID
- Proguard
- App Initilization
- App Store
- ATTrackingManager (iOS)
- SKAdNetwork and Conversion Value
- SKAdNetwork iOS 15+ Postbacks
- GDPR
- Purchase Events
- Custom Events
- Server-to-server integration
- App Subversion
- LiveOps Campaigns
- Customer User ID
- Analytics Installation ID
- Google DMA parameters
- Retry/cache events and IAP
- Impression Level Ad Revenue Integration
- [Testing][29]
-
Download the latest Unity SDK from here.
-
Import the
TenjinUnityPackage.unitypackage
into your project:Assets -> Import Package
.
To ensure Tenjin works seamlessly with the latest features and fixes, please make sure your Maven (Gradle) dependencies are up to date, as we distribute our Tenjin Android SDK through Maven. We've noticed some developers still using outdated versions, which might cause issues.
If you build through Android Studio, please make sure to run Gradle sync to update the dependencies.
If you don't use Android Studio, please update your dependencies in Unity by following these steps:
- Open Unity.
- Navigate to Assets > External Dependency Manager > Android Resolver.
- Select Force Resolve to update your Gradle dependencies to the latest versions.
By default, unspecified is the default App Store. Update the app store value to googleplay, if you distribute your app on Google Play Store.
Set your App Store Type value to googleplay
:
BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>");
instance.SetAppStoreType(AppStoreType.googleplay);
The Tenjin SDK requires the following permissions:
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" /> <!-- Required to get network connectivity (i.e. wifi vs. mobile) -->
Google Play Services requires all API level 32 (Android 13) apps using the advertising_id(Android Advertising ID (AAID)) to declare the Google Play Services AD_ID permission (shown below) in their manifest file. You are required to update the tenjin-android-sdk to version 1.12.8 in order to use the below permission.
<uses-permission android:name="com.google.android.gms.permission.AD_ID"/>
Add Android Advertising ID (AAID) and Install Referrer libraries, add it to your build.gradle file.
dependencies {
implementation 'com.google.android.gms:play-services-ads-identifier:{version}'
implementation 'com.android.installreferrer:installreferrer:{version}'
}
To be able to collect Meta's Install Referrer, add these queries to your Android Manifest:
<queries>
<package android:name="com.facebook.katana" />
</queries>
<queries>
<package android:name="com.instagram.android" />
</queries>
If you haven't set up Facebook's SDK (Meta) yet, add the following to your strings.xml
file:
<string name="facebook_app_id" translatable="false">YOUR_APP_ID</string>
By default, unspecified is the default App Store. Update the app store value to amazon, if you distribute your app on Amazon store.
Set your App Store Type value to amazon
:
BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>");
instance.SetAppStoreType(AppStoreType.amazon);
Tenjin supports promoting your app on other Android App Stores using the Android OAID. We have the following requirements for integrating OAID libraries. If you plan to release your app outside of Google Play, make sure to implement these OAID libraries.
MSA OAID is an advertising ID for devices manufactured in China that the MSA (Mobile Security Alliance) provides. For integration with the MSA library, download the following oaid_sdk_1.0.25.aar.
Place the oaid_sdk_1.0.25.aar
file in your project's Android libs directory: /Assets/Plugins/Android
Set your App Store Type value to other
:
BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>");
instance.SetAppStoreType(AppStoreType.other);
For outside of China, you can collect OAID using the library provided by Huawei. For integration with the Huawei OAID library, download the following Huawei AAR file: huawei-ads-identifier.aar. If your app is in the Huawei App Gallery, download and add the Huawei Install Referrer file: huawei-ads-installreferrer.aar.
Place the Huawei files in your project's Android libs directory: /Assets/Plugins/Android
Set your App Store Type value to other
:
BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>");
instance.SetAppStoreType(AppStoreType.other);
-keep class com.tenjin.** { *; }
-keep public class com.google.android.gms.ads.identifier.** { *; }
-keep public class com.google.android.gms.common.** { *; }
-keep public class com.android.installreferrer.** { *; }
-keep class * extends java.util.ListResourceBundle {
protected java.lang.Object[][] getContents();
}
-keepattributes *Annotation*
If you are using Huawei libraries, you can to use these settings:
-keep class com.huawei.hms.ads.** { *; }
-keep interface com.huawei.hms.ads.** { *; }
-
Get your
SDK_KEY
from your app page. Note:SDK_KEY
is unique for each of your app. You can create up to 3 keys for the same app. -
In your project's first
Start()
method, add the following line of code. Also add toOnApplicationPause()
if you want to send sessions data when a user resumes using the app from the background.using UnityEngine; using System.Collections; public class TenjinExampleScript : MonoBehaviour { void Start() { TenjinConnect(); } void OnApplicationPause(bool pauseStatus) { if (!pauseStatus) { TenjinConnect(); } } public void TenjinConnect() { BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>"); // Sends install/open event to Tenjin instance.Connect(); } }
Note
Please ensure you implement this code on every Start()
, not only on the first app open of the app. If we notice that you don't follow our recommendation, we can't give you the proper support or your account might be suspended.
We support three app store options,
- googleplay
- amazon
- other
By default, unspecified is the default App Store. If you are publishing in a specific App Store, update the app store value to the appropriate app store value. The app store value other is used for Huawei AppGallery and other app stores:
-
AndroidManifest.xml
:<meta-data android:name="TENJIN_APP_STORE" android:value="{{SET_APP_STORE_TYPE_VALUE}}" />
-
SetAppStoreType()
:BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>"); instance.SetAppStoreType(AppStoreType.{{SET_APP_STORE_TYPE_VALUE}});
-
Starting with iOS 14, you have the option to show the initial ATTrackingManager permissions prompt and selection to opt in/opt out users.
-
If the device doesn't accept tracking permission, IDFA will become zero. If the device accepts tracking permission, the
Connect()
method will send the IDFA to our servers. -
You can also still call Tenjin
connect()
, without using ATTrackingManager. ATTrackingManager permissions prompt is not obligatory until the early spring of 2021.
using UnityEngine;
using System.Collections;
using UnityEngine.iOS;
public class TenjinExampleScript : MonoBehaviour {
void Start() {
TenjinConnect();
}
void OnApplicationPause(bool pauseStatus) {
if (!pauseStatus) {
TenjinConnect();
}
}
public void TenjinConnect() {
BaseTenjin instance = Tenjin.getInstance("SDK_KEY");
#if UNITY_IOS
if (new Version(Device.systemVersion).CompareTo(new Version("14.0")) >= 0) {
// Tenjin wrapper for requestTrackingAuthorization
instance.RequestTrackingAuthorizationWithCompletionHandler((status) => {
Debug.Log("===> App Tracking Transparency Authorization Status: " + status);
// Sends install/open event to Tenjin
instance.Connect();
});
}
else {
instance.Connect();
}
#elif UNITY_ANDROID
// Sends install/open event to Tenjin
instance.Connect();
#endif
}
}
To comply with Apple’s ATT guidelines, you must provide a description for the ATT permission prompt, then implement the permission request in your application.
Note
You must implement the permission request before serving ads in your game.
Apple requires a description for the ATT permission prompt. You need to set the description with the NSUserTrackingUsageDescription
key in the Info.plist
file of your Xcode project. You have to provide a message that informs the user why you are requesting permission to use device tracking data:
- In your Xcode project navigator, open the
Info.plist
file. - Click the add button (+) beside any key in the property list editor to create a new property key.
- Enter the key name
NSUserTrackingUsageDescription
. - Select a string value type.
- Enter the app tracking transparency message in the value field. Some examples include:
- "We will use your data to provide a better and personalized ad experience."
- "We try to show ads for apps and products that will be most interesting to you based on the apps you use, the device you are on, and the country you are in."
- "We try to show ads for apps and products that will be most interesting to you based on the apps you use."
Note
Apple provides specific app store guidelines that define acceptable use and messaging for all end-user facing privacy-related features. Tenjin does not provide legal advice. Therefore, the information on this page is not a substitute for seeking your own legal counsel to determine the legal requirements of your business and processes, and how to address them.
As part of SKAdNetwork, we created a wrapper method for updatePostbackConversionValue(_:)
.
Our methods will register the equivalent SKAdNetwork methods and also send the conversion values to our servers.
updatePostbackConversionValue(conversionValue: Integer)
6 bit value should correspond to the in-app event and shouldn't be entered as binary representation but 0-63 integer. Our server will reject any invalid values.
As of iOS 16.1, which supports SKAdNetwork 4.0, you can now send coarseValue
(String, with possible variants being "low", "medium" or "high") and lockWindow
(Boolean) as parameters on the update postback method:
updatePostbackConversionValue(conversionValue: Integer, coarseValue: String)
updatePostbackConversionValue(conversionValue: Integer, coarseValue: String, lockWindow: Bool)
-
For iOS version 16.1+ which supports SKAdNetwork 4.0, you can call this method as many times as you want and can make the conversion value lower or higher than the previous value.
-
For iOS versions lower than 16.1 supporting SKAdnetWork versions lower than 4.0, you can call this method and our SDK will automatically detect the iOS version and update
conversionValue
only.
using UnityEngine;
using System.Collections;
public class TenjinExampleScript : MonoBehaviour {
void Start() {
TenjinConnect();
}
void OnApplicationPause(bool pauseStatus) {
if (!pauseStatus) {
TenjinConnect();
}
}
public void TenjinConnect() {
BaseTenjin instance = Tenjin.getInstance("SDK_KEY");
#if UNITY_IOS
// Sends install/open event to Tenjin
instance.Connect();
// Sets SKAdNetwork Conversion Value
// You will need to use a value between 0-63
instance.updatePostbackConversionValue(<Integer between 0 and 63>);
// For iOS 16.1+ (SKAN 4.0)
instance.updatePostbackConversionValue(<Integer between 0 and 63>, "medium");
instance.updatePostbackConversionValue(<Integer between 0 and 63>, "medium", true);
#elif UNITY_ANDROID
// Sends install/open event to Tenjin
instance.Connect();
#endif
}
}
To specify Tenjin as the destination for your SK Ad Network postbacks, do the following:
- Select
Info.plist
in the Project navigator in Xcode. - Click the Add button (+) beside a key in the property list editor and press Return.
- Type the key name
NSAdvertisingAttributionReportEndpoint
. - Choose String from the pop-up menu in the Type column.
- Enter
https://tenjin-skan.com
These steps are adapted from Apple's instructions at https://developer.apple.com/documentation/storekit/skadnetwork/configuring_an_advertised_app.
Note
If you are using AppLovin MAX for mediation, their Unity SDK will overwrite any value you entered for NSAdvertisingAttributionReportEndpoint
with their own URL during the build process. You should be able to set the NSAdvertisingAttributionReportEndpoint to https://tenjin-skan.com
in XCode after it's been overwritten in the following process.
-
Export the iOS app following the steps Unity outlines here.
-
After you build the iOS app, you should have an XCode project that has this structure: https://docs.unity3d.com/Manual/StructureOfXcodeProject.html
-
Navigate to the
Info.plist
file in the XCode project to manually change the NSAdvertisingAttributionReportEndpoint tohttps://tenjin-skan.com
. Otherwise, you can ask your AppLovin account manager to set up forwarding the postbacks to us.
As part of GDPR compliance, with Tenjin's SDK you can opt-in, opt-out devices/users, or select which specific device-related params to opt-in or opt-out. OptOut()
will not send any API requests to Tenjin, and we will not process any events.
To opt-in/opt-out:
void Start () {
BaseTenjin instance = Tenjin.getInstance("SDK_KEY");
boolean userOptIn = CheckOptInValue();
if (userOptIn) {
instance.OptIn();
}
else {
instance.OptOut();
}
instance.Connect();
}
boolean CheckOptInValue()
{
// check opt-in value
// return true; // if user opted-in
return false;
}
-
To opt-in/opt-out specific device-related parameters, you can use the
OptInParams()
orOptOutParams()
. -
OptInParams()
will only send device-related parameters that are specified.OptOutParams()
will send all device-related parameters except ones that are specified. -
Kindly note that we require the following parameters to properly track devices in Tenjin's system. If one of these mandatory parameters is missing, the event will not be processed or recorded.
- For Android,
advertising_id
- For iOS
developer_device_id
- For Android,
-
If you are targeting IMEI and/or OAID Ad Networks for Android, add:
imei
oaid
-
If you intend to use Google Ad Words, you will also need to add:
platform
os_version
app_version
locale
device_model
build_id
If you want to only get specific device-related parameters, use OptInParams()
. In example below, we will only these device-related parameters: ip_address
, advertising_id
, developer_device_id
, limit_ad_tracking
, referrer
, and iad
:
BaseTenjin instance = Tenjin.getInstance("SDK_KEY");
List<string> optInParams = new List<string> {"ip_address", "advertising_id", "developer_device_id", "limit_ad_tracking", "referrer", "iad"};
instance.OptInParams(optInParams);
instance.Connect();
If you want to send ALL parameters except specific device-related parameters, use OptOutParams()
. In the example below, we will send ALL device-related parameters except: locale
, timezone
, and build_id
parameters.
BaseTenjin instance = Tenjin.getInstance("SDK_KEY");
List<string> optOutParams = new List<string> {"locale", "timezone", "build_id"};
instance.OptOutParams(optOutParams);
instance.Connect();
You can automatically opt in or opt out using your CMP consents (purpose 1) which are already saved in the user's device. The method returns a boolean to let you know if it's opted in or out.
OptInOutUsingCMP()
BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>");
optInOut = instance.OptInOutUsingCMP();
Param | Description | Platform | Reference |
---|---|---|---|
ip_address | IP Address | All | |
advertising_id | Device Advertising ID | All | Android, iOS |
developer_device_id | ID for Vendor | iOS | iOS |
oaid | Open Advertising ID | Android | Android |
imei | Device IMEI | Android | Android |
limit_ad_tracking | limit ad tracking enabled | All | Android, iOS |
platform | platform | All | iOS or Android |
referrer | Google Play Install Referrer | Android | Android |
iad | Apple Search Ad parameters | iOS | iOS |
os_version | operating system version | All | Android, iOS |
device | device name | All | Android, iOS (hw.machine) |
device_manufacturer | device manufactuer | Android | Android |
device_model | device model | All | Android, iOS (hw.model) |
device_brand | device brand | Android | Android |
device_product | device product | Android | Android |
device_model_name | device machine | iOS | iOS (hw.model) |
device_cpu | device cpu name | iOS | iOS (hw.cputype) |
carrier | phone carrier | Android | Android |
connection_type | cellular or wifi | Android | Android |
screen_width | device screen width | Android | Android |
screen_height | device screen height | Android | Android |
os_version_release | operating system version | All | Android, iOS |
build_id | build ID | All | Android, iOS (kern.osversion) |
locale | device locale | All | Android, iOS |
country | locale country | All | Android, iOS |
timezone | timezone | All | Android, iOS |
iOS receipt validation requires transactionId
and receipt
. For receipt
, be sure to send the receipt Payload
(the base64 encoded ASN.1 receipt) from Unity.
IMPORTANT: If you have subscription IAP, you will need to add your app's shared secret in the Tenjin dashboard. You can retrieve your iOS App-Specific Shared Secret from the App Store Connect > Select your app > General > App Information > App-Specific Shared Secret.
Google Play receipt validation requires receipt
and signature
parameters.
IMPORTANT: You will need to add your app's public key in the Tenjin dashboard. You can retrieve your Base64-encoded RSA public key from the Google Play Developer Console > Select your app > Monetization setup.
Warning
For Google play, Please ensure to 'acknowledge' the purchase event before sending it to Tenjin. For more details, read here.
Amazon AppStore receipt validation requires receiptId
and userId
parameters.
Important
You will need to add your Amazon app's Shared Key in the Tenjin dashboard. The shared secret can be found on the Shared Key in your developer account with the Amazon Appstore account
In the example below, we are using the widely used MiniJSON library for JSON deserializing.
public static void OnProcessPurchase(PurchaseEventArgs purchaseEventArgs) {
var price = purchaseEventArgs.purchasedProduct.metadata.localizedPrice;
double lPrice = decimal.ToDouble(price);
var currencyCode = purchaseEventArgs.purchasedProduct.metadata.isoCurrencyCode;
var wrapper = Json.Deserialize(purchaseEventArgs.purchasedProduct.receipt) as Dictionary<string, object>; // https://gist.github.com/darktable/1411710
if (null == wrapper) {
return;
}
var store = (string)wrapper["Store"]; // GooglePlay, AmazonAppStore, AppleAppStore, etc.
var payload = (string)wrapper["Payload"]; // For Apple this will be the base64 encoded ASN.1 receipt. For Android, it is the raw JSON receipt.
var productId = purchaseEventArgs.purchasedProduct.definition.id;
#if UNITY_ANDROID
if (store.Equals("GooglePlay")) {
var googleDetails = Json.Deserialize(payload) as Dictionary<string, object>;
var googleJson = (string)googleDetails["json"];
var googleSig = (string)googleDetails["signature"];
CompletedAndroidPurchase(productId, currencyCode, 1, lPrice, googleJson, googleSig);
}
if (store.Equals("AmazonApps")) {
var amazonDetails = Json.Deserialize(payload) as Dictionary<string, object>;
var amazonReceiptId = (string)amazonDetails["receiptId"];
var amazonUserId = (string)amazonDetails["userId"];
CompletedAmazonPurchase(productId, currencyCode, 1, lPrice, amazonReceiptId, amazonUserId);
}
#elif UNITY_IOS
var transactionId = purchaseEventArgs.purchasedProduct.transactionID;
CompletedIosPurchase(productId, currencyCode, 1, lPrice , transactionId, payload);
#endif
}
private static void CompletedAndroidPurchase(string ProductId, string CurrencyCode, int Quantity, double UnitPrice, string Receipt, string Signature)
{
BaseTenjin instance = Tenjin.getInstance("SDK_KEY");
instance.Transaction(ProductId, CurrencyCode, Quantity, UnitPrice, null, Receipt, Signature);
}
private static void CompletedIosPurchase(string ProductId, string CurrencyCode, int Quantity, double UnitPrice, string TransactionId, string Receipt)
{
BaseTenjin instance = Tenjin.getInstance("SDK_KEY");
instance.Transaction(ProductId, CurrencyCode, Quantity, UnitPrice, TransactionId, Receipt, null);
}
private static void CompletedAmazonPurchase(string ProductId, string CurrencyCode, int Quantity, double UnitPrice, string ReceiptId, string UserId)
{
BaseTenjin instance = Tenjin.getInstance("SDK_KEY");
instance.TransactionAmazon(ProductId, CurrencyCode, Quantity, UnitPrice, ReceiptId, UserId);
}
Disclaimer: If you are implementing purchase events on Tenjin for the first time, make sure to verify the data with other tools you’re using before you start scaling up your user acquisition campaigns using purchase data.
Choose between 15% and 30% App Store’s revenue commission via our new setup. The steps are -
- Go to CONFIGURE --> Apps
- Click on the app you want to change it for
- Under the ‘App Store Commission’ section click ‘Edit’
- Choose 30% or 15% as your desired app store commission.
- Select the start date and end date (Or you can keep the end date blank if you dont want an end date)
- Click Save (note: the 15% commission can be applied only to dates moving forward and not historical dates. So please set the start date from the date you make the change and forward)
-
You are responsible to send a subscription transaction one time during each subscription interval (i.e., For example, for a monthly subscription, you will need to send us 1 transaction per month). In the example timeline below, a transaction event should only be sent at the "First Charge" and "Renewal" events. During the trial period, do not send Tenjin the transaction event.
-
Tenjin does not de-dupe duplicate transactions.
-
If you have iOS subscription IAP, you will need to add your app's public key in the Tenjin dashboard. You can retrieve your iOS App-Specific Shared Secret from the iTunes Connect Console > Select your app > Features > In-App Purchases > App-Specific Shared Secret.
-
For more information on iOS subscriptions, please see: Apple documentation on Working with Subscriptions
-
For more information on Android subscriptions, please see: Google Play Billing subscriptions documentation
IMPORTANT: Limit custom event names to less than 80 characters. Do not exceed 500 unique custom event names.
- Include the Assets folder in your Unity project
- In your projects' method for the custom event, write the following for a named event:
Tenjin.getInstance("<SDK_KEY>").SendEvent("name")
and the following for a named event with an integer value:Tenjin.getInstance("<SDK_KEY>").SendEvent("nameWithValue","value")
- Make sure
value
passed is an integer. Ifvalue
is not an integer, your event will not be passed.
Here's an example of the code:
void MethodWithCustomEvent(){
//event with name
BaseTenjin instance = Tenjin.getInstance ("SDK_KEY");
instance.SendEvent("name");
//event with name and integer value
instance.SendEvent("nameWithValue", "value");
}
.SendEvent("name")
is for events that are static markers or milestones. This would include things like tutorial_complete
, registration
, or level_1
.
.SendEvent("name", "value")
is for events that you want to do math on a property of that event. For example, ("coins_purchased", "100")
will let you analyze a sum or average of the coins that are purchased for that event.
Tenjin offers server-to-server integration, which is a paid feature. If you want to access to the documentation, please send email to [email protected] and discuss the pricing.
If you are running A/B tests and want to report the differences, we can append a numeric value to your app version using the AppendAppSubversion()
method. For example, if your app version 1.0.1
, and set AppendAppSubversion(8888)
, it will report app version as 1.0.1.8888
.
This data will appear within DataVault, where you will be able to run reports using the app subversion values.
BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>");
instance.AppendAppSubversion(8888);
instance.Connect();
Tenjin supports retrieving of user attribution information, like sourcing ad network and campaign, from the SDK. This will allow developers to collect and analyze user-level attribution data in real-time. Here are the possible use cases using Tenjin LiveOps Campaigns:
- If you have your own data anlytics tool, custom callback will allow you to tie the attribution data to your in-game data per device level.
- Show different app content depending on where the user comes from. For example, if user A is attributed to organic and user B is attributed to Facebook and user B is likely to be more engaged with your app, then you want to show a special in-game offer after the user installs the app. If you want to discuss more specific use cases, please write to [email protected].
Warning
LiveOps Campaigns is a paid feature, so please contact your Tenjin account manager if you would like to get access.
You can set and get customer user id to send as a parameter on events.
.SetCustomerUserId("user_id")
.GetCustomerUserId()
BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>");
instance.SetCustomerUserId("user_id");
string userId = instance.GetCustomerUserId();
You can get the analytics id which is generated randomly and saved in the local storage of the device.
GetAnalyticsInstallationId()
BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>");
analyticsId = instance.GetAnalyticsInstallationId;
If you already have a CMP integrated, Google DMA parameters will be automatically collected by the Tenjin SDK. There’s nothing to implement in the Tenjin SDK if you have a CMP integrated. If you want to override your CMP, or simply want to build your own consent mechanisms, you can use the following:
SetGoogleDMAParameters(bool, bool)
BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>");
instance.SetGoogleDMAParameters(adPersonalization, adUserData);
To explicitly manage the collection of Google DMA parameters, you have the flexibility to opt in or opt out at any time. While the default setting is to opt in, you can easily adjust your preferences using the OptInGoogleDMA or OptOutGoogleDMA methods, ensuring full control over your data privacy settings:
instance.OptInGoogleDMA();
instance.OptOutGoogleDMA();
You can enable/disable retrying and caching events and IAP when requests fail or users don't have internet connection. These events will be sent after a new event has been added to the queue and user has recovered connection.
.SetCacheEventSetting(true)
BaseTenjin instance = Tenjin.getInstance("<SDK_KEY>");
instance.SetCacheEventSetting(true);
Tenjin supports the ability to integrate with the Impression Level Ad Revenue (ILRD) feature from,
- AppLovin
- Unity LevelPlay
- HyperBid
- AdMob
- Topon
- CAS
- TradPlus
This feature allows you to receive events which correspond to your ad revenue which is affected by each advertisement shown to a user. To enable this feature, follow the below instructions.
Warning
ILRD is a paid feature, so please contact your Tenjin account manager to discuss the price at first before sending ILRD events.
You can verify if the integration is working through our Live Test Device Data Tool. Add your advertising_id
or IDFA/GAID
to the list of test devices. You can find this under Support -> Test Devices. Go to the SDK Live page and send the test events from your app. You should see live events come in: