> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glood.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reports

> The reports in the dashboard, how to scope and compare them, and how to download them

Open **Reports** in the left rail. Reading reports needs `analytics:read`, which
every built-in role has.

## The reports

| Report | What it shows |
| - | - |
| **Overview** | How Glood is performing across your stores |
| **Revenue** | Online-store revenue as Shopify recorded it, including channels the storefront pixel never sees. In-person and manually entered orders are excluded |
| **Conversion** | How often a visit becomes an order, and what Glood changes about that |
| **Average order value** | What an order is worth, and what Glood adds to it |
| **Attribution** | What Glood is responsible for, measured two ways that disagree on purpose |
| **Orders** | Every online-store sale Shopify recorded |
| **Customers** | Who bought in the period, and how many had bought before |
| **Products** | Every product, ranked by what Glood did with it. Select one for its full picture |
| **Collections** | Whether each collection page is doing its merchandising, and which products it moves |
| **Live view** | Every shopper action as it lands, and how busy each app is |
| **Event explorer** | Every event as it arrived, down to one shopper's session |
| **Data health** | Which fields the storefront pixel is actually sending, and what each gap costs a number elsewhere |
| **Store health** | How your storefront behaves for a shopper, from Glood's own visits |

Most reports read the events the Glood apps collect. A store with no Glood app
enabled shows **No Glood app is enabled yet**; enable Glood Search or Glood.AI
Personalization from the store's [Settings](https://docs.glood.ai/platform/dashboard/stores.md#integrations).

## Scope, dates and comparison

The bar at the top of a report sets what it covers:

| Control | What it does |
| - | - |
| **Store** | One store, or **All stores** |
| **Channel** | One sales channel, or **All channels** |
| **Date range** | A preset (Today, Yesterday, Last 7, 30 or 90 days, Last 12 months, Week, Month, Quarter or Year to date) or your own dates. **Include today** adds the current partial day |
| **Comparison** | **No comparison**, **Previous period**, **Previous year**, **Previous year (match day of week)** or **Custom** |
| **Currency** | Follows the store, or the organization for all stores together |

Pixel data arrives with up to 30 seconds of lag and goes back 366 days.

## Download a report

Each report card has a download button that saves it as CSV. It needs
`analytics:export`, which every built-in role has.

## Store health

**Store health** looks at one store at a time and comes entirely from the
[storefront probe](https://docs.glood.ai/platform/dashboard/stores.md#the-storefront-probe). If the
probe is off, the page says so and links to the store's Monitoring settings.

| Section | What it shows |
| - | - |
| **Right now** | Whether the store is online, how many pages loaded, whether add to cart works and checkout opens, and when the next check is |
| **Speed** | Each page's LCP, CLS, TBT and TTFB, rated against Google's Core Web Vitals limits, with theme changes marked on the trend |
| **Page weight** | What each page downloaded: size, JavaScript, CSS, render-blocking files, requests and third-party domains |
| **Availability and security** | Uptime over the dates, each page's result and status, the security certificate and crawler access |
| **Product pages** | What a shopper and a search engine find on a product page: the add to cart button, product details for search engines, and reviews |
| **What's broken** | JavaScript errors, console messages, failed requests and broken images |
| **Page details** | A screenshot of every page on the latest visit, and where the checkout journey stopped |

These numbers describe Glood's own visits, on the devices you chose, not every
shopper.

> [!TIP]
>
> Your AI assistant can run the same reports, and compose breakdowns no report
> covers. See [Using it](https://docs.glood.ai/platform/using.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.