Namespace Appearition.Analytics

Classes

Activity

An activity is a collection of several activity events. When recording event, it's a good habit to group them per activity. One activity can be a single UI panel, for instance. Within that activity, you can record multiple events, such as where the user clicks and when.

Activity.ActivityEventContainer<T>

Container class for an activity event data. Each class which inherits from Activity can use it to facilitate transportation and demand of additional parameters.

ActivityEvent

Contains the data for a single event as part of an activity. An event should contain an EventCode (referring to what kind of event this specific event is). The EventData should contain additional key-value-pair data you may want to attach to this event. If this event is to be shown on the EMS Dashboard, you can check the list of available event codes and required content on the EMS for each module.

AnalyticsConstants

Contains message constants for the Analytics module.

AnalyticsData

Contains a data entry for a single event.

AnalyticsHandler

Handles Analytics related API requests. When wishing to start a session or add content, refer to this handler. This handler will also manage analytics submission based on the application life cycle.

BaseActivityHelper

DeviceInfoConstants

Session

Container for a full analytics session. Sessions are usually divided from the moment the user starts the application until the moment the user closes it. A session is made of Activities, which can be classified as a group of actions made per user. Each of these could be a single UI panel, a functionality of your app, etc.