> For the complete documentation index, see [llms.txt](https://docs.motar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motar.com/motar-core-services/intro-to-core-services/studio/listing-performance-metrics.md).

# Listing Performance Metrics

## Video

MOTAR gives creators and instructors insight into how their video assets are performing through CMI5 & xAPI standardized **metrics**. These analytics make it easy to measure learning impact, optimize content, and track skill development.

By combining these metrics, instructors can **gauge learner engagement, identify areas of improvement, and validate skill acquisition** directly within the MOTAR platform. This data helps ensure content is not just delivered, but learned, retained, and applied.

To view metrics on a video asset, navigate to the asset details page

* Click the **Metrics** tab

<figure><img src="/files/yhh45xUQ2YnPWPEIKm41" alt=""><figcaption></figcaption></figure>

### Playback & Engagement Metrics

<table><thead><tr><th width="198">Name</th><th width="337">Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Launches</strong></td><td>How many times launched</td><td>Launched <strong>159</strong> times.</td></tr><tr><td><strong>Downloads</strong></td><td>Number of times the video has been downloaded</td><td>Downloaded <strong>53</strong> times.</td></tr><tr><td><strong>Completion Rate</strong></td><td>% of viewers who reach 100 %</td><td><strong>92.3%</strong> completion rate.</td></tr></tbody></table>

***

## Audio

To view metrics on an audio asset, navigate to the asset details page

* Click the **Metrics** tab

<figure><img src="/files/W4YT0crT8JcnPXaEgdRd" alt=""><figcaption></figcaption></figure>

### Playback & Engagement Metrics

<table><thead><tr><th width="198">Name</th><th width="337">Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Launches</strong></td><td>How many times launched</td><td>Launched <strong>159</strong> times.</td></tr><tr><td><strong>Downloads</strong></td><td>Number of times the audio has been downloaded</td><td>Downloaded <strong>53</strong> times.</td></tr><tr><td><strong>Completion Rate</strong></td><td>% of listeners who reach 100 %</td><td><strong>92.3%</strong> completion rate.</td></tr></tbody></table>


---

# 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.motar.com/motar-core-services/intro-to-core-services/studio/listing-performance-metrics.md?ask=<question>&goal=<endgoal>
```

`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.
