Dashboard Overview
8 min read
The TrustLens Dashboard — also called the Command Center — is the single screen that answers “what’s happening with risk in my store right now?” It surfaces trust score health, segment distribution, refund and chargeback activity, module status, the customers who need your attention, and (in Pro) the revenue you’ve already protected. This guide walks through every section of the page and explains what each number means.
Access: TrustLens → Dashboard, or click the TrustLens menu item.
The Admin Header #
Every TrustLens page — Dashboard, Customers, Notifications, Automation, Card-Testing Defense, Chargeback Monitor, Settings — sits under a persistent plugin-wide admin header. It’s the same UI on every page so navigation is consistent.
| Element | What It Does |
|---|---|
| TrustLens logo + page title | Click logo to return to Dashboard from anywhere |
| Status pill | Live indicator of overall store health — green / amber / red based on average score, ratio status, and active card-testing alerts |
| Notifications bell | Unread alert count; click to open the notifications dropdown with recent events |
| ⌘K command palette | Keyboard shortcut Cmd+K (Mac) or Ctrl+K (Windows) opens a fuzzy-search palette for jumping to any customer, settings tab, or admin page |
| Tab navigation | Quick links to Customers, Notifications, Automation, Card-Testing Defense, Chargeback Monitor, and Settings (the Chargeback Monitor tab appears once disputes exist; Automation and Chargeback Monitor carry a PRO badge on the free plan) |
Quick Start Card #
On a new install the Dashboard opens with a Quick Start card — “A few quick choices to get TrustLens working for your store.” It puts the three decisions that matter most right at the top so you don’t have to hunt through Settings:
| Choice | What it does |
|---|---|
| Block risky customers at checkout | Turns on checkout blocking. Nothing is ever auto-blocked — this just lets you block specific customers; you stay in control. |
| Email me about attacks & high-risk customers | Turns on notifications so you get a heads-up when a card-testing attack hits or a high-risk order comes in. |
| Import your past orders | Links straight to the Historical Sync import. Once customers are being scored, this row instead confirms “Your customers are being scored.” |
Each toggle saves instantly with a confirmation toast. When you’re set up, click Hide to dismiss the card — it won’t come back. You can change any of these choices later in Settings.
Historical Sync Banner #
Until Historical Sync has run, a banner sits at the top of the Dashboard with a Run Historical Sync button. While sync is in progress, the banner shows a progress bar with batch count and ETA. Once sync completes, the banner is dismissed automatically and won’t reappear unless you wipe plugin data.
You can rerun sync at any time from Settings → Data — it deduplicates by order ID and only processes new or updated records.
Trust Score Health Card #
The first card shows your store’s overall trust health at a glance.
- Average Trust Score — the mean trust score across all scored customers (those above the minimum-orders threshold)
- Segment label — the segment your average score falls into (e.g. “Trusted” if your store-wide average is 75)
- 30-day trend sparkline — micro-chart showing whether average trust is rising, falling, or stable
- Total scored customers — the count of customers with enough order history to be in a real segment
A drop in the trend line is usually the first signal that something is changing — a new abuse pattern, a coupon being shared, or an unusual refund spike. Investigate by looking at the high-risk customer list below.
Segment Distribution Row #
Six tiles, one per segment, showing customer counts and percentages:
| Segment | Color | Score Range | What the Count Tells You |
|---|---|---|---|
| VIP | Green | 90–100 | Loyal high-value customers — protect from friction |
| Trusted | Blue | 70–89 | Reliable repeat buyers |
| Normal | Gray | 50–69 | Average customers and those below the min-orders threshold |
| Caution | Yellow | 30–49 | Early warnings — watch this number rise |
| Risk | Orange | 10–29 | Likely abuse patterns — review individually |
| Critical | Red | 0–9 | Confirmed multi-module abuse — typically warrants action |
Click any segment tile to filter the Customers page to that segment.
Healthy distribution: ~80% in Normal/Trusted/VIP, ~15% Caution, ~5% Risk/Critical. Significant deviation usually means thresholds need tuning or a new attack vector has appeared.
Detection Modules Panel #
A status panel listing all eight detection modules, each showing:
- Module name (Returns, Coupons, Linked Accounts, etc.)
- Whether it’s active or off
- One headline stat (e.g. “12 customers flagged this week” for Returns; “3 fraud rings detected” for Linked Accounts)
This is the fastest way to verify every detector is alive and producing signals. The panel is read-only — to actually turn a module on or off, go to TrustLens → Settings → Modules (Card-Testing Defense has its own dedicated page).
Chargeback Ratio Speedometer #
One of the most important cards on the page. The speedometer shows your blended monthly chargeback ratio — total disputes / total orders for the current calendar month, across all card brands.
| Color | Meaning | Default Threshold |
|---|---|---|
| Green | Healthy | < 50% of the lowest brand monitoring threshold |
| Yellow | Approaching threshold | 50–100% of warn threshold |
| Red | Action needed | At or above warn threshold |
Card networks (Visa VDMP/VFMP, Mastercard ECP, Amex, Discover) place merchants into monitoring programs when their dispute ratio exceeds program-specific thresholds. Crossing those thresholds triggers fees, processor scrutiny, and potential account termination.
The Free speedometer shows the blended ratio against the lowest brand threshold. Pro adds the dedicated Chargeback Monitor page with per-brand breakdowns, 12-month trend chart, and trailing-30-day window. See Chargeback Ratio Speedometer.
Customers Requiring Attention #
Shown in the Command Center as Priority Targets · action required, this is a live list of the highest-risk customers in your store right now. Sorted by trust score ascending, so the worst score is at the top.
For each customer the list shows:
- Segment badge (Critical / Risk / Caution)
- Email (or hash-derived identifier if the email isn’t available)
- Trust score with delta vs 30 days ago
- Top signals — a short summary line like “67% return rate · $2,340 refunded · 3 linked accounts”
- Quick actions — View profile, Block, Allowlist, Recalculate
Click View to open the Customer Detail page, which shows the full event timeline and every individual signal contribution.
Top Returners #
A separate panel showing your top five customers by absolute refund value over the last 30 days. This catches a different pattern than trust score: a customer with a 30% return rate on $20,000 of orders is more financially damaging than a customer with a 90% return rate on $200. The list surfaces both.
Category Abuse Stats #
For stores using the Category-Aware Risk module, this card lists product categories with elevated cross-customer return rates. If Outerwear shows a 38% category-wide return rate, that’s a structural issue with the category itself (sizing, fit, photography) — not just individual customer abuse. Investigate the category before reading each customer as risky.
Recent Coupon Abuse Activity #
If the Coupons module is enabled, this card lists:
- Top coupons by abuse signal volume
- Customers who’ve used multiple first-order coupons
- Coupon-then-refund pattern detections in the last 30 days
If a single coupon code is being shared on a deal forum, this is where you’ll see it first.
Refund Activity Chart #
A 30-day chart showing refund count and refund value per day. Spikes here usually correlate with either a product issue (a defective batch causing legitimate returns) or coordinated abuse (a coupon being exploited then refunded). Cross-reference with the Top Returners and Category Abuse cards to tell them apart.
Hourly Activity Heatmap #
A 7-day × 24-hour heatmap of order activity. Card-testing attacks often show up here as bursts at unusual hours (3 AM local time, weekends). Spotting a strange burst here is a prompt to check the Card Testing tab for velocity events.
Monthly ROI Summary (Pro) #
For Pro users, a six-month chart of money protected — the cumulative value of orders blocked, customers prevented from completing checkout, and disputes avoided based on automation rule actions. The number is conservative: only actions you’ve explicitly configured to take are counted.
Quick Actions #
A row of one-click buttons at the bottom of the Dashboard:
- Run Historical Sync — re-run sync if you’ve added orders from another source
- Export Customers (CSV) — pull the full customer table for offline analysis
- View Automation Logs — Pro; jumps to automation activity
- Panic Freeze — Card-Testing emergency stop; store-wide checkout halt (5–30 min, default 15)
Empty State #
If you’ve just activated the plugin and not yet run Historical Sync, most cards will show empty states with helpful prompts:
- Segment row shows zeros with a “Run Historical Sync to build profiles” link
- Trust health card shows “—” with a note that scoring needs data
- Customers requiring attention shows “No customers yet”
- Charts show flat empty placeholders, not error messages
This is intentional — the Dashboard doesn’t hide its scaffolding before you have data. Once sync completes (or your first new order comes in after activation), the cards populate automatically.
Performance Notes #
The Dashboard is optimized for stores with hundreds of thousands of orders:
- Segment counts and analytics are cached as transients with 15-minute and 1-hour TTLs
- Caches are invalidated automatically when new scoring events fire, so the Dashboard never serves data more than 15 minutes stale
- High-risk customer list uses an indexed query against
trust_scorewith a small LIMIT — sub-100ms on million-row tables - Chargeback ratio computation is done once per page load and reused across cards
If the Dashboard is slow, suspect a different cause first: a sluggish host, a conflicting plugin, or an unindexed custom query elsewhere on the page. See Performance Tuning for diagnostics.
