> For the complete documentation index, see [llms.txt](https://help.blings.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blings.io/docs/analytics-reporting/views-engagement.md).

# Views & Engagement

Understanding how people interact with your videos is crucial for measuring success. Here are the primary metrics you'll see in your Blings dashboard:

## Definitions

* **Impressions** – The number of times your video or thumbnail is loaded in an email, page or feed. An impression doesn't mean the video was played.
* **Plays** – The number of times viewers click the play button. Plays are usually a subset of impressions.
* **Views (Completions)** – The number of times a viewer finishes watching the main content. Depending on the flow, you can define a view as reaching a specific scene or threshold.
* **Average watch time** – How long viewers stay engaged with your video. Longer watch times indicate higher interest.
* **Engagement rate** – The percentage of impressions that result in a play (plays ÷ impressions).
* **Completion rate** – The percentage of plays that result in a view (views ÷ plays).

Use these metrics to identify which videos grab attention and which need improvement. Comparing engagement rates across different segments (new vs. returning users) can reveal valuable insights.


---

# 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:

```
GET https://help.blings.io/docs/analytics-reporting/views-engagement.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.