For more information on Analytics in general please see the PASI Analytics Overview.

See the PASIprep Analytics page for full detail on the events that are being tracked.

The objective of incorporating analytics into PASIprep is to understand how often a functionality is accessed in the application, so the team can better understand the impact of certain functionality and changes depending on frequency of user accessing that particular functionality.

Page tracking should be added to all PASIprep distinct views (this is also the same list of views where permalinking (permalink_guidelines) is available).

Since most operations in PASIprep requires user to access a specific page to perform that function (e.g. going to an “Add” screen to add an item), event tracking should be used only when page view tracking is not sufficient to determine if a user has accessed a function or not. For actions that display a confirmation dialog, the event should be recorded when the confirmation dialog opens, and so will be sent regardless of whether or not the user clicks 'Yes' to the confirmation.

e.g. Most 'delete' functions simply involves a confirmation dialog and is not trackable as a 'page view' - thus an event should be used to determine whether the user have accessed the function (e.g. an event will be tracked when the Delete Confirmation Dialog displays).

Events are tracked using the convention “Category>Action>Label”.

Below are guidelines on selecting/creating categories, actions and labels.

The category should represent the general area/functionality of the event:

Commonly used Categories:

Action are unique for each event and should accurately describe the event PASI intends to track, e.g. “Download DAR”, “Delete Exam Registration”, “Undelete Exam Registration”, etc.

Labels should be a supplementary description of the action. It generally should describe how user performs the action.

The labels below are generic labels description that should be utilize as much as possible.