What the TrustLens Command Center Dashboard Is Actually Telling You

The TrustLens Command Center dashboard is not designed to be checked constantly. It is designed so that when something genuinely needs your attention, it is obvious at a glance — and everything else can wait until next week. If you understand what each section is actually measuring, you can move through the dashboard in under five minutes and leave knowing whether any action is needed.

This guide walks through every section of the Command Center as it exists in TrustLens version 1.2.3, verified directly against the dashboard template and analytics code. It explains what each number represents, how it is calculated, and — most importantly — when it warrants a response and when it does not.

The Monday Morning Habit

The most effective pattern for using the TrustLens Command Center is a short weekly review — not a daily one. The dashboard aggregates over a 30-day window for most charts, and the KPI cards surface the key risk signals at a store-wide level. Daily checking adds noise without adding signal; a 5-minute Monday review catches genuine trend shifts without turning fraud monitoring into a distraction.

Here is a practical 5-minute sequence:

1. Glance at the header bar health ring and the health message — is the store state still “Your store is in great shape” or has it shifted to a warning?
2. Check the New High-Risk (7d) KPI card — has the count of customers entering Risk or Critical in the past 7 days jumped?
3. Look at the Trust Score Trends chart — is the 30-day average trending down consistently, or flat?
4. Check the Chargeback Ratio speedometer — is the status still “Healthy”?
5. Scan the Customers Requiring Attention list — any new names you recognise?

If all five are clear, close the tab. If any of them are not clear, the sections below explain what to look at next.

The Header Bar — Your Store Health at a Glance

The TrustLens Command Center header bar is the first thing you see when you navigate to TrustLens in your WordPress admin. It consists of a health ring on the left and a summary panel on the right.

The health ring

The health ring displays the average trust score across all customers TrustLens has profiled, rounded to the nearest integer. The ring’s color adapts to the segment that score corresponds to: a score of 74 renders in the Trusted-segment color; a score of 22 renders in the Risk color. This color coding is directly tied to TrustLens’s six-segment system — it is not a separate health metric.

The number itself is the mean of all customer trust scores. A store whose customers are predominantly long-standing, clean buyers will see something in the 70s or higher. A store that has recently run several promotions drawing new customers — or one that has been experiencing return abuse — will see the average drift downward as lower-scored customers accumulate.

The health message

Below the greeting, TrustLens shows one of three health messages, derived from the combination of average score and the count of customers in Risk or Critical segments:

• “Your store is in great shape” — zero Risk or Critical customers, or average score above 40 with no concerning count. No action needed.
• “Some customers need attention” — at least one Risk or Critical customer is present but the average score is 40 or above.
• “Multiple risks detected — review flagged customers” — at least one Risk or Critical customer exists and the average score has fallen below 40. This is the state that warrants an immediate look at the Customers Requiring Attention list.

The header also shows a real-time summary: events in the last 24 hours and the count of distinct customers who generated those events. This is a pulse check — a store that normally sees 200 events per day spiking to 800 on a Monday morning is worth investigating for unusual activity, whether that is a card-testing attack, a flash-sale surge, or an unusual refund batch.

The Six KPI Cards — What Each One Means

Directly below the header bar, TrustLens displays six KPI cards. These are the most frequently misread section of the dashboard, because some of them look like actionable metrics when they are actually contextual ones. Here is what each card actually measures.

The Module Status Pills

Sitting between the KPI cards and the primary charts is a row of module status pills. These are a compact at-a-glance status for features that do not have their own dashboard surface: Card-Testing Defense, Automation (Pro), Webhooks (Pro), Payment Controls (Pro), Shipping Anomalies, and Scheduled Reports (Pro).

Each pill shows an on/off state and a single micro-stat. For Card-Testing Defense, the pill surfaces the current defense state (Idle / Targeted / Panic) and the 24-hour decline count. If Card-Testing Defense is in “Targeted” state — meaning at least one device fingerprint has been locked out of checkout — the pill will show how many devices are currently targeted. If it has escalated to “Panic” (all checkouts frozen), the pill turns red and shows “All checkouts frozen.”

Clicking any pill navigates directly to the relevant settings or admin page. The pills are not for deep analysis; they are a status board. If everything is green and idle, move on. If Card-Testing Defense is showing “Targeted” or your Shipping Anomalies module is off when you thought it was on, the pill flags that without requiring you to open the settings page to check.

Trust Score Trends — Reading the 30-Day Line

The Trust Score Trends chart is a 30-day line chart showing the daily average trust score across all customers who had a score update on that day. Each data point represents the mean score from score_update events in the TrustLens signals table — which means it reflects only days where scores actually changed, not a rolling average of all customer scores.

What the chart is actually measuring

On any given day, a subset of your customers will have scores updated — because they placed an order, received a refund, triggered a coupon event, or had a background recalculation run. The daily average on the chart reflects the mean score of those customers on that day. This means the chart responds to activity, not the full customer base.

A day with no score updates will simply have no data point. The chart will show a gap rather than a flat line. This is normal.

How to read trends

You are looking for two patterns:

• Consistent downward slope: If the 30-day line shows a clear downward trend across multiple weeks — not a single dip but a sustained drift — it suggests that the customers triggering score updates lately are scoring lower than average. This could indicate new high-risk customers arriving, existing customers accumulating negative signals, or a promotional period that brought in customers with riskier profiles. Any of these are worth investigating by checking the segment distribution and the Customers Requiring Attention list.
• Sharp single-day drop: A dramatic single-day drop often means a batch of high-risk events happened at once — a large refund run, a coupon-abuse cluster being detected after the historical sync, or a card-testing event. The Activity by Hour chart and the Detection Overview section will help you identify the cause.

A stable line in the 65–80 range on a store with a mix of new and established customers is a healthy signal. You do not need to act on it.

Customer Segments — Where the Distribution Matters

Alongside the Trust Score Trends chart, the dashboard shows a segment distribution chart: a visual breakdown of how many customers are in each of the six TrustLens segments (VIP, Trusted, Normal, Caution, Risk, Critical).

The segment counts are pulled directly from the TrustLens customer table. The total shown in the chart header is the sum across all six segments. The chart uses Chart.js with the segment colors TrustLens assigns to each tier.

What a healthy distribution looks like

For a store with a settled customer base and an active return policy, a typical healthy distribution might look something like:

• VIP and Trusted: 30–50% of total customers
• Normal: 35–50% (includes new customers not yet classified)
• Caution: 5–10%
• Risk and Critical combined: under 5%

These numbers will vary significantly by store type, return policy generosity, and how long the store has been running. A new store with mostly new customers will have a high Normal percentage and small VIP/Trusted segments — that is expected. What you are watching for is the Critical segment growing as a proportion of total customers over time.

What to do when Critical is growing

If the Critical segment count increases week over week, navigate to the customer list filtered to Critical and work through the profiles. Sort by trust score ascending so the lowest scores — the most severe signals — come first. For each one, open the profile and read the event timeline. The segment distribution chart tells you there is a pattern worth examining; the customer profiles tell you what it actually is. For a full decision framework on what to do with each segment, the TrustLens segments operational guide walks through each tier in detail.

Revenue Protection Overview

The Revenue Protection Overview is a scorecard showing four figures calculated over the last 30 days: Money Protected, Money at Risk, Protection Rate, and Actions Taken. Below the four headline figures, a detail row breaks down Orders Held, Checkouts Blocked, and (for Pro users) Chargeback Prevention estimates.

This section is worth understanding carefully, because the numbers are modeled estimates — not direct accounting figures.

Money Protected

Money Protected is the sum of three components:

• Orders Held: The value of orders that were held via automation rules and were not subsequently refunded or cancelled. This reflects value that was at risk and was safely processed after review.
• Blocked Checkouts: An estimate based on the number of checkout-blocked events multiplied by the average order value of blocked customers (or high-risk customers if no blocked customers have completed orders). This is necessarily an estimate — TrustLens cannot know the exact value of the cart that was blocked, only the customer’s historical average. A 60% fraud-rate factor is applied.
• Chargeback Prevention (Pro only): An estimate based on the count of customers who had disputes filed and were already in Risk or Critical at that time, multiplied by the average dispute value plus the estimated chargeback fee (~$25). Visible in the free version only when TrustLens’s chargeback tracking is enabled (Stripe or WooPayments users).

Money at Risk

Money at Risk is the estimated value of orders placed by Caution, Risk, and Critical customers who were not blocked. TrustLens applies risk-factor weights: Caution at 10%, Risk at 30%, Critical at 60%. This is an acknowledgment that not every order from a Caution customer represents a loss — most do not — but that exposure exists and is worth quantifying.

Chargeback Ratio Speedometer

The Chargeback Ratio section appears on the dashboard when TrustLens’s chargeback tracking is active — which requires using Stripe or WooPayments as your payment gateway. If you process payments through a different gateway, this section will not appear unless you have manually entered chargeback data via the order edit screen.

The speedometer shows your blended calendar-month chargeback ratio: the number of disputes for the current calendar month divided by the number of card orders in the same month, expressed as a percentage. It also shows the raw numerator and denominator (“4 disputes / 1,240 card orders”) so you can verify the math.

The three status states

TrustLens shows one of three statuses, derived from how close your blended ratio is to the nearest card-network monitoring threshold (Visa VDMP/VFMP, Mastercard ECP, Amex, Discover):

• Healthy: Your ratio is well clear of the nearest threshold. No action needed.
• Approaching threshold: TrustLens has calculated you are 3 or fewer additional disputes away from crossing a threshold. This is a warning — review any customers with recent dispute history and consider whether any pending high-risk orders should be held for manual review.
• Action needed: You have crossed or are at a network monitoring threshold. This warrants immediate attention: review your dispute history, check for patterns in the customers behind recent chargebacks, and contact your payment processor if needed.

Free users see the blended ratio and the status. Pro users also get a “View details” link to the dedicated Chargeback Monitor page, which shows per-brand ratios, a 12-month trend chart, a trailing-30-day window, and daily email alerts before you cross a threshold. If you are a Stripe or WooPayments user and chargebacks are a real concern for your store, the distinction between Visa VDMP and Mastercard ECP thresholds matters — Pro surfaces those separately so you know which brand is driving your ratio. For a detailed breakdown of all five card-network thresholds, the exact percentage cutoffs, and what to do at each speedometer state, see the TrustLens Chargeback Speedometer guide.

Refund Activity and Activity by Hour

The Refund Activity chart shows daily refund event counts over the last 30 days, broken down by full refunds and partial refunds. The Activity by Hour chart shows event volume distributed across 24 hours of the day, averaged over the last 7 days.

Reading Refund Activity

The Refund Activity chart is useful for two things. First, distinguishing seasonal variation from trend changes — a refund spike that coincides with a promotional period is expected; one that appears two or three weeks after the promotion ended might reflect customers who bought during the sale and are now returning at higher rates. Second, monitoring the full-refund versus partial-refund ratio. A store whose refund profile is shifting toward more full refunds — without a product quality change — may be developing a wardrobing pattern that warrants closer attention to the Return Rates table.

Reading Activity by Hour

The Activity by Hour chart is most useful when something unusual has happened and you want to understand when it occurred. A card-testing attack, a refund cluster, or an unusual coupon redemption pattern will usually show up as a spike at a specific hour. If the Events (24h) KPI card is much higher than usual, open the Activity by Hour chart to see when the volume happened. An 11 PM spike is a different concern from a 9 AM one.

On a normal week where nothing unusual has happened, both charts can be read in under 30 seconds. You are looking for “is this roughly what last week looked like?” rather than performing analysis.

Highest Return Rates Table

The Highest Return Rates table shows the top 5 customers by return rate (with refund value as the tiebreaker), including their email, segment badge, return rate percentage, total refund value, and a View link to their profile.

The table assigns color coding to return rates: 15–29% is “elevated” (amber), 30–49% is “high” (deeper amber), 50%+ is “critical” (red). The top two rows are highlighted as priority attention items.

How to use this table

This table is not for acting on every week. It is for checking whether the names in it have changed, and whether anyone new has appeared with a very high return rate you would not have otherwise caught. A customer who has been in this table for months at 28% return rate is a known situation — your decision about them has already been made. A new name appearing at 65% is worth opening immediately.

For stores running regular promotions, this table is particularly worth checking after a high-volume sale period. Promotional events attract customers with high return rates — often specifically because your return policy makes the purchase feel risk-free. The table will surface that pattern within days of a sale ending if it is happening. The connection between return-rate increases after promotions and how to read that data is covered in more depth in the guide to measuring whether a WooCommerce discount campaign actually worked.

Detection Overview — Coupon and Chargeback Stats

The Detection Overview card shows aggregate statistics from two detection modules: Coupon Abuse Detection and (if chargebacks are enabled) Chargeback Tracking.

Coupon abuse stats

Four figures are shown:

• Coupons Used: The total count of coupon applications recorded across all profiled customers.
• First-Order: How many of those coupon applications were on a customer’s first order — the signal TrustLens uses to detect welcome-discount farming.
• Coupon + Refund: The number of coupon applications followed by a refund on the same order — the coupon-then-refund abuse pattern.
• Multi-Account: Customers flagged for using coupons across multiple linked accounts.

For most stores, the First-Order number is the most useful one to watch. If the ratio of First-Order coupons to total coupons used is unusually high — say, 30% or more — it suggests that a meaningful fraction of your coupon redemptions are coming from new accounts, which may include welcome-discount farming. The coupon-abuse posts in the TrustLens cluster cover how to recognise coupon abuse patterns before they compound.

Chargeback tracking stats (Pro / Stripe / WooPayments)

If chargeback tracking is enabled, four figures appear: Total Disputes, Won, Lost, and the number of Customers with disputes. These are raw counts, not ratios. The ratio is on the speedometer card above. The Detection Overview counts are useful for understanding scale — “we have had 12 disputes this month, won 7, lost 5, and 4 distinct customers are involved” is actionable context when you are reviewing the Customers Requiring Attention list and want to understand which disputes came from the same customer cluster.

Customers Requiring Attention

The Customers Requiring Attention section at the bottom of the dashboard shows up to 10 customers in the Risk or Critical segments, with their segment badge, trust score, return rate, total refund value, and a View link. The attention count in the section header reflects the combined Risk and Critical customer total across your entire customer base — not just the 10 shown here.

This is the section that usually determines whether your Monday review ends in 3 minutes or 30. If the list is empty (“No high-risk customers detected — your store is looking good”), close the tab. If there are names here you do not recognise from last week, click through to their profiles.

What to do with each name

The table shows the customer’s segment badge and score. A Risk customer with a score of 22 and a return rate of 18% warrants a different response from a Critical customer with a score of 4 and a return rate of 67%. Open the profile, read the signal breakdown and event timeline, and make a decision. The guide to reading a TrustLens customer profile walks through exactly this process — what the signal breakdown shows, how to read the event timeline, and what action fits each risk level.

If the list has grown substantially since last week — a dozen new names where there were two before — do not try to process them all in one session. Filter the customer list to Critical and work through those first. Then come back to Risk when you have time.

Pairing the Dashboard with Campaign Analytics

The TrustLens Command Center measures customer behavior over time. WooCommerce campaign analytics measure what happened during a specific promotional window. When you run a discount campaign, the two data sources tell you different things about the same period — and combining them gives you a fuller picture than either provides alone.

After a sale period, the questions worth asking across both systems are:

• Did the Trust Score Trends chart dip during the sale window? A dip during a sale that corrects afterward might simply reflect a surge in new customers who haven’t accumulated positive signals yet. A dip that persists or deepens after the sale ends may indicate you attracted customers who are driving refund and return rates up.
• Did the Highest Return Rates table get new entries in the week after the sale? Post-sale return spikes are a predictable pattern for stores with generous return policies. TrustLens will surface the individual customers behind the aggregate return-rate increase that WooCommerce Analytics shows but cannot attribute.
• Did the Coupon + Refund count increase during the promotional period? A spike here means customers applied your promotional coupon and then refunded the order — extracting the coupon benefit without keeping the product. That is margin loss that WooCommerce’s coupon redemption count won’t capture.
• Did any customers enter the Critical segment who first appeared during the sale period? If new customers from a promotional window are scoring Critical within their first few orders, the sale attracted a pattern — not just a customer.

The guide to measuring WooCommerce discount campaign performance covers the campaign analytics side of this in depth — what WooCommerce can and cannot tell you about whether a promotion actually made money, and how to think about incremental value versus discount cost. The TrustLens dashboard adds the behavioral layer on top: not just “did the campaign generate revenue?” but “what kind of customers did it attract, and are they still costing you money three weeks later?”

Common Questions

How often should I check the TrustLens Command Center dashboard?

Once a week is the right cadence for most stores. The dashboard aggregates over 30-day windows for most charts — daily checking adds noise without adding decision value. A 5-minute Monday review covering the header health state, the New High-Risk count, the Trust Score Trends chart, the chargeback ratio, and the Customers Requiring Attention list is sufficient to catch any genuine changes. If you are running a promotional campaign that week, a mid-week check of the Refund Activity chart and Highest Return Rates table can be useful, since return patterns from promotional customers often emerge within 3–5 days of the sale ending.

The average trust score has been declining for three weeks. What should I look at first?

Start with the segment distribution chart. Is the Critical or Risk count growing as a proportion of total customers, or is the Normal count growing (which would suggest new customers arriving who don’t yet have enough order history for favorable scoring)? If Risk and Critical are growing, open the Customers Requiring Attention list and work through the profiles of customers who entered those segments in the past two weeks — their event timelines will tell you what behavioral change drove the decline. If Normal is growing with no corresponding increase in Risk and Critical, the declining average is likely a new-customer dilution effect: new shoppers start at 50 and haven’t yet accumulated enough orders to earn positive signals. That is a positive situation, not a concerning one.

The Chargeback Ratio says “Approaching threshold.” What do I do?

Check the Detection Overview to see how many disputes have been recorded this month and how many customers are behind them. If it is a small number of customers responsible for multiple disputes, open their profiles — you may find they are already in Risk or Critical, and blocking them proactively may prevent the additional disputes that would push you across the threshold. If you are a Pro user, the dedicated Chargeback Monitor page shows which card brand is closest to its threshold (Visa VDMP/VFMP, Mastercard ECP, Amex, or Discover) and the exact proximity — which helps you decide whether this is a structural issue or a one-month spike. The TrustLens Dispute Evidence Report is also worth generating for any customers with multiple disputes — it produces a print-ready behavioral summary you can submit alongside a processor dispute response.

The Customers Requiring Attention list shows names I don’t recognise. Should I immediately block them?

No. The list shows customers in Risk or Critical — but a segment is a threshold, not a verdict. Before blocking anyone, click through to their profile and read the signal breakdown and event timeline. Confirm the pattern is genuine: multiple signals from different modules, accumulated over time, not an artifact of a single unusual order or a data import issue. The customer profile reading guide explains what to look for in the signal breakdown and when a Risk or Critical score warrants blocking versus monitoring. For the TrustLens free version in particular, blocking is always a manual choice — nothing happens automatically.

What does it mean when “New High-Risk (7d)” is zero but I have many customers in the Risk segment?

It means all the customers currently in Risk had their profiles created more than 7 days ago. The “New High-Risk” KPI counts profiles created in the past 7 days that are already Risk or Critical — it does not count existing customers who moved into those segments this week. If you want to track segment-change events (a customer who was Trusted last week and is now Caution), the Trust Score Trends chart is the right place to look for store-wide movement, and the Customers Requiring Attention list will surface individual customers whose scores have recently dropped into risk territory.

How does TrustLens score the customers who appear on the dashboard?

Each customer starts at a base score of 50 and is adjusted by eight detection modules: returns, order patterns, coupon abuse, category-aware risk, linked accounts, shipping address anomalies, chargebacks, and card-testing defense. The complete guide to TrustLens customer scoring walks through exactly what each module measures, what penalties and bonuses it applies, and why two customers with similar order counts can end up 30 points apart.