You can track and manage the data that you receive from the app by configuring a variety of variables and metrics.
Standard Variables & Metrics
Each app includes variables and metrics for tracking shopping cart and purchase activities. Some purchase information cannot be handled with processing rules, so the SDK exposes the special
"&&products" context data. For example, you can have variables such as cart additions, cart removals, check outs, orders, and so on. The context data has to be mapped to data in Adobe Analytics. If this variable is populated with a simple mapping from context data, this is the key that maps to it. Leave it blank if the variable is populated by more complex rules in Analytics Admin Tools.
For more information about these variables and metrics, see the following:
The Custom Variables page displays all of the custom Analytics variables that are configured for the report suite that contains your app data. On this page you can enable additional variables and map context data to Analytics variables.
Click Manage App Settings > Manage Variables & Metrics > Custom Variables.
These mappings call the same API that Processing Rules use in Adobe Analytics.
Here is a list of the custom variables that you can configure:
The Custom Properties (or props) answer the question “which one?” Props can be set to a text value that will be associated with other variables and metrics sent in the same hit. The values can be used to filter reports or can be listed in rank order by an associated metric.
When a value is set for a property in a tracking call (or hit), it applies only to that call.
The Custom Variables (or eVars) also answer the question “which one?” However, an eVar value can apply not only to the hit it is sent in, but also to variables and metrics sent in subsequent hits until the value expires or a new value is set.
The Custom List Variables (or Multi-Value Variables) behave the same as variables except they allow you to capture multiple values on one hit. For more information, see list variables in the Adobe Analytics documentation.
The following mappings display in Analytics as being created in Mobile Services.
The friendly name of the data collection variable.
If this variable is populated with a simple mapping from context data, this is the key that maps to it. Leave this field blank if the variable is populated by more complex rules in Analytics Admin Tools.
Click in the context data column and select the context data variable that you would like mapped. The drop-down list contains variables received in the past 30 days, so if the context data you want to map is not in the list you can type it.
Persistence (Custom Variables and Custom List Variables)
Persistence determines the point at which a Custom Variable (eVar) value will expire or will no longer be associated with additional hits. If an eVar has expired when a hit fires, the None value will be associated with that hit for that eVar. This means that no eVar value was active when the hit fired.
You can select one of the following options:
The eVar value persists for the length of the Analytics visit.
The eVar value persists only for the tracking call or hit it in which it was included.
The eVar value persists for all subsequent tracking calls.
Adobe Analytics has a more advanced UI for setting persistence for eVars. If a persistence value is set for the eVar that is not supported in Mobile Services, this value is displayed in the Mobile Services UI.
To manage eVars, click Adobe Analytics Report Suite Manager > Conversion Variables UI.
Enables passing multiple values to be associated with the property in one tracking call. The delimiter must be one character and cannot be a zero or a space.
The delimiter must be one character and cannot be a zero or a space.
You can enable additional variables using the drop-down list at the bottom of each variable section.
Select an unused variable number and type a name. You can optionally provide the context data variable that you would like stored and any additional information.
Metrics (or events) answer the questions how much? or how many?. Events can increment each time the user takes an action or hold numeric values such as a price. Custom metrics include events such as an app was created, the PDF or CSV file was downloaded or exported, a campaign was saved, the SDK was downloaded, a report was run, a link to the App Store was added, an in-app message was activated, and so on.
Select one of the following custom metric types:
Points of interest allow you to define geographical locations that you can use for correlation purposes, target with in-app messages, and so on. When a hit is sent in a point of interest, the point of interest is attached to the hit. For more information about points of interest, see Manage Points of Interest.
You can create, edit, archive/unarchive, and delete link destinations. These destinations can then be called inline when building Marketing Links, push notifications, or in-app messages. For more information about link destinations, see Manage Link Destinations.
Postbacks let you send data collected by Adobe Mobile to a separate third-party server. Leveraging the same triggers and traits you use to display an in-app message, you can configure Mobile to send customized data to a third-party destination. For more information about postbacks, see Configure Postbacks.