> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/analytics.md). # Analytics Analytics is now your home for your Reports, Dashboards, and Attribution views. It can be found in the left nav sidebar in your HockeyStack app. **Reports - All reports and report folders in one place.** * In the Reports page, you can do the following actions: * View: Reports, Folders, Dashboards your report is used in, Edit History. * Search for specific reports * Add: New Report or Folder * Folders: Rename or Delete * Reports: Edit, Duplicate or Delete *** **Dashboards: All dashboards and dashboard folders in one place.** In the Dashboards page, you can do the following actions: * View: Dashboards, Folders, Reports used in your dashboard. * Search for specific dashboards * Add: New Dashboard or Folder * Folders: Rename or Delete * Reports: Rename, Duplicate or Delete *** **Attribution views: All your attribution-related views in one place.** In the attributions views page, you can do the following actions: * View: Attribution views * Search for specific attribution views * Add: New Attribution View --- # 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.hockeystack.com/marketing-intelligence/analytics.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.