How to Set Up TrustLens for the First Time

Installing a new plugin and actually getting value from it are two different things. The installation takes two minutes. Understanding what you are looking at and doing the right things in the right order — that is what takes a little guidance.

This post is the companion to the TrustLens overview — that one explains what the plugin is and how the scoring engine works. This one picks up the moment after you install it: what you see on first load, what to do with it, and what to leave alone until you have more context.

TrustLens version 1.2.3 at the time of writing. The steps below reflect the current admin interface.

What You See When TrustLens Loads for the First Time

After activating TrustLens, WordPress redirects you directly to the TrustLens dashboard. No wizard, no multi-step onboarding flow — just a clean admin screen that shows you where things stand.

What you see depends on one thing: whether TrustLens has analyzed any customers yet.

On first load, it has not. Your store’s existing customers have no trust profiles — TrustLens only starts building them from the moment of activation. So the dashboard opens in an empty state, which includes three things:

• A health ring showing a dash instead of a score — that is correct, not an error. There is no data yet.
• An onboarding card titled “Get Started with TrustLens” that shows you three steps to follow.
• A chip showing how many of your existing WooCommerce orders are ready to be analyzed — if you have historical order data, this number is usually in the hundreds or thousands.

The onboarding card also tells you how many detection modules are already active. By default, all five free modules are enabled: Return Abuse Detection, Order Tracking, Coupon Abuse Detection, Category-Aware Scoring, and Linked Accounts Detection. You do not need to turn any of them on manually — they are protecting your store from the moment you activate the plugin.

Step 1: Run the Historical Sync

The historical sync is the first meaningful action to take. It processes your existing WooCommerce orders in the background and builds trust profiles for all the customers who placed orders before TrustLens was installed.

Without the sync, TrustLens only knows about activity that happens after installation. With it, your customer profiles reflect however much order history your store has accumulated — which is where the most useful behavioral patterns tend to live.

1. Find the sync button in the onboarding card

   On the empty-state dashboard, scroll down to the onboarding card. Below the three setup steps, you will see a “Start Historical Sync” button. The chip above it shows how many orders will be processed.

2. Click “Start Historical Sync” and keep the tab open

   The sync runs in the background using WordPress’s Action Scheduler — the same system WooCommerce uses for its own background jobs. Progress appears in real time on the dashboard: a progress bar and a counter showing processed vs. total orders. Keep the tab open if you want to watch the progress, but the sync will continue even if you navigate away.

3. Wait for it to complete — then come back

   Duration depends on your order volume. A store with 2,000 historical orders typically finishes in 15–30 minutes. Larger stores with 20,000+ orders may take a couple of hours. You can pause and resume the sync from the same button area. There is no performance impact on your frontend while it runs.

What the sync actually builds: for each customer, it backfills their refund metrics, coupon behavior, category return rates, linked-account fingerprints, and a full event timeline using the original timestamps from your historical order data. When it finishes, customer profiles look like the customer has been tracked since their first order, not since you installed TrustLens.

Step 2: The Settings Worth Looking at on Day One

TrustLens has a Settings page accessible from the left admin menu (TrustLens → Settings). There are several tabs. Most of them can wait. Three settings are worth reviewing in your first session.

Minimum orders for scoring

Found under Settings → General. The default is 3 orders. Customers with fewer orders than this threshold stay in the Normal segment — TrustLens collects their signals but does not move them out of Normal until there is enough data for reliable classification.

For most stores, 3 is a reasonable default. If you run a store where a single high-value order tells you a lot — jewelry, bespoke goods, B2B orders — you might lower this to 1 or 2. If your customers typically place many small orders before a pattern becomes clear, you might raise it to 5. Either way, this is the first number to check against your store’s reality.

Return rate thresholds

Also under Settings → General. There are two: High Risk threshold (default 40%) and Critical Risk threshold (default 60%). A customer whose return rate crosses the High Risk threshold gets flagged; crossing the Critical threshold applies a larger penalty.

These defaults work well for general merchandise stores. If you sell clothing or electronics — categories with structurally higher legitimate return rates — you may want to raise both thresholds slightly. If you sell digital goods with very low expected return rates, you might lower them. Wait until after the sync before touching these: the category return rate breakdown on the dashboard will show you what your actual return picture looks like across your catalog.

Checkout blocking — leave it off for now

Settings → General → Enable Blocking. This is off by default, and that is the right default. Checkout enforcement should not go live until you have looked at the data the sync surfaces and are confident in what you are seeing. Turn it on only when you are ready to act on the scores — when you understand your segment distribution, have reviewed a few Risk and Critical profiles, and have confirmed the signals look genuine.

When you do enable blocking, the block message field below it lets you customize what blocked customers see. The default (“We are unable to process your order at this time. Please contact support for assistance.”) is deliberately neutral — it does not explain the reason, which is intentional. You do not want to reveal your detection logic to the people you are trying to block.

Modules tab — mostly fine as-is

Settings → Modules shows the five detection modules with checkboxes. All five are on by default. The one setting worth noting here is Max first-order coupons under the Coupon Abuse Detection section. The default is 2: a customer can use first-order coupons up to twice before the coupon module flags them. If you have a strict “one per customer” first-order policy, you might change this to 1. If you are more permissive, leave it at 2.

Step 3: Reading Your Dashboard After the Sync

Once the historical sync completes, the dashboard transforms. The onboarding card is replaced by the full command center — nine data sections giving you a store-wide view of your customer risk picture. Here is what each part is telling you.

The health ring and header bar

The health ring in the top-left shows your store’s average trust score as a gauge — a single number representing the trust profile of your customer base as a whole. A score in the 60s–70s is typical for a store with a few years of order history and some return activity. Scores in the 80s suggest a very clean customer base. Scores in the 50s or below suggest a store with meaningful abuse patterns that are worth investigating.

Below the ring, the header bar shows KPI chips: total customers profiled, average trust score, new high-risk customers, recent events, total orders analyzed, and your store return rate. These give you a quick read on the scale of the data before you look at the charts.

Segment distribution

This is the most immediately useful section after the sync. It shows the percentage of your customers in each of the six segments: VIP, Trusted, Normal, Caution, Risk, and Critical.

What you are looking for:

• If Critical is above 5–10% of your customer base, that is a signal worth investigating — particularly if those customers have order histories, not just one order
• If VIP and Trusted together make up the majority of your customer base, you have a fundamentally clean customer picture
• If Caution is unusually large, it often means a group of customers who have elevated return rates without crossing into Risk — worth monitoring but not urgent

Trust score trends

A 30-day line chart of average trust score movement. Right after the sync, this chart fills in using your historical data — so you can see whether your average trust score has been rising or falling over the past month, even though TrustLens was only just installed. A declining trend is worth noting; it can reflect a growing abuse problem or a recent change in your return or coupon policies.

Category return rates

This chart shows which product categories have the highest return rates across your customer base. Cross-reference this with the segment distribution: if one category has a disproportionately high return rate and several of your Critical customers are concentrated in that category, you may have a category-specific exploitation pattern.

Top returners and high-risk attention list

At the bottom of the dashboard, TrustLens surfaces the top returners (by return rate) and the highest-risk customers (by trust score). These are not automatically problematic — high return rates can be legitimate — but they are the customers worth looking at first. Click any name to go to their full profile.

Step 4: Looking at Your First Customer Profiles

The TrustLens customer list (TrustLens → Customers) is where individual customer analysis happens. It shows every profiled customer with their trust score, segment badge, return rate, and order count. You can filter by segment, search by name or email, and sort by score.

Start with your Critical segment

Filter the list to Critical. If you have any customers in this segment, review them one by one. Click a customer’s name to open their full profile. The profile shows:

• Trust score and segment badge
• A score breakdown: every signal that contributed to the score, with the module name, the adjustment amount (positive or negative), and the reason text
• Key metrics: total orders, total refunds, return rate, refund value, coupon use count, cancellation count
• Any linked accounts TrustLens has detected, with the match types that triggered the link
• A full event timeline — every order, refund, coupon application, cancellation, and score update, in chronological order

Read the event timeline. The score breakdown tells you the what; the timeline tells you the when and how. A customer with a score of 8 who has a 68% return rate going back 18 months looks very different from one who placed two orders last week and triggered the coupon-then-refund signal twice. The numbers are the same on the list view. The context is everything.

Check a few VIP profiles too

It is worth looking at the other end of the scale. Click into a few VIP customers — customers with scores in the 85+ range. Their profiles show the positive signals: long order history, clean return record, no coupon abuse flags. This gives you a reference point for what “healthy” looks like in your own store’s data, which helps you calibrate your reading of the riskier profiles.

The allowlist — when to use it on day one

If you recognize any customers in the Risk or Critical segment who you know are legitimate — a business buyer with unusual order patterns, a wholesale customer with high order volume and above-average returns for genuinely defective products — add them to the allowlist now. Allowlisted customers are locked at a score of 100 and will not trigger any enforcement, regardless of what the detection modules find.

To allowlist a customer: open their profile, then click the “Allowlist” button in the action buttons area. The score updates immediately.

Step 5: Trust Scores in Your WooCommerce Orders List

TrustLens adds a trust context layer to the standard WooCommerce orders interface — in two places.

The orders list column

On the WooCommerce → Orders screen, TrustLens adds a segment badge column next to each customer name. The badge shows the customer’s current segment (VIP, Trusted, Normal, Caution, Risk, or Critical) in the segment’s color. Clicking the badge links directly to the customer’s TrustLens profile.

You can also filter the orders list by segment using a dropdown that TrustLens adds to the order filters. This lets you pull up “all orders from Critical customers” or “all orders from Risk customers” in one click — useful when you want to review recent orders from high-risk customers as a group rather than one at a time.

The order edit metabox

When you open an individual order (WooCommerce → Orders → any order), TrustLens adds a metabox on the right side of the screen showing the customer’s trust score, current segment, and key risk metrics. You see the risk context while processing a specific order without having to navigate away to the TrustLens customer page.

This integration is on by default. If you want to turn it off (for example, to reduce visual clutter on the order screen), you can disable it under Settings → General → Order Warnings.

What to Do Next — and What to Leave Alone for Now

After completing the steps above, you have done the meaningful setup work for a first session. Here is a practical guide to what comes next, and what to hold off on.

Do: set up email notifications

TrustLens → Notifications has email notification settings. There are three free notification types worth enabling if they are not already on:

• Welcome summary — sent 24 hours after activation, summarizing your store’s current risk picture. If you are reading this guide, you probably missed it — check the Notifications page to confirm it is set to your correct email address for future use.
• Weekly summary — a regular email showing your current segment distribution, top returners, and any new high-risk customers. Low noise, genuinely useful.
• Blocked checkout alert — fires when a blocked customer attempts to check out. Only relevant once you have enabled blocking and added customers to the block list, but worth turning on in advance.

Do: make a note of any customers you want to revisit

If you saw customers in the Critical or Risk segment whose event timelines showed genuine behavioral patterns — not data artifacts, not legitimate business patterns — note them down. You do not have to act immediately. The next step is understanding whether checkout enforcement makes sense for your store before you enable it.

As a starting point, the post on why blocking bad WooCommerce customers manually never works is useful context if you are thinking about what enforcement looks like in practice — specifically why static blocklists don’t close the loop and what behavioral triggers actually do.

Do: check the dashboard weekly, not daily

The TrustLens dashboard is designed for a quick weekly review, not daily monitoring. Check whether the average trust score has shifted, whether the Critical segment count has grown, and whether any new names have appeared in the high-risk attention list. Five minutes a week is enough to stay on top of the picture TrustLens builds.

Don’t: enable blocking before you are ready

Blocking a customer is consequential. Before you enable checkout enforcement and start blocking people, make sure you have read through at least several profiles in the Critical and Risk segments, confirmed the signals are genuine, and have a plan for what happens when a blocked customer contacts your support team. The TrustLens block message is customizable — set it to something that directs customers to support rather than explaining the reason for the block.

Don’t: change threshold settings based on gut feel

You now have a full picture of your store’s risk data. Use it. If you want to change the return rate thresholds, look at the category return rates chart first. If you want to change the minimum orders threshold, look at how many customers in each segment have fewer than 5 orders. Data first, then settings.

Don’t: delete customers from TrustLens profiles unnecessarily

The customer list has a bulk-delete option. Resist using it unless you have a specific reason — for example, removing test accounts from your development period. Deleting a customer profile removes their entire event history and score, which means TrustLens will rebuild them from scratch on their next order. For customers with genuine behavioral patterns, this erases the evidence that supports your policy decisions.

Common First-Session Questions