> For the complete documentation index, see [llms.txt](https://fulbix.gitbook.io/fulbix-fraud-and-ip-blocker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fulbix.gitbook.io/fulbix-fraud-and-ip-blocker/setup/dashboard-overview.md).
# Dashboard Overview
The Dashboard is the first page you see when you open Fulbix. It gives you a quick health check of your store's protection status — how many visitors arrived, how many were blocked, and what still needs to be set up.
***
### The App Embed Banner
At the very top of the Dashboard is a status banner.
**Green banner** — *"App Embed is active. Your storefront is protected by Fulbix Fraud."*\
Your store is being actively protected. You can click **Manage in theme editor** if you ever need to change theme settings.
**Yellow banner** — *"App Embed is not activated. Enable it in your theme editor to start protecting your storefront."*\
Protection is not running. Click **Activate App Embed** immediately and follow the steps in Article 1.
***
### The 4 Metric Cards
Below the banner you will find four cards showing your store's traffic summary for the **last 30 days**.
#### Total Visitors
The total number of unique visitor sessions detected by Fulbix. This includes everyone — allowed, blocked, and redirected.
#### Blocked Requests
The number of sessions that were stopped by a rule or security setting. Includes both block page responses and redirects.
The badge next to this number shows your **block rate** — what percentage of all traffic was blocked.
| Badge color | What it means |
| ----------- | ------------------------------------------------------------------------------ |
| Green | Block rate is low (under 5%) — normal for most stores |
| Yellow | Block rate is moderate (5–20%) — worth investigating |
| Red | Block rate is high (over 20%) — review your rules to check for false positives |
#### Allowed Traffic
The number of sessions that passed all checks and reached your store normally.
#### Block Rate
The percentage of all traffic that was blocked. Shown again as a standalone card for emphasis.
> **If all four cards show "—":** Your App Embed is either not activated or no visitors have arrived yet. Check the banner at the top of the Dashboard.
***
### The Setup Checklist
Below the metric cards is a **Setup Checklist** — a guided list of the 4 steps to get fully protected.
Each step shows:
* What needs to be done
* A short description
* A button to take you directly to the right page
A progress bar at the top shows how many steps you have completed (e.g., "2 / 4 completed").
Click the checkmark next to any step to mark it as done manually. The checklist is there to guide you — it does not enforce anything.
**The 4 steps:**
1. **Activate App Embed** — enables protection on your storefront
2. **Configure Protection Settings** — set up Security preferences
3. **Create Your First Rule** — block IPs, countries, or ranges
4. **View Analytics** — review detected threats and visitor activity
***
### Support & Guidelines
At the bottom of the Dashboard are three support cards:
| Card | What it links to |
| ------------------- | ------------------------------------------------------- |
| **Documentation** | Step-by-step guides for every feature |
| **Video Tutorials** | Walkthroughs for fraud rules, block pages, and security |
| **Contact Support** | Live chat with the Fulbix support team (7 days a week) |
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://fulbix.gitbook.io/fulbix-fraud-and-ip-blocker/setup/dashboard-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.