> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/displays/displays_metrics.md). # Reporting Xibo has a variety of reports to help users assess network health and uptime and Display statistics. Proof of Play data offers further insights into content performance shown across your Display network to reveal trends to enable stakeholders to refine content scheduling and placement for improved targeting and audience engagement. Reports can be viewed in real time, emailed as a PDF to users and saved for future reference as well as scheduled to run on a Daily, Weekly, Monthly or Yearly basis. Available metrics can be found by selecting **All Reports** under the **Reporting** section of the main CMS menu. Similar Reports are grouped together to make it easier to find the data you need, which are presented as Charts as well as Tabular data so you can easily identify patterns and trends. ## FAQs ***Can I remove the logo shown on exported reports?*** Go to Settings under the Administration section of the main CMS menu and select the General tab to control whether the logo should be shown. ***Can I set a collection of proof of play stats by default for Displays?*** From Settings under the Administration section of the main CMS menu, select Displays to enable Stats/Layout Stat Collection and Aggregation Level default for Displays. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.xibosignage.com/displays/displays_metrics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.