> For the complete documentation index, see [llms.txt](https://docs.mavenseed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mavenseed.com/creating-content/courses/course-stats.md).
# Course Stats
Are you curious how your videos are performing?
### How to view your Course Video Stats
1. Login with your Mavenseed account and head over to your Site Admin,
2. Clicking on Content then Courses in the left hand menu will display all of your created Courses,
3. Click on the drop-down menu on the course you'd like to review statistics on and choose **Stats.**
This will bring up an array of data regarding the performance of the video content on your course.
{% hint style="info" %}
The **Engagement value** is a custom Mavenseed calculation we're building to assign a single performance number to a piece of content.
{% endhint %}
**This includes:**
* Video Views
* Load Count
* Play Count
* Play Rate
* Hours Watched
### **Updating stats**
To update the stats, click the sync button at the bottom of the list.
{% hint style="danger" %}
This area is still in development. If there is something you'd like to see please let us know!
{% endhint %}
---
# 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://docs.mavenseed.com/creating-content/courses/course-stats.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.