"app.version":"0.0.0.1",//optional, default value = ''
"analytics.offlineEnabled":true,//optional, default value = false
"session.timeout":30//optional, default value = 30
If the key analytics.offlineEnabled is set to true, then timestamp(ts) is included in the Adobe Analytics request.
The key lifecycle.sessionTimeout represents the period, in seconds, that must elapse between the time the app is launched and before the launch is considered to be a new session. This timeout also applies when your application is sent to the background and reactivated. The default value is 30 seconds.
To send data to multiple report suites, use commas to separate RSIDs in the configuration code block. For example: "analytics.rsids": "example.rsid1,example.rsid2" causes the SDK to send data to the example.rsid1 and example.rsid2 report suites.
After being initialized, the SDK automatically collects and transmits lifecycle metrics to Adobe Analytics. For a complete list of metrics, please read the document on Lifecycle metrics.
3. Enable debug logging
By default, the SDK hides internal exceptions and prints error messages in the console log. To allow the SDK to throw those exceptions, enable debug mode.
4. Track screens and user actions
You can use the following screen and action tracking APIs to measure your user's engagement with your app.
Actions are events that occur in your app. Use this API to track and measure an action, where each action has one or more corresponding metrics that increment each time the event occurs. For example, you can call this API for every new subscription, every time an article is viewed, or every time a level is completed.
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).
After the SDK is initialized, Lifecycle metrics are automatically sent to Adobe Analytics. A complete list of the metrics that are collected and sent can be found below:
Triggered at first run after installation or re-installation.
Date of first launch after installation. The format is M/d/yyyy, and an example is 5/3/2017.
Triggered at the first run after upgrade or when the version number changes.
Days since last upgrade
Number of days since the application version number changed.
Launches since last upgrade
Number of launches since the application version number changed.
Daily Engaged Users
Triggered when the application is used on a particular day. Important: This metric is not automatically stored in Adobe Analytics. You must create a processing rule that sets a custom event to capture this metric.
Monthly Engaged Users
Triggered when the application is used during a particular month. Important: This metric is not automatically stored in Analytics. You must create a processing rule that sets a custom event to capture this metric.
Triggered on every run, including crashes and installs. This value is also triggered when the app is resumed from the background after the lifecycle session timeout is exceeded.
Previous Session Length
Reports the number of seconds that a previous application session lasted, based on how long the application was open and in the foreground.
The number of times the application was launched or brought out of the background.
Days since first use
Number of days since the first run.
Days since last use
Number of days since the last use.
Hour of Day
Measures the hour the app was launched and uses the 24-hour numerical format. Used for time parting to determine peak usage times.
Day of Week
Measures the day of the week the app was launched.
Stores the application name and version in the AppName BundleVersion (app version code) format. An example of this format is MyAppName 1.1(1). This value will be populated from the app ID provided in the SDK configuration.
Stores the device name.
Operating system version
Operating system name and version.
Width x height, in pixels.
The SDK running mode, for example, Application/Extension.
5. Validate requests to Adobe Analytics
The following blurbs shows example of Adobe Analytics events: