> 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/looks-vs-dashboards.md). # Looks vs Dashboards ### Introduction Looks and dashboards are the two major building blocks of Chord Analytics. The dashboards present data and insights using customizable charts, graphs, and reports. You can drill into all dashboards and queries to discover information in multiple layers. {% hint style="info" %} Take a look at [Cloud Skills Boost](https://www.cloudskillsboost.google/catalog?keywords=Looker\&locale=\&format%5B%5D=any\&level%5B%5D=any\&duration%5B%5D=any\&modality%5B%5D=any\&language%5B%5D=any) to learn more about LookML. {% endhint %} ### What are Looks? Looks are created from the Explores. They are saved visualizations and stand-alone reports that you can use to answer one specific question from your data. ### Creating a Look For instance, we want to know the Order Average Gross Revenue value for each Month this past year. Click Explore Select Order Created Year and click Filter by field

Select Order Create Date = Month Scroll down to Measure and select Average Gross Revenue

Click Run To save it as a Look, click the gear icon, and click Save, Save as Look. Provide a Title "Average Monthly" and click Save

You have just created a Look! ### What are dashboards? Dashboards allow you to place multiple tables, graphs or looks on one page to get a quick view of the related content. You can also make dashboards interactive and filter them down to the specific data that interest you. ### Creating a dashboard from a look Suppose you want to add the newly created Look report to an existing Dashboard. Navigate to Folders--> My Folder and select the "Average Monthly" in the Look section You can click Add to Dashboard or click the gear icon and select Save --> Save to existing dashboard (you can also save to a new dashboard)

In the **Add to a Dashboard in this folder** form select an existing dashboard: In this example "Current Week"

{% hint style="info" %} Add Look to Dashboard - This option will add a Look-linked tile, and if you make any changes to the Look, it will reflect in your dashboard. {% endhint %} Click Save to Dashboard - this tile is copied as a query tile to the existing Dashboard. That option is the most preferred choice as the Dashboard will not depend on the Look; any changes to the Look will not affect the tile in your Dashboard. To verify that the new Look has been added to the Dashboard, navigate to Folder --> My Folders and click on the "**Current View**" Dashboard. You should see Average Monthly visualization display

You've just added a Look to your existing Dashboard! --- # 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/looks-vs-dashboards.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.