> ## 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. # Insights > What Glood noticed about your stores, the evidence behind it, and which checks run on each store Insights is Glood telling you something changed, without being asked. Every store is checked every hour, in its own time zone, and anything worth a look lands in the feed with the figures behind it. Open **Insights** in the left rail. ## The feed The feed lists insights newest first, each with its severity (**Critical**, **Warning** or **Info**), its store and when it was last seen. The line at the top says when the stores were last checked. The **Status** filter switches between: | Status | What it means | | - | - | | **Open** | Still true at the last check. This is the default view | | **Snoozed** | Hidden by someone until a date they picked | | **Resolved** | The condition went away on its own | | **Archived** | Someone dismissed it, with a reason | | **No longer tracked** | Glood stopped checking it: the check was switched off, the store lost the data it needs, or the store was disconnected. This is not the same as resolved | Insights are marked read per person. Open one and use **Mark read** or **Mark unread**, or **Mark all read** at the top of the feed. What you mark does not change what a colleague sees. ### When the feed is empty The empty feed tells you which of three things is true: * **The first check has not run yet.** Come back in an hour. * **Nothing was checked.** Every check is switched off for the store, or the store does not have enough history for its checks to judge yet. **Open check settings** from here. * **Nothing needs you right now.** The checks ran and found nothing worth raising. ## Reading an insight Select an insight to open it. It starts with one sentence saying what happened, for example *"Sessions fell to 120 in a weekday hour that usually sees 410 (normal range 300 to 520)"*. **How we know** holds the figures: | Figure | What it is | | - | - | | **Now** | The value in the hour or day that broke | | **Baseline** | What that hour or day usually sees | | **Change** | How far it moved from the baseline | | **Normal range** | The range the value usually falls in. Outside it is what raised the insight | | **Sample size** | How much data the figure stands on | | **Estimated impact** | What it is likely costing, when it can be estimated | **Details** adds the store, what it affects, the category, when it was first and last seen, how many times it has been seen, and how long it stays tracked. Some insights carry a button that opens the report behind them. ### Normal ranges A normal range comes from your store's own last 28 days, kept apart for weekdays and weekends. A measure with enough traffic in most hours of the day is judged hour by hour, in those hours; one without is judged over the whole day. A store needs at least 14 days of history before a check can judge it. So a quiet Sunday night is compared with other quiet Sunday nights, not with a Friday afternoon. ## Snooze or archive an insight Both change what everyone in the organization sees, so they need the `insight:manage` permission (Owner and Admin have it). * **Snooze** hides the insight until a date you pick. The latest date you can pick is when the insight stops being tracked. * **Archive** dismisses it. You are asked why, and the reason is kept on the insight under **Dismissed because**, so the next person who wonders can read your answer. Archived insights stay under the **Archived** filter. ## Choose which checks run on each store Check settings switch each check on or off for one store at a time. They need `insight:manage`. **1. Open check settings** When the feed says **Nothing was checked**, choose **Open check settings**. You can also open them at any time by adding `?checks=1` to the Insights address. **2. Pick the store** **Store** lists your connected stores. **3. Switch checks on or off** Each row shows the check, its category, any data it needs, and how long an insight it raises stays after it was last seen. **4. Save** Use the save bar at the bottom of the screen. A check whose data the store does not have is skipped rather than failed. The row names what it needs. ### What the checks look for | Check | Raises an insight when | | - | - | | Traffic drop | Sessions fall below their normal range | | Bot traffic spike | Bot events rise above their normal range | | Conversion rate drop | Conversion falls below its normal range | | Add to cart rate drop | Add to cart rate falls below its normal range | | Checkout rate drop | The share of carts reaching checkout falls | | Checkout errors spike | Checkout errors rise | | Payment errors spike | Payment errors rise | | Orders drop | Orders fall below their normal range | | Orders spike | Orders rise above their normal range | | Discount usage spike | The share of orders using a discount rises | | Zero result searches rise | More searches find nothing | | Page speed regression | Largest paint at the 75th percentile on Glood's storefront visits gets slower | | Page errors spike | Console errors and exceptions on Glood's storefront visits rise, or an error breaks the pages a visit opened | | Fulfilment delay | The average time to fulfil an order rises | | Returns spike | Returns rise | | Refunds spike | The refunded amount rises | | Store unreachable | The home page times out, loads blank or answers with an error on a storefront visit | | Password page on | The storefront asks for a password, so shoppers cannot see it | | Add to cart broken | A storefront visit could not add a product to the cart | | Checkout unreachable | A product went into the cart but checkout would not open | | Search shows no products | A search on the storefront showed nothing | | Best seller unavailable | One of your top 10 sellers of the last 30 days cannot be bought | | Certificate expiring | The storefront's TLS certificate is close to expiry, or has expired | | Crawler access expiring | The crawler access signature for Glood's storefront visits is close to expiry | The checks that look at the storefront itself (page speed, page errors, unreachable, password page, add to cart, checkout, search and certificate) need the storefront probe, which is off until you switch it on. See [Monitoring](https://docs.glood.ai/platform/dashboard/stores.md#monitoring). ## Insights and agents When a store runs a **Store monitor** agent, an insight wakes it, and the agent finds the change behind it. You then get one alert, for the agent's finding with its cause, rather than one for the insight and another for the explanation. If the agent has not explained it within about an hour, the insight alerts on its own. See [Alerts](https://docs.glood.ai/platform/dashboard/alerts.md) and [Schedules and triggers](https://docs.glood.ai/platform/agents/schedules.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.