Homepage metrics

Functions active

The green Functions active pill at the top confirms FairDrop's checkout enforcement is deployed and switched on for your store. If it reads Functions pending, your rules are saved but not yet enforcing at checkout — finish activation to turn it green. This reflects deployment, not traffic, so it doesn't change based on orders.

Protected products

The number of distinct products and variants currently covered by a live (enforcing) policy, plus how many policies they're spread across (e.g. “4 across 4 policies”). It's a snapshot of what you're protecting right now, read from your policy configuration — not from any sales.

Buyers stopped at the gate

The headline is the total number of shoppers stopped by the storefront gate in the last 24 hours— real people who tried to add a protected item and were asked to verify first. It's split by the reason they were stopped:

• Not signed in— the shopper wasn't logged into a customer account.
• No passkey— signed in, but hasn't set up a passkey yet.
• Needs re-verify — signed in and enrolled, but their verification had expired (a passkey check lasts 10 minutes).

Each stop is counted once per shopper attempt, so a buyer who clicks the prompt several times only counts once.

Orders protected

The number of completed, paid orders that contained a protected item — counted since you installedFairDrop, with a this-week vs. prior-week breakdown. Where “Protected products” is what you've set up, this is the real-world outcome: actual purchases that went through your protected drops.

Verified buyers recovered

This is your passkey recovery funnel for the last 24 hours. It answers: of the real shoppers stopped for a missing or expired passkey, how many came back, verified, and bought? The three stages are:

• Stopped (passkey) — signed-in shoppers stopped because they needed to verify a passkey.
• Verified passkey — of those, how many completed verification.
• Completed purchase — of the verified, how many went on to pay.

The large percentage is the recovery rate — completed purchases ÷ shoppers stopped. Recovery rate vs prior compares it to the previous 24 hours in points, and the note below counts anyone who was stopped but didn’t return. A high rate means the gate is converting legitimate buyers rather than losing them; a low rate is worth investigating — often a confusing enrollment step.

Passkeys enrolled

The lifetime total of passkeys shoppers have set up across all your protected drops. Unlike most tiles this is all-time — not a 24-hour or weekly window — so it represents the size of your verified-buyer base.

Verifications

The number of successful passkey verifications in the last 24 hours — each time a returning shopper confirmed their identity with their device biometric to get past the gate. A steady stream here means enrolled buyers are sailing through.

Why bots aren’t counted

The gate tiles count real shoppers who reach your storefront. Bots and scripts that skip the storefront and hit checkout directly are still blocked — the checkout Function stops them regardless — but they're deliberately not itemized here, which is why you may see a “Bots are blocked but not counted here — why?” note. Counting them requires an enterprise-only checkout-telemetry feature; blocking them does not.