Adobe Analytics

Configure the Analytics extension in Experience Platform Launch

  1. In Experience Platform Launch, click the Extensions tab.

  2. On the Catalog tab, locate the Adobe Analytics extension, and click Install.

  3. Type the extension settings. For more information, see Configure the Analytics Extension.

  4. Click Save.

  5. Follow the publishing process to update SDK configuration.

Workflow Overview for Launch, Mobile SDK, and Adobe Analytics

Configure the Analytics Extension

Adobe Analytics Extension Configuration

Report suites

Want to know how to find report suite IDs? See Report Suites.

Select one or more mobile-enabled report suite identifiers from the combo box to which the Analytics data should be sent. Only report suite identifiers that belong to a company and that are enabled for mobile can be selected. For information on how to enable mobile for your report suite, see [Mobile Management] (

To narrow the search for a report suite identifier, type a string in the combo box text field. After a valid report suite identifier has been selected, this identifier appears in a tag below the combo box (shown above). To remove a report suite ID, click on the X next to the ID you want to remove. Report suite IDs can also be configured for the Development and Staging environments.

Tracking server

Want to know what a tracking server is and where to find it? For more information, see Correctly populate the trackingServer and trackingServerSecure variable.

Type the tracking domain to which all Analytics requests should be made.

Offline enabled

Do you need offline tracking? For more information, see Offline tracking.

When the Offline Enabled checkbox is selected, Analytics hits are queued when your device is offline and are sent later when your device is back online. To use offline tracking, ensure that your report suite is timestamp enabled .

If your report suite is timestamp enabled, the checkbox must be selected. If your report suite is not timestamped enabled, leave the checkbox deselected. If this setting is not configured correctly, data will be lost.

If you are not sure whether your report suite is timestamp enabled, contact Customer Care.

If you currently send mobile SDK data to a report suite that also collects data from web JavaScript, you might need to set up a separate report suite for mobile data or include a custom timestamp on all JavaScript hits that use thes.timestampvariable. For more information, contact Customer Care.

Audience Manager forwarding

For more information about Analytics server-side forwarding to Audience Manager, see Analytics sever-side forwarding.

If you set up Analytics server-side forwarding to Audience Manager, select the Audience Manager Forwarding checkbox. When this checkbox is selected, all SDK requests to Analytics servers are sent with an expected response code of 10. This step ensures that Analytics traffic is forwarded to Audience Manager and that the Audience Manager User Profile is correctly updated in the SDK.

Backdate previous session info

Select the Backdate Previous Session Info checkbox only if you have timestamp-enabled report report suites.

When you select this checkbox, the SDK backdates the end-of-session lifecycle information so that this information can be attributed into its correct session. Session information currently consists of crashes and session length. The SDK also backdates the session information hit to 1 second after the last hit of the previous session. This means that crashes and session data will correlate with the correct date on which they occurred. One hit is backdated each time a new launch of the application is occurs.

For example, if you select the checkbox, Lifecycle session information or crash events are backdated to one second after the last hit was sent. If you do not select the checkbox, Lifecycle data is attached to the first hit of the subsequent session.

If this option is disabled, the Adobe SDK attaches the session information to the current lifecycle.

Batch limit

This setting creates a threshold number of hits to be sent in consecutive calls. For example, if you type or select 10, each Analytics hit before the 10th hit is stored in the queue. When the 10th hit comes in, all 10 hits are sent to Analytics in the order in which they were generated.

If you set a value greater than 0, ensure that the Offline Enabled checkbox is also selected.

The default value for this setting is 0, which means that hit batching is disabled, and all hits are immediately sent to Analytics as they are generated.

Launch hit delay

Number of seconds to wait before Analytics launch hits are sent from the SDK. Ensure that this setting is set at 5s or greater when using acquisition functionality from the Mobile Services extension.

Add Analytics to your app

React Native
  1. Add the Mobile Core and Analytics extensions to your project using the app's Gradle file.

implementation ''
implementation ''


  1. Import the Analytics extension in your application's main activity.


​ 1. Add the Mobile Core and Analytics extensions to your project using Cocoapods.

  1. Add following pods in your Podfile:

pod 'ACPCore'
pod 'ACPAnalytics'
  1. Import the Analytics and Identity libraries:


#import "ACPCore.h"
#import "ACPAnalytics.h"
#import "ACPIdentity.h"


import ACPCore
import ACPAnalytics
import ACPIdentity


Install Analytics

npm install @adobe/react-native-acpanalytics
react-native link @adobe/react-native-acpanalytics

Importing the extension

import {ACPAnalytics} from '@adobe/react-native-acpanalytics';

Getting the extension version

ACPAnalytics.extensionVersion().then(version => console.log("AdobeExperienceSDK: ACPAnalytics version: " + version));

Register Analytics with Mobile Core

React Native


To call the set up methods that call the setApplication() method in the onCreate() method:

public class MobileApp extends Application {
public void onCreate() {
try {
Analytics.registerExtension(); //Register Analytics with Mobile Core
} catch (Exception e) {
//Log the exception

Important: Analytics depends on the Identity extension and is automatically included in Core by Maven. When manually installing the Analytics extension, ensure that you add the identity-1.x.x.aar library to your project.

In your app'sapplication:didFinishLaunchingWithOptions, register Analytics with Mobile Core:


- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
[ACPCore configureWithAppId:@"yourAppId"];
[ACPAnalytics registerExtension];
[ACPIdentity registerExtension];
[ACPCore start:nil];
// Override point for customization after application launch.
return YES;


func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
ACPCore.configure(withAppId: "yourAppId")
// Override point for customization after application launch.
return true;

Important: Analytics depends on the Identity extension and is automatically included in the Core pod. When installing the Analytics extension manually, ensure that you added the libACPIdentity_iOS.a library to your project.


import { ACPAnalytics } from "@adobe/react-native-acpanalytics";
initSDK() {

Send Lifecycle Metrics to Analytics

To automatically report on the application lifecycle details in Analytics, ensure that you properly configure the lifecycle data collection. For more information, see Lifecycle Metrics.

Send app states and actions to Analytics

To track mobile app states and actions in Adobe Analytics, implement the trackAction and trackState APIs from the Mobile Core extension. For more information, see Track app actions and Track app states.

trackState reports the View State as Page Name, and state views are reported as Page View in Analytics. The value is sent to Analytics by using the page name variable (pagename=value).

trackAction reports the Action as an event and does not increment your page views in Analytics. The value is sent to Analytics by using the action variable (action=value).

Integrations with Experience Platform solutions and services

Analytics for Target (A4T)

To see the performance of your Target activities for some segments, you can set up the Analytics extension for Target (A4T) cross-solution integration by enabling the A4T campaigns. This integration allows you to use Analytics reports to examine your results. If you use Analytics as the reporting source for an activity, all reporting and segmentation for that activity is based on Analytics data collection. For more information, see Target.

Server-side forwarding with Audience Manager

To enable the ability to share Analytics data with Audience Manager, in the Launch UI, select the Audience Manager Forwarding checkbox and install the Audience Manager extension. For more information, go to Audience Manager.

Audio and Video Analytics

For more information about collecting audio and video analytics, see Media Analytics for Audio and Video.

Event serialization

Event serialization is not supported by processing rules. To set serialized events directly on the hits sent to Analytics, use the following syntax in context data parameters:




cdata.put("&&events", "event1:12341234");


//create a context data dictionary
HashMap cdata = new HashMap<String, Object>();
// add events
cdata.put("&&events", "event1:12341234");
// send a tracking call - use either a trackAction or TrackState call.
// trackAction example:
MobileCore.trackAction("Action Name", cdata);
// trackState example:
MobileCore.trackState("State Name", cdata);



[contextData setObject:@"eventN:serial number" forKey:@"&&events"];


//create a context data dictionary
NSMutableDictionary *contextData = [NSMutableDictionary dictionary];
// add events
[contextData setObject:@"event1:12341234" forKey:@"&&events"];
// send the tracking call - use either a trackAction or trackState call.
// trackAction example:
[ACPCore trackAction:@"Action Name" data:contextData];
// trackState example:
[ACPCore trackState:@"State Name" data:contextData];


Using trackState APIs to send data to Adobe Analytics

Configuration keys

To update the SDK configuration programmatically, use the following information to change your Analytics configuration values.






See Tracking Server



See Report Suites

Multiple report suite IDs can be comma separated with no space in- between. For example: "rsids" : "rsid" "rsids" : "rsid1,rsid2"



See Audience Manager Forwarding



See Offline Enabled



See Backdate Previous Session Info.

React Native

update Analytics Configuration


HashMap<String, Object> data = new HashMap<String, Object>();
data.put("analytics.server", "");
data.put("analytics.rsids", "rsid1,rsid2");
data.put("analytics.batchLimit", 10);
data.put("analytics.offlineEnabled", true);

update Analytics Configuration



NSDictionary *updatedConfig = @{@"analytics.server":@"", @"analytics.rsids":@"rsid1,rsid2", @"analytics.batchLimit":@(10), @"analytics.offlineEnabled":@YES};
[ACPCore updateConfiguration:updatedConfig];


let updatedConfig = ["analytics.server":"", "analytics.rsids":"rsid1,rsid2", "analytics.batchLimit":10, "analytics.offlineEnabled":true]



ACPCore.updateConfiguration({"analytics.server":"", "analytics.rsids":"rsid1,rsid2", "analytics.batchLimit":10, "analytics.offlineEnabled":true});

For more information, see Configuration API Reference.