Collapse

Estimated Time to Complete

10 Minutes

SDK VERSION NOTE: This feature requires Kochava SDK Version 1.1.0 or higher.

SDK PLATFORM NOTE: This feature is applicable to iOS platforms only.

No special code is needed to support SKAdNetwork, beyond tracking your existing events which are eligible for conversion. However, events which are to be considered for SKAdNetwork conversion updates must be built using standard parameters, rather than using an existing serialized/stringified json object for event data. See the topic “Tracking Events” for more detail on using standard parameters.

After setting up SKAdNetwork in your Free App Analytics dashboard, the SDK will automatically:

1. Call Apple’s SKAdNetwork registration at the first opportunity following launch.
2. When an eligible conversion event is triggered on iOS 14, the SDK will calculate the appropriate conversion value based on the event’s properties and automatically call Apple’s SKAdNetwork conversion update.

Generating SKAdNetwork Postbacks:

While the SDK automatically makes the necessary Apple API calls for you, a SKAdNetwork postback will only be generated if requirements are met for both the source app and advertised app. The advertised app must have been reviewed and available for download in the App Store, while the source app (where the ad is displayed) can be one that you are currently developing and run from Xcode or through TestFlight. Be sure to use the correct SKStoreProductParameterAdNetworkSourceAppStoreIdentifier per your case.

For testing purposes, you can cut down on the 24 hour postback wait by using the “SKAdNetwork Profile” from the Apple developer console here: https://developer.apple.com/download/more/ (search for “skad”).

Collapse

Estimated Time to Complete

30 Minutes

SDK VERSION NOTE: This feature requires Kochava SDK Version 1.1.0 or higher.

SDK PLATFORM NOTE: This feature is applicable to iOS platforms only.

As of iOS 14, IDFA collection is gated behind Apple’s new AppTrackingTransparency (ATT) permission-based authorization. This means that when an app is running on iOS 14, the IDFA is not available for collection until after the user grants permission, similar to any other iOS permission-based collection. However, Apple is delaying enforcement of ATT, which is discussed below.

Enforcing ATT for IDFA Collection

The SDK makes this very simple for you. All you need to do is tell the SDK you want to enable ATT enforcement during configuration.

As a tracking requirement by Apple, you must include in your info.plist the key NSUserTrackingUsageDescription and a string value explaining why you are requesting authorization to track. This text will be included in the prompt displayed by the operating system when tracking authorization is requested.

Configure the SDK

During SDK configuration, tell the SDK you wish to enable ATT enforcement. By default, the user will be prompted for tracking authorization one time, upon launch, and the SDK will allow up to 30 seconds for the user to answer the tracking authorization prompt. You may adjust this behavior if you wish.

Example Enabling ATT with default settings (recommended):

Example Allow more than the default 30 seconds for the user to respond:

At this point you are done. The user will be prompted for tracking authorization one time, during the first launch of the app, and the IDFA will be gathered if authorization is granted.

For purposes of testing, you will need to uninstall and reinstall the app each time you wish for the tracking prompt to appear, as Apple will only allow this to be displayed once.

Optionally, if you wish to prompt the user for tracking authorization at a specific moment or you do not want the SDK to trigger the prompt, continue reading below.

Custom Prompt Timing (Optional)

Follow these steps only if you wish for the tracking authorization prompt to be displayed at a time other than when the app is first launched or you do not want the SDK to trigger the prompt.

In order to accomplish this, first configure the SDK so that it does not automatically request authorization and allows enough time for the user to reach the point where tracking authorization will be requested at the moment of your choosing. In this example, we are allowing up to 120 seconds for the user to provide an answer to the tracking authorization request.

Example Configure the SDK:

Secondly, add code which requests the tracking authorization at the time of your choosing and then notifies the SDK when the authorization request completes. It is your responsibility to ensure your tracking authorization request code is reached. If it is not, the timeout will be reached and the SDK will proceed without collecting the IDFA.

NOTE: Regardless of how many times you request tracking authorization, the user is only prompted once. This means you can repeatedly request tracking authorization at a specific moment per app launch and the user will only be prompted once, the first time the code is reached.

Example Request authorization and notify the SDK upon completion:

App Store Submission Guidance and Best Practices

Developing Section: The information contained within this section is subject to change as Apple shares more information and their requirements evolve.

If you have added the NSUserTrackingUsageDescription entry to your info.plist and/or are referencing the ATT framework, Apple expects to visibly see the ATT prompt during the review process of your submission. At the time of this writing, the App Store submission guidelines do not state this requirement, but Apple has cited this as cause for rejection.

If the ATT prompt is not automatically triggered upon launch, we suggest that you include instructions for the reviewer detailing the steps they must take to trigger the ATT prompt. If you’ve forcibly disabled the ATT prompt whether through our UI or otherwise, you must add a review note indicating that you are not invoking the ATT consent prompt until the release of iOS 14.5.

NOTE: Apple may reject apps which attempt to preempt the ATT prompt with a soft prompt of any kind. We suggest that you avoid this approach and allow the ATT prompt to be triggered immediately upon launch.

Collapse

Estimated Time to Complete

15 Minutes

SDK VERSION NOTE: This feature requires Kochava SDK Version 1.1.0 or higher.

SDK PLATFORM NOTE: This feature is applicable to Android platforms only.

The standard SDK is used within your instant app (no special variant of the SDK is needed for an instant app).

In order to properly support user and attribution flow between the instant app and full app, the following steps must be taken.

Create two App GUIDs:

The instant app and full app should not use the same App GUID. For the instant app, create or use a Free App Analytics app of platform type Android – Instant App. For the full app, create or use a Free App Analytics app of platform type Android.

Configure the SDK:

You will need to provide the Instant App GUID to both the instant app and the full app. This must be done prior to starting the SDK. The SDK will automatically choose the correct app GUID to use.

Process the Deeplink:

When the instant app is launched, pass the invocation URL to the SDK’s Process Deeplink API as soon as possible, just as you would any other deeplink. See the topic Enhanced Deeplinking for complete instructions on how to use the Process Deeplink API.

By taking these steps, all functionality related to attribution, analytics, and measurement will be properly implemented between the app clip and full app.

Supporting Older Android Versions:

Instant Apps are natively supported on Android 8 (API 26) and higher with data being automatically migrated from the instant app to the full app. If supporting Android 7 or lower you are responsible for migrating the SDK’s data prior to starting the SDK. See the documentation on transferring data.

Collapse

Estimated Time to Complete

15 Minutes

SDK VERSION NOTE: This feature requires Kochava SDK Version 1.1.0 or higher.

SDK PLATFORM NOTE: This feature is applicable to iOS platforms only.

The standard SDK is used within your app clip app (no special variant of the SDK is needed for an app clip).

In order to properly support user and attribution flow between the app clip and full app, the following steps must be taken.

Create Two App GUIDs:

The app clip and full app should not use the same App GUID. For the app clip, create or use a Free App Analytics app of platform type iOS – App Clip. For the full app, create or use a Free App Analytics app of platform type iOS.

Configure the SDK:

You will need to provide an app group identifier string which facilitates shared storage between the app clip and full app. To accomplish this, in Xcode under the project Signing & Capabilities, add a new capability for App Groups if you do not have one already using the plus button. For the new identifier, start with your app’s bundle identifier and then prefix it with group. and suffix it with .kochava. Provide this identifier to the SDK prior to starting the SDK. This identifier must be the same between the app clip and full app.

Example (Provide a Shared Storage Container Before Starting the Tracker) —

NOTE: The SDK detects your app clip by looking for the bundle identifier’s default .clip suffix.

Process the Deeplink:

When the instant app is launched, pass the invocation URL to the SDK’s Process Deeplink API as soon as possible, just as you would any other deeplink. See the topic Enhanced Deeplinking for complete instructions on how to use the Process Deeplink API.

By taking these steps, all functionality related to attribution, analytics, and measurement will be properly implemented between the app clip and full app.

Collapse

Standard Events:

Example (Standard Event with Standard Parameters) —

Example (Standard Event with Standard and Custom Parameters) —

If you wish to use a custom event type with standard parameters, use a custom event name string within your event constructor in place of a standard event type.

For a detailed list of standard event types and parameters, see: Post Install Event Examples

Custom Events:

Example (Custom Event with Custom Parameters) —

Example (Send a Custom Event with Only a Name, no Event Data) —

Example (Send a Custom Event with Event Data) —

Example (Send a Custom Event with Serialized JSON Data) —

Collapse

Example (Standard Purchase Event):

Example (Custom Purchase Event with Serialized JSON Data):

Collapse

Estimated Time to Complete

10 Minutes

In order to effectively track user subscriptions and free trials, an event should be instrumented at the time of the subscription purchase or start of the free trial along with an accompanying identity link.

When a subscription or free trial begins, first set an identity link for this subscriber and then instrument a standard Subscription or Trial event populated with the following values:

• Price
• Currency
• Product Name
• User or Subscriber ID (hash suggested)
• Receipt (if available)

BEST PRACTICES: Always set the identity link before sending the event, otherwise the identity link will not be properly associated with the event.

Example (Identity Link with Subscription):

A free trial is handled in a similar way, although the price should be set to 0 and the event type should indicate Trial rather than Subscription. The product name should remain the same, as the event type indicates whether this was free trial or subscription.

Example (Identity Link with Free Trial):

Collapse

Example (Standard Deeplink Event):

Collapse

Estimated Time to Complete

10 Minutes

Example (Acquire the Deeplink) —

Example (Wait for the Callback) —

Collapse

Example (Register an Identity Link During Tracker Configuration):

Example (Register an Identity Link After Starting the Tracker):

Collapse

Example (Requesting Attribution Results):

Example (Using the Getter After Attribution Results Have Been Retrieved):

Collapse

Example (Getting the Kochava Device ID):

Collapse

Example (Enabling App Limit Ad Tracking During Tracker Configuration):

Example (Enable App Limit Ad Tracking After Starting the Tracker):

Collapse

Example (Enabling trace logging in a non-production build):

Collapse

Example (Enabling Sleep Mode During Tracker Configuration):

Example (Enabling Sleep Mode After Starting the Tracker):

Example (Waking the Tracker from Sleep Mode) —

Collapse

Estimated Time to Complete

5 Minutes

SDK VERSION NOTE: This feature requires Kochava SDK Version 2.0.0 or higher.

Clearing SDK Data:

The shutdown() method accepts a boolean indicating whether you wish to also clear all persisted SDK data from disk when shutting down. This should always be set to false and should never be set to true without a complete understanding of the ramifications of clearing this data, as it could create duplicate user metrics or worse.

Example (Shut Down the SDK and Clear Data) —

Collapse

Estimated Time to Complete

5 Minutes

Example (Starting the Tracker Only When Consent Allows) —

Example (Calling Tracker Methods Only When Consent Allows) —

Collapse

Estimated Time to Complete

5 Minutes

Collapse

1. Use an alternate testing App GUID so that your testing activities do not have an impact on your live app analytics.
2. Enable Logging, if helpful, to gain insight into the SDK’s behavior during runtime.
3. If you would like the SDK to behave as it would during a new install, be sure to un-install the app before each test.
4. Test your Free App Analytics integration. For more information see: Testing the Integration.

Analyzing SDK Behavior:

Collapse