> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/analyze-with-dashboards/analytics/analytics-homepage-overview.md). # Analytics homepage overview ## Introduction Chord's analytics platform is a powerful tool that helps businesses collect, organize, and interpret data, transforming raw information into actionable insights. With customizable dashboards and reports, brand operators, analysts, and marketers can visualize trends, measure key metrics, and optimize strategies across various channels, empowering teams to drive growth and efficiency with confidence. Below is a tour of the **Analytics Homepage** and its key features. ## Page overview The **Analytics Homepage** consists of the following features: * **Pinned Reports** * **My Reports** * **Shared Reports** * **Explores** * **Quickstarts** More information on each of the above features is provided below. {% hint style="info" %} **A note on terminology:** A report on the Chord platform can refer to either a **dashboard** or a **Look** (which also known as an **explore**). A **dashboard** is made up of a collection of **Looks** (**explores**). {% endhint %} ### Pinned reports This is the first page you will land on under the **Analytics Homepage**. The\*\* Pinned Reports **tab will display pinned dashboards and Looks.** Pinned Reports \*\*allows users to view key reports as designated by admin users, making it easy for all stakeholders to access vital company reports in one central location. ### My reports You'll be able to see all of the dashboards and Looks in your personal folder via the dropdown menu on the top left of the **My Reports** page. You will also be able to create new dashboards and Looks from this page, as well as share and import dashboard links with your team. You can also share a report to your organization's shared reports folder from your personal reports folder as well. ### Shared reports By default, the **Shared Reports** page will display all of the shared reports in your organization. Use the dropdown menu on the left to view the list of all shared dashboards and Looks. Additionally, any custom, personal reports that are created ***and shared*** to your organization via the\*\* My Reports \*\*page will also appear here. ### Explores The **Explores** page is where you can dive into your data a bit deeper and use different data dimensions to create individual measures to build visualizations and reports. You can use the dropdown menu on the top left to explore different categories of data that Chord collects on behalf of your store. ### Quickstarts Chord Commerce's **Quickstarts** is where you will find a collection of Looks and dashboards created by the Chord team that you can use to build reports that suit your business needs. You can search and filter different quickstart templates in our library to find what you are looking for in no time. For additional information about quickstarts, visit our guide [here](/analyze-with-dashboards/analytics/using-quickstarts.md). --- # 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.chord.co/analyze-with-dashboards/analytics/analytics-homepage-overview.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.