> For the complete documentation index, see [llms.txt](https://everyday-digital.gitbook.io/analytics-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everyday-digital.gitbook.io/analytics-docs/content-specific-analytics/learning-story-logs.md). # Learning Story Logs ## Learning Story Logs **Story Logs allow you to access a detailed account of every user's interaction with a story.** ## How to view Logs **Open Analytics, open a Story, and access the Logs section from the left-hand menu.** View more detailed (and archived) logs by selecting the options icon on the log, and then selecting View Log. {% embed url="" %} ## **Log Status** **Story Logs** allow you to see the **state/progress** of each user. | Story Progress State | Description | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | **Started** | Indicates that the user is busy doing the story for the first time. | | **In Progress** | Indicates that the user has started the story. | | **Completed** | This indicates that the user has completed the story (this will show in the export data). | | **Archived** | Old logs of previous story versions that a user has completed. Logs are archived once a user completes a newer version of a story. | {% hint style="warning" %} **Whenever a user chooses to Redo a story, their progress will be reset.** Results from the redo will overwrite the user's previous log, and old logs will be archived. {% endhint %} ## Log Options {% embed url="" %} Select the cogwheel icon to view options {% endembed %} | Story Log Option | Description | | --------------------- | ----------------------------------------------------------------------------------------- | | **View Log** | View an individual user's story log | | **Force Complete** | If you want to set the user's status to "complete" | | **Delete Story Data** | If you want to remove the user's recorded data based on their interaction with the story | | **Delete App Data** | If you want to remove the user's recorded data from their interaction with a platform app | ## Export Logs **To export the story logs, simply select the export icon (top right) from the Logs section.**
### **What does the Log .csv export contain?** | Column | Log description | | ---------------- | --------------------------------------------------------------------------------- | | **Firstname(s)** | User's first name(s) | | **Lastname** | User's last name | | **Status** | In Progress, Completed, Redoing | | **Passed** | Passed / Failed | | **Attempts** | Number of attempts (if allowed) | | **Duration** | Time taken to complete (hh:mm:ss) | | **Score** | User's score expressed as a percentage | | **Last update** | Date & time when the last story attempt was completed | | **Version** | [Story build version](/analytics-docs/content-specific-analytics/story-builds.md) | ## Export Group Logs From [Analytics](/analytics-docs/analytics-explained/real-time-analytics.md), you can export logs per [Group](https://everyday-digital.gitbook.io/groups-cohort-docs/groups/creating-groups). Exporting Group Logs means that you are **exporting users from all groups and comparing content/pathway records**. The **export** is delivered in a **.csv** format and contains the following data: * **Firstname** - User's first name * **Lastname** - User's last name * **Age** - User's age (if supplied) * **Email** - User's email address * **Telephone** - User's telephone number (if supplied) * **Country** - User's country of origin * **City** - User's city of origin * **Registered** - Date and time of user's account registration/sign up * **Group Status** - Active or Nudged * **Groups** - List of all groups a user has been added to * **Status** - Started (the user has opened the content/pathway), In Progress (the user has at least completed 1 page/activity), Complete, or Empty. * **Progress** - Percentage completed * **Last Update** - Date and time of user's last recorded activity {% hint style="info" %} User rows with an empty status mean they have not opened or engaged with the content/pathway. {% endhint %} ### Step-by-Step Group Log Export 1. **Open Analytics and select Groups.** 2. **Select the first group icon, top right.**
3. **Set the preferred format and content types.** The Format Options include Grouped Logs (Default), which formats the logs by group, and Inline Logs, which lists content types in a column. Choose the Content Types that should be included in your export of logs. ![](/files/8y75qLCmXacIOkpzcPG0) 4. **Select Export to download the group logs.** ## Build Analytics **To see a specific release/build, you can select one using the filter option.** By default, all builds are loaded for analysis. Next to the question title you can see the range of builds being displayed. {% embed url="" %} ## Individual User Results & Logs | User Log | Description | | ----------------- | ------------------------------------------- | | **Highest Mark** | Highest mark achieved by a user | | **Average Mark** | User average | | **Lowest Mark** | Lowest mark achieved by a user | | **Average Time** | Average time required to complete the story | | **Lowest Mark** | Lowest mark achieved by a user, per chapter | | **Average Score** | Average score, per chapter | | **Highest Score** | Highest score achieved, per chapter | ### **View Log, Delete Story Data, or Delete App Data** Select View Log via the cogwheel icon to see the exact logs uploaded from the user's app. | Log Type | Log Detail | | --------------------- | ----------------------------------------------------- | | **View Log** | Time taken to complete each page | | | Total score, max score and percentage | | **Delete Story Data** | When last the log was updated | | **Delete App Data** | Delete a user's complete story logs (for all stories) |

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://everyday-digital.gitbook.io/analytics-docs/content-specific-analytics/learning-story-logs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.