Page tracking has been added to every myPass web page as well as the events listed on this page are being tracked to help the PASI team understand the interactions of users with myPass.

See this reference page for more information on the Google Analytics Events.

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

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

Events are categorized based on the area/functionality:

Action describe what the user is performing on screen to trigger the event:

Labels are unique for each event and should accurately describe the event PASI intends to track.

Note that a Category/Action combination can have different labels to indicate different stages of the action/event the user is performing (e.g. “Edit Started” vs “Edit Completed”).

The following security interactions are being tracked using Google analytic events:

The following interactions are being tracked using Google analytic events:

The following interactions are being tracked using Google analytic events:

The following interactions are being tracked using Google analytic events with order management (mainly through the View Document Order History screen):

The following interactions are being tracked using Google analytic events:

When the user have to complete a wizard-style form (i.e. forms with multiple steps/pages), Events will be used to track the user's movement through the multiple steps.

The following are screen flow diagrams that describes what events would be tracked as user move through the wizard/form.

How to read screen flow diagrams:

• Each white block in the diagram represents a ‘screen’ user sees on myPass
  • The blue text identifies the screen shown to the user
  • The black italic text, when present, denotes the event to track when the screen is shown to the user - the event should be tracked every time the user sees the screen.
• Arrows show the possible paths the user has the option of taking for each screen
  • The number (e.g. (1)) denotes an event to track the movement. See the notes below the diagram to determine what user action triggers the event
    • Note: Not every path/action is meant to be tracked.
  • Events are shown as “{Action}>{Label}”; most events in the diagram belong to the same category unless otherwise stated (the category will be underlined).
  • Admin mode events should still always be prefixed with “ADMIN: ”

The following diagram lists the event flow for Order a Transcript in public mode:

transcriptpublicworkflow.vsdx

1. Click>Student Selected – when user clicks [Order] in the Initial Step
2. Add>{Order Item Type} Order Item Added – when user adds an Order Item on “New Transcript Order Item” (in new mode only)
   1. NOTE: {Order Item Type} is:
      1. “Duplicate” if the Order Item is added from the Matching Transcript Order Found dialog
      2. “ASAP”, if the Order Item is to be Issued ASAP (regardless if they went through the ASAP dialog)
      3. “Scheduled” otherwise.
3. Add>Add Another Order Item – when user clicks [Add Another Transcript] on “Review My Transcript Order”
4. Modify>Edit Order Item – when user clicks [Edit] on an item in “Review My Transcript Order”
5. Delete>Remove Order Item – when user clicks [Remove]/[Remove from My Order] to remove an order Item
   1. Delete>Remove Order Item Cancelled– when user clicks [No] on the dialog that appears for removing the Order Item
6. Delete>Cancel Order – when user clicks [Cancel Entire Order] on “Review My Transcript Order”
   1. Delete>Cancel Order Cancelled- when user clicks [No] on the dialog that appears for cancelling the Order
7. View>Return to Order – when user clicks [View My Order]/[Return to Order] (link or button)
   1. View>Return to Order Cancelled – when user clicks on [No] on the dialog that appears
8. Modify>{Order Item Type} Order Item Edited – when user clicks [Save Request] on “New Transcript Order Item” (in edit mode only)
   1. NOTE: {Order Item Type} is:
      1. “ASAP”, if the Order Item is to be Issued ASAP (regardless if they went through the ASAP dialog)
      2. “Scheduled” otherwise.
9. Click>Retry Transcript Payment – when user clicks [Retry Payment] on the Payment Not Received page
10. Click>EPS2 Transcript Payment Launched – when user clicks on [Proceed with Payment] on the Billing Info page
11. Help Click>Post-secondary – when user clicks on the [Can’t find your post-secondary] help tooltip link
12. Contact Click>FOIP Contact – when user clicks on the TAD email address in the FOIP statement
13. Expander>Review Transcript Order Details – when user clicks on [More Details] for an order item
14. Document>Download>Transcript Receipt – when user clicks to download the receipt PDF
15. Document>Download>DAR – when user clicks the [Review Current Marks] button in the ASAP dialog
16. Add>Add Duplicate Order Item – when the Duplicate APAS order dialog is shown

The following diagram lists the event flow for Order a Transcript in admin mode:

transcriptadminworkflow.vsdx

The following diagram lists the event flow for Register for a Diploma Exam in public mode:

derpublicworkflow.vsdx

The following diagram lists the event flow for Register for a Diploma Exam in admin mode:

deradminworkflow.vsdx

The following diagram lists the event flow for Create Rescore Request - Public (myPass)

analytics_event_flow.vsdx