Advanced Topics

App Level Ad Tracking Opt-out

With the TUNE SDK, an app can allow its users to "opt-out" of app-level ad tracking. If a user decides to opt-out, then the TUNE SDK uses the install or conversion event only for ad reporting and not for ad targeting (such as by device, country, or language). By default, ad tracking is enabled (opt-in).

Android SDK Opt-out

To opt-out, call the following setter method:

setAppAdTrackingEnabled(false);

To opt-in (default), call the following setter method:

setAppAdTrackingEnabled(true);

iOS SDK Opt-out

To opt-out, call the following setter method:

[Tune setAppAdMeasurement:NO];

To opt-in (default), call the following setter method:

[Tune setAppAdMeasurement:YES];

Unity Plugin Opt-out

To opt-out, call the following setter method:

TuneExterns.TuneSetAppAdTracking(NO);

To opt-in (default), call the following setter method:

TuneExterns.TuneSetAppAdTracking(YES);

Attributing with UIID for iOS Apps in APAC

In many countries (such as Japan) across the Asia Pacific (APAC) region, a significant portion of advertising partners (publishers) use the Unique Installation Identifier (UIID) for identifying unique and distinct app installs on iOS. For information about UIID, please visit https://github.com/akisute/UIApplication-UIID#readme.

Similar to the other unique device identifiers that Attribution Analytics (AA) uses for mobile app attribution, when UIID is passed into the TUNE link on click (and the TUNE SDK is set up to collect the value on install), AA performs attribution using unique identifier matching.

UIID Collected in SDK on Install

To set up the TUNE iOS SDK for UIID collection, use our "setUIID" method.

파라미터	설명	Android	iOS
UIID	The Unique Installation Identifier (UIID) of the device. Generate this value using the official implementation according to: https://github.com/akisute/UIApplication-UIID	해당 없음	`setUIID:`

UIID Collected in TUNE Link

Partners who collect UIID must pass this value on click into the advertiser TUNE link. Specifically, partners pass the UIID into the "device_id_md5" parameter of AA:

&device_id_md5={UIID-value-here}

In the example above, replace "UIID-value-here" with the real UIID value that is 32 characters long, as shown in the following example TUNE link:

https://12345.api-01.com/serve?action=click&publisher_id=9558&site_id=2962&offer_id=237906&device_id_md5={UIID-value-here}

Automatic Collection of Device Geo Location

User device location information can provide you with important insights by allowing you to segment users based on their geographic location. To facilitate this, the TUNE iOS SDK 3.10.0+ and TUNE Android SDK 4.0.0+ automatically collects the user device geo location when a measure call is fired (ex. "measureSession", "measureEvent").

When our SDK detects the presence of the CoreLocation framework on iOS, or access location permissions on Android, it auto-collects the device location (only if the end-user allows your app to access the device location). If you explicitly call "setLocation:", then the SDK uses the provided location during the app session and then stops auto-collecting the location.

This feature does not force you to include CoreLocation framework or Android location permissions, if your app does not need it otherwise.

📘
Prompt for Device Location
Even when location is present, the TUNE SDK never prompts the end-user for permission to access location information. It is the responsibility of your app to prompt the user for permission to access location information.

If the user does not enable location, then there is no location for the SDK to collect. If the user enables location but does not allow your app to collect the device’s location, then again, the SDK cannot collect the location.

To help conserve battery, the SDK accesses the device location only once when an event measurement call is fired. The auto-collected location info includes latitude, longitude, and altitude. On iOS, it also collects horizontal accuracy, vertical accuracy, and timestamp — properties from CoreLocation.CLLocation.

You can call a setter to control the SDK device location auto-collection behavior:

Android SDK Location Access

void setShouldAutoCollectDeviceLocation(boolean autoCollect)

iOS SDK Location Access

+ (void)disableLocationAutoCollection:(BOOL)autoCollect;

Unity Plugin Location Access

Tune.SetShouldAutoCollectDeviceLocation(shouldAutoCollect);

Avoiding the Dalvik 65K Method Limit

Android APKs have a limit of 65K methods for a single DEX file. This limit can easily be reached when including the Google Play Services SDK required by the TUNE Android SDK, as the Google Play Services SDK alone holds over 20K methods.

There are several ways to reduce the amount of methods added to your app. When working with third-party libraries, you can include only the methods your app actually uses during the build process. The TUNE SDK only requires the Ads library in the Google Play Services SDK, in order to access the Google Advertising ID.

ProGuard

We recommend using ProGuard to strip any unused methods during compilation. To set up ProGuard for Google Play Services, add to your <project_directory>/proguard-project.txt file:

-keep class * extends java.util.ListResourceBundle {
    protected Object[][] getContents();
}

-keep public class com.google.android.gms.common.internal.safeparcel.SafeParcelable {
    public static final *** NULL;
}

-keepnames @com.google.android.gms.common.annotation.KeepName class *
-keepclassmembernames class * {
    @com.google.android.gms.common.annotation.KeepName *;
}

-keepnames class * implements android.os.Parcelable {
    public static final ** CREATOR;
}

Please note that ProGuard will apply only for release builds.

Selective Gradle Compilation

For a Gradle build, you may also selectively include only the required Ads API from the SDK, starting from Google Play Services version 6.5+.

In your build.gradle file, include only the "play-services-ads" library as a dependency:

compile 'com.google.android.gms:play-services-ads:7.5.0'

instead of

compile 'com.google.android.gms:play-services:7.5.0'

Multidex

You may consider configuring your app as a multidex build to circumvent the 65K limit if you are still above the limit.