> For the complete documentation index, see [llms.txt](https://docs.legitimate.tech/tag-management-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.legitimate.tech/tag-management-platform/dashboard/legitimate-dashboard-home-screen.md).

# Legitimate Dashboard Home Screen

Once your SKU has been created, your NFTs have been minted, and your tags have been connected you can use your dashboard's home screen to help keep track of your SKU.&#x20;

Your dashboard home screen displays the following information that can be helpful for easily accessing your SKU information. These columns can be filtered to help you easily naviagte your SKUs:&#x20;

<figure><img src="https://2471615621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiXxdLAbs3St8VWpChjnt%2Fuploads%2FZkUarzGqM4LdVtVGwgwt%2FScreenshot%202024-03-19%20at%206.04.05%E2%80%AFPM.png?alt=media&amp;token=0a8a5363-9ad8-4475-b0ec-81dddb10f4e4" alt=""><figcaption></figcaption></figure>

1. The "SKU ID" column displays all the SKUs you have created. You can use this tab to edit each SKU individually by clicking on the pencil button next to the SKU ID number.&#x20;
2. The "views" column tells you how many times the tags in a certain SKU have been tapped. This includes taps that do not lead to an unlock or transfer.&#x20;
3. The "QC" column lets you know if your tags have been encoded properly. If there is a green check mark then all tags have been encoded correctly. If the column displays some #/the number of tags you activated or encoded there may be an error. If this occurs please reach out to the Legitimate team
4. The "Created by" column tells you the date and time a SKU was created&#x20;
5. The "Item Name" and "Notes" Column show you the item name and notes you provided when you created a SKU. These can be updated at any time by editing a SKU&#x20;
6. The "Chain" column tells you which block chain you minted a SKU's NFTs on&#x20;
7. The "Contract Address" column displays a link of the chain address for the NFTs associated with a SKU. If you click the link you'll be redirected to a chain scanner displaying all the activity on that contract address.&#x20;

### Looker Studios Analytics Boards&#x20;

In your dashboard homescreen you'll see an icon that looks like this in each row.

&#x20;<img src="https://2471615621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiXxdLAbs3St8VWpChjnt%2Fuploads%2FXv7n7gMBbW60NuJRqLQ5%2FScreenshot%202024-03-19%20at%206.20.09%E2%80%AFPM.png?alt=media&amp;token=dc95a680-b508-4f67-b6ce-e4f08d4c20f5" alt="" data-size="original">

This icon tells you if a Looker Studio Analytics Board is connected to a SKU. If the icon is a pale grey as in the image above there is no Looker Studio Analytics Board connected. If the icon is a dark grey like below there is a Looker Studio Analytics Board connected.

&#x20;![](https://2471615621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiXxdLAbs3St8VWpChjnt%2Fuploads%2FAtmSfE9WNLUe0TuU0aVa%2FScreenshot%202024-03-19%20at%206.23.30%E2%80%AFPM.png?alt=media\&token=8c0eab3f-a542-432c-bff4-560fa9456bf1)

To view the Looker Studio Analytics Board simply click on the icon in the row and you'll be redirected to the board.

\*if your SKU does not have a Looker Studio Analytics Board connected and you would like to create one please contact the Legitimate team.&#x20;


---

# 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.legitimate.tech/tag-management-platform/dashboard/legitimate-dashboard-home-screen.md?ask=<question>&goal=<user_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.
