Initialize the SDK and set up tracking
To initialize the SDK, you'll first need to configure the SDK with the Environment ID from Launch.
To find your Environment ID, navigate to Environments tab in Launch, and click on the 
icon corresponding to the environment you are setting up.
Adobe Experience Platform SDK for Android supports Android 4.0 (API 14) or later.
The SDK requires standard network connection permissions in your manifest to send data, collect cellular provider and record offline tracking calls:
To add these permissions, add the following lines to your AndroidManifest.xml file, which is located in the application project directory:
<uses-permission android:name="android.permission.INTERNET" /><uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
Create MainActivity.java in the app.
Add
MobileCore.configureWithAppID("PASTE_ENVIRONMENT_ID_HERE");
Adobe Experience Platform SDK for iOS supports iOS 10 or later.
In Xcode, find your didFinishLaunchingWithOptionslocated in AppDelegate.h and add:
[ACPCore configureWithAppId:@"PASTE_ENVIRONMENT_ID_HERE"];
In Xcode, find your didFinishLaunchingWithOptions located in AppDelegate.swift and add:
ACPCore.configure(withAppId: "PASTE_ENVIRONMENT_ID_HERE")
Adobe Experience Platform SDKs for iOS supports iOS 10 or later.
In Xcode, open AppDelegate.swift
Under
didFinishLaunchingWithOptions, add:ACPCore.configure(withAppId: "PASTE_ENVIRONMENT_ID_HERE")
Developing extensions and using Launch Integration? The environment ID should be prefixed with staging/. For example, staging/launch-EN58bc2c40c3b14d688b768fe79a623519-development
Debug logging is optional and helps you ensure that the SDK is working as intended. Below is a table that explains the levels of logging available and when they may be used:
Log Level | Description |
Error | This log level details unrecoverable errors caused during SDK implementation. |
Warning | In addition to detail from Error log level, Warning provides error information during SDK integration. This log level may indicate that a request has been made to the SDK, but the SDK may be unable to perform the requested task. For example, this may be used when catching an unexpected but recoverable exception and printing its message. |
Debug | In addition to detail from Warning log level, Debug also provides high-level information on how the SDK processes network requests/responses data. |
Verbose | In addition to detail from the Debug level, Verbose provides detailed, low-level information into how SDK processes database interactions and SDK events. |
To enable debug logging:
MobileCore.setLogLevel(LoggingMode.DEBUG);// MobileCore.setLogLevel(LoggingMode.VERBOSE);// MobileCore.setLogLevel(LoggingMode.WARNING);// MobileCore.setLogLevel(LoggingMode.ERROR);
[ACPCore setLogLevel:ACPMobileLogLevelDebug];// [ACPCore setLogLevel:ACPMobileLogLevelVerbose];// [ACPCore setLogLevel:ACPMobileLogLevelWarning];// [ACPCore setLogLevel:ACPMobileLogLevelError];
ACPCore.setLogLevel(ACPMobileLogLevel.debug)// ACPCore.setLogLevel(ACPMobileLogLevel.verbose)// ACPCore.setLogLevel(ACPMobileLogLevel.warning)// ACPCore.setLogLevel(ACPMobileLogLevel.error)
The Experience Cloud ID service provides a cross-channel notion of identity across Experience Cloud solutions and is pre-requisite for most implementations.
Confirm that you have the right Experience Cloud Org ID in the Mobile Core settings page, as mentioned in Get the SDK.
Import the Identity framework into your project:
import com.adobe.marketing.mobile.*;
Register the framework with Mobile Core:
public class MobiletApp extends Application {@Overridepublic void onCreate(){super.onCreate();MobileCore.setApplication(this);try {Identity.registerExtension();} catch (Exception e) {//Log the exception}}}
Add the Identity framework into your project
#import <ACPIdentity_iOS/ACPIdentity_iOS.h>
import ACPIdentity_iOS
Register the Identity framework with Mobile Core
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {[ACPIdentity registerExtension];// Override point for customization after application launch.return YES;}
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {ACPIdentity.registerExtension()return true}
After successful configuration, you'll see the Experience Cloud ID generated and included on every network hit sent to Adobe. Other automatically generated and custom will also be sent with each hit.
This section shows how to start collecting lifecycle metrics. Setup Analytics or other Experience Cloud solution extensions in order to view, and report on this data in those respective solutions.
Lifecycle metrics are valuable, out-of-the-box information about your app user. These metrics contain information on the app user's lifecycle such as device information, install or upgrade information, session start and pause times, etc. You may also choose to set additional, lifecycle metrics.
Import the Lifecycle framework:
import com.adobe.marketing.mobile.*;
Register the framework with Mobile Core:
public class TargetApp extends Application {​@Overridepublic void onCreate() {super.onCreate();MobileCore.setApplication(this);​try {Lifecycle.registerExtension();} catch (Exception e) {//Log the exception}}}
With the onResume function, start Lifecycle data collection:
@Overridepublic void onResume() {MobileCore.setApplication(getApplication());MobileCore.lifecycleStart(null);}
Setting the application is only necessary on activities that are entry points for your application. However, setting the application on each Activity has no negative impact and will ensure that the SDK will always have the necessary reference to your application. So, we recommend calling setApplicationin each of your activities.
Finally, you may use the onPause function, to pause the lifecycle data collection:
To ensure accurate session and crash reporting, this call must be added to every activity.
@Overridepublic void onPause() {MobileCore.lifecyclePause();}
Import the Lifecycle framework:
#import <ACPLifecycle_iOS/ACPLifecycle_iOS.h>
Register the framework with Mobile Core by adding the following in your app's didFinishLaunchingWithOptions:
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {[ACPLifecycle registerExtension];​ // Override point for customization after application launch.return YES;}
Start Lifecycle data collection by adding lifecycleStart to your app'sdidFinishLaunchingWithOptions
// Objective-C- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {[ACPLifecycle registerExtension];[ACPCore lifecycleStart];return YES;}
Pause Lifecycle data collection when your app has entered the background:
// Objective-C- (void) applicationDidEnterBackground:(UIApplication *)application {[ACPCore lifecyclePause];}
Import the Lifecycle framework:
import ACPLifecycle_iOS
Register the framework with Mobile Core by adding the following in your app's didFinishLaunchingWithOptions:
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {ACPLifecycle.registerExtension();​ // Override point for customization after application launch.return true;}
Start Lifecycle data collection by adding lifecycleStart to your app'sdidFinishLaunchingWithOptions
// Swiftfunc application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {ACPCore.start {ACPCore.lifecycleStart(nil);}return true}
Pause Lifecycle data collection when your app has entered the background:
// Swiftfunc applicationDidEnterBackground(_ application: UIApplication) {ACPCore.lifecyclePause()}
See Lifecycle Metrics, for complete usage reference.
You may use the following screen and action tracking APIs in order to start measuring your user's engagement with your app.
Actions are events that occur in your app. Use this API to track and measure an action - each action has one or more corresponding metrics that are incremented each time the event occurs. For example, you might call this API for each new subscription each time an article is viewed, or each time a level is completed.
This section shows how to start tracking app screens and user actions. Setup Analytics or other Experience Cloud solution extensions in order to view, and report on this data in those respective solutions.
You must call this API when an event that you want to track, occurs. In addition to the action name, you may send additional context data with each track action call.
public static void trackAction(final String action, final Map<String, String> contextData)
Map<String, String> additionalContextData = new HashMap<String, String>();additionalContextData.put("customKey", "value");MobileCore.trackAction("loginClicked", additionalContextData);
States represent screens or views in your app. Each time a new state is displayed in your application, for example, when a user navigates from the home page to the news feed, this API may be called.. This method sends an Analytics state tracking hit with optional context data.
In Android, trackState is typically called each time a new activity is loaded
public static void trackState(final String state, final Map<String, String> contextData)
Map<String, String> additionalContextData = new HashMap<String, String>();additionalContextData.put("customKey", "value");MobileCore.trackState("homePage", additionalContextData);
See Mobile Core API Reference, for complete usage reference.