What is the Activity_Accumulator table?
The Activity_Accumulator is the table that tracks user activity. Almost every page a user visits in your system gets recorded here. The Activity_Accumulator table allows you to easily query for user activity, join additional Learn tables, and generate custom reports.
Review users’ activity in the activity accumulator to help with troubleshooting and supporting fair decisions in academic disputes.
In this page you can find:
Structure of the Activity Accumulator table
| Column Name | Description | Data type |
|---|---|---|
| timestamp | Date and/or time at which an event occurred. | datetime |
| event_type | This is the type of activity users did inside Ultra. For example, sign into the platform, access content, submit a test, and others. | varchar(30) Text field with max length of 30 characters |
| pk1 | Primary key for the table. Each record has a unique pk1 ID. | id |
| course_pk1 | Primary key of the course associated with this activity. Each course has a unique ID in the platform. | id |
| content_pk1 | Primary key of the content item associated with this activity. For content access, assessment submission, discussion reply/response and similar events this column is useful to identify content item associated. | id |
| user_pk1 | Primary key of the user associated with this activity. Each user has a unique ID in the platform. | id |
| session_id | Primary key of the user session associated with this activity. | id |
| group_pk1 | Primary key of the course group associated with this activity. | id |
| forum_pk1 | Primary key of the discussion forum association with this activity. | id |
| data | Contains any free-form text data associated with the event. Some events contain useful information in this field, such as name of the course content associated. For events that have this field empty, use pk1 IDs to identify relevant information. | nvarchar(255) Text field with max length of 255 characters |
| internal_handle | Reference to the internal handle of the navigation item associated with page and course access events. | varchar(255) Text field with max length of 255 characters |
| status | Indicates the status of the event. 1 for SUCCESS or 0 for FAILURE. | numeric |
Events registered in the Activity Accumulator
These are the events saved in the “event_type” column.
| Event name | Rule | Available in Original and/or Ultra? |
|---|---|---|
| ASSESSMENT_DRAFT | A user saves a draft on a test or an assignment. Note:
| Ultra |
| ASSESSMENT_SUBMIT | A user submits a test or an assignment. Notes:
| Ultra |
| COMMAND_LINE_TOOL | A user runs a selected command-line tool. | Original |
| CONTENT_ACCESS | A user accesses a course content item. Content items include Tests, Assignments, Discussions, Journals, LTI activities, SCORM packages, Folders, and Learning Modules. Notes:
| Original and Ultra |
| COURSE_ACCESS | A user accesses a course. | Original and Ultra |
| DISCUSSION_DRAFT | A user saves a draft in a reply or response in a discussion. | Ultra |
| DISCUSSION_EDIT | A user edits a reply or response in a discussion. | Ultra |
| DISCUSSION_REPLY | A user posts a reply on a discussion. | Ultra |
| DISCUSSION_RESPONSE | A user posts a response on a discussion. | Ultra |
| LOGIN_ATTEMPT | A user attempts to authenticate into the platform. This attempt can be a success or a failure. | Original and Ultra |
| LOGOUT | A user logs out from the platform. | Original and Ultra |
| MODULE_ACCESS | A user accesses a Module. Note:
| Original |
| PAGE_ACCESS | A user accesses a page. Event related with admin panel pages. | Original and Ultra |
| PASSWORD_CHANGE | A user changes a password. This includes password change by self, by a privileged user, or via forget password. | Original and Ultra |
| RESET_MFA | A privileged user resets an MFA | Original |
| SCHEDULED_TASK | Event that results from the running of a selected scheduled task. | Original |
| SESSION_INT | A session is initiated in the system. | Original and Ultra |
| SESSION_TIMEOUT | A user’s session had a timeout due to user inactivity. | Original and Ultra |
| START_IMPERSONATION | An administrator or higher role log in as a user into the platform. | Original |
| STORED_PROCEDURE | Event that results from the running of a selected stored procedure. | Original |
| TAB_ACCESS | A user accesses a tab. | Original |
Key considerations:
- The Activity Accumulator table registers events of all users no matter the role.
- User actions made in the mobile app are also included in the Activity Accumulator table.
- Content accessed with Ally records events in the Activity Accumulator.
Turn on Activity_Accumulator
- In the Administrator Panel, under Tools and Utilities, select System Reporting.
- Select Auto-Reporting Options.
- To record system activity in the Activity_Accumulator table, select Yes in the Event tracking field.
The default state is on. If Event tracking is turned off, no data will be sent to the Activity_Accumulator table.
Two Activity_Accumulator tables
The Activity Accumulator records all users' interactions on the platform. This produces large amounts of data. For more effective data management, there are two Activity_Accumulator tables.
- BBLEARN schema has the most recent activity data. By default, it retains the most recent 6 months of data. A daily process copies data into BBLEARN_STATS to keep it updated.
- BBLEARN_STATS schema is an archival table to hold older records. This table saves historic data and helps for reporting purposes, minimizing performance impact in the main Learn database.
If your institution has data pipeline enabled, the data is sent to snowflake activity_accumulator_archive instead of BBLEARN_STATS.
How much data is retained in Activity_Accumulator?
The amount of data in the Activity_Accumulator table depends on how often PurgeAccumulator runs. PurgeAccumulator runs every 24 hours.
The PurgeAccumulator utility copies the latest records from the BBLEARN schema over to the BBLEARN_STATS schema. Afterwards, the PurgeAccumulator removes all data older than 180 days from the BBLEARN schema.
All the records beyond the configured retention period are removed from BBLEARN but kept in BBLEARN_STATS for reporting purposes.
If your institution has data pipeline enabled, then the data is sent to snowflake activity_accumulator_archive instead of BBLEARN_STATS
