# 6. Do: Define key metrics Few experiences are more frustrating in reading a data dashboard than a lingering question. * What makes a wallet in your analysis “active”, or “old” or “new”? * What are the specific criteria you used to define a “sold-out” NFT collection? * What does the TVL of this particular protocol contain and why? Why did you choose a particular time span or frequency of measuring your metric? * What does this abbreviation mean? Define these either towards the start of your dashboard, and/or the first time they come up. The same goes for a metrics-dashboard: You can define metrics next to the chart, or all in a separate Index. Make your data visualizations into *friendly data graphics* for your audience (Tufte, p. 183). --- # Agent Instructions: 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: ``` GET https://docs.metricsdao.xyz/analyst-resources/tips-for-an-impactful-analytics-dashboard/dos/6.-do-define-key-metrics.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.