> For the complete documentation index, see [llms.txt](https://docs.admira.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.admira.com/english/management/stats/stats-by-content.md).
# Stats by content
The system allows us to select the content for which we want to see the broadcast data.
Stats by content
The graphs will show the number of passes of the selected content, according to the date that we enter at the top.
Stats
We can see the number of passes in three ways:
1. Reproductions between specific dates or the same day by hours (depending on whether we choose several days or just one in the dates above). In the drop-down box you can choose whether to show the reproductions of all the players at the same time in which that content is or only one in particular.
Plays between specific dates
2. Passes of content by player with broadcast percentage according to the player. If we select the button “change the type of graph”, we will see the number of total passes per player
Pass content by player
3. Total reproductions during the different months of the year
Total plays
---
# 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.admira.com/english/management/stats/stats-by-content.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.