Most loyalty dashboards report a dozen numbers and explain none of them. The result is an owner who checks the page every morning for a week, sees four figures move, cannot tell which movement matters, and stops looking.
Seven numbers do the work. They are listed below under the exact labels Fideliya prints on screen, so the thing you read here and the thing you read on the dashboard are the same thing with the same name. Every one of them is reported today. None of them comes with a target, and the last section explains why publishing one would be the least honest thing on this page.
The seven numbers, by the name on the screen
Total Scans. Every stamp or point recorded in the window. This is the volume number and the one that moves first, because it moves whenever your day is busy. It says nothing on its own about loyalty. Its job is to be the denominator you read everything else against.
Active customers this period. How many distinct people were scanned inside the window, printed above a smaller line reading "of N enrolled". That second half is the one people skip and the one that carries the meaning: a hundred scans from twelve people is a different business from a hundred scans from ninety.
Returning this period. The share of customers active in the window who came in more than once, with the raw pair underneath it: "R of A who visited". This is the closest thing the product has to a loyalty reading, and it is the number that takes longest to become believable.
Rewards redeemed. How many customers actually reached and took the thing you promised. It is the only number here that measures the offer rather than the traffic. A program with scans and no redemptions has a goal set too far away, and this is where that shows.
Loyalty Funnel. One cohort followed through four stages: joined, first visit, returned, earned a reward. Each stage is selected from the stage above it, so every drop is a real drop. The first gap is usually the loudest, because joining and visiting are genuinely two events in this product and not one.
Not in for 8+ days. The named list of people whose last visit has slipped past a week, sorted so the ones you can still do something about are at the top. It is a list rather than a figure on purpose. The number is not actionable; the names are.
Weekly rhythm. When your regulars actually come, by day and hour, with the peak window called out. This is the one number here that is about your staffing and your offers rather than about your customers.
Where each one lives, and on which plan
| Number | Where it lives | Plan |
|---|---|---|
| Total Scans | Analytics, first tile of the hero row | Every plan |
| Active customers this period | Analytics, second tile, with "of N enrolled" beneath | Every plan |
| Returning this period | Analytics, third tile, with the raw pair beneath | Every plan |
| Rewards redeemed | Analytics, fourth tile | Every plan |
| Loyalty Funnel | Analytics, below the scan trend | Every plan |
| Not in for 8+ days | Analytics, named list with a message action | Pro and Enterprise |
| Weekly rhythm | Analytics, day and hour grid with the peak window | Pro and Enterprise |
The window matters as much as the plan. Free reports on 7 days. Pro and Enterprise add 30 and 90, which is the difference between watching a week and watching a season. The pricing page carries the full split.
Reading them in week one
In the first week only three of the seven are saying anything, and knowing which three saves a lot of misreading.
- Total Scans tells you whether the counter is using it. A flat line here is a staff problem or a signage problem, never a customer problem. Nobody declines a card they were never offered.
- Active customers, against the enrolled count beside it, tells you whether joining is working. If enrolled is climbing and active is not, the card is being added and then forgotten, and the fix is at the till rather than in the program.
- The first funnel gap, joined to first visit, is the honest week-one reading. Joining writes no scan in this product, so a first visit is a real event that either happened or did not.
Returning this period, rewards redeemed and the drifting list are all close to meaningless in week one, for the same reason: nobody has had time to come back or to fall behind. Reading a returning rate on day four and concluding anything is the most common way to talk yourself out of a program that was working.
Reading them in month three
By month three the order inverts. Total scans becomes background, and the three that were silent become the ones worth opening the page for.
Returning this period is now comparable, because there is a previous window of the same length to compare it against, and the dashboard prints that comparison beside it. Rewards redeemed is now a verdict on the goal you chose: a quarter with scans and almost no redemptions is a goal set too far out, and moving it is a smaller decision than most owners treat it as. The weekly rhythm has enough scans behind it to be a shape rather than noise, which is when it starts changing what you do on a Tuesday.
The drifting list is also now populated with people who genuinely used to come, rather than with people who joined last week and have not been back yet. That distinction is why the band structure exists at all, and it is set out in full on how to win back customers who stopped coming.
What a move usually means
None of the readings below is a rule. Each is the first thing worth checking, in the order that costs least to check.
| What moved | What to look at first |
|---|---|
| Scans up, active customers flat | The same regulars visiting more often. Good news, and not growth. |
| Active customers up, returning down | A wave of new joiners diluting the rate. Check the funnel cohort rather than the tile. |
| Enrolled climbing, first visits not | The card is being added away from the counter, or the QR sits somewhere nobody scans at the till. |
| Scans healthy, rewards redeemed near zero | The goal is further away than the visit rhythm supports. |
| The 8-day list growing week on week | Retention slipping, and the only one of the seven that names the individual people it is describing. |
| Rhythm peak shifting | Trading pattern changed. Staffing and offers, not loyalty. |
One trap is worth naming because it is built into the product and not into your reading of it. Two screens in Fideliya compute a repeat rate. The analytics figure is customers who returned inside the window over customers active inside it. The overview figure is lifetime repeaters over everyone ever enrolled. Both are correct, they answer different questions, and they are labelled differently for exactly that reason. If two numbers disagree, read the label before you read the number.
The one number this product refuses to report
Fideliya can send a message to the lock screen of everyone holding a card. What it reports afterwards is that Apple and Google accepted the message. It does not report that anyone saw it, and it never will on the evidence available, because there is no read receipt in the wallet pass channel: no delivery webhook, no open event, nothing that observes a human eye.
This is the concession that belongs on a page about measurement. Every messaging tool that publishes an open rate is either counting a tracking pixel or counting something the platform told it, and the wallet channel gives neither. So the product calls the state accepted rather than delivered, and an owner reading this page should treat any loyalty vendor quoting a wallet push open rate as quoting a number nobody can have. What to send instead, and when, is on the win-back page.
Why there are no target values on this page
Every benchmark published in this category, when chased, ends at a company selling loyalty software. That includes the ones with a decimal point. A target invented by a vendor and quoted back at an owner is worse than no target, because it makes a working program look broken and a broken one look fine.
The comparison that survives scrutiny is against yourself. Each of the four hero tiles prints its change against the window immediately before it, and that comparison is computed from your own data on your own customers. Where there was no previous window, it shows nothing rather than showing a growth figure against a period nobody measured. That refusal is deliberate, and it is the same refusal this page is making.
Sources
Every metric name above is quoted from the English message catalogue this product ships, namespace dashboard.analytics, read on 5 September 2026, and each is cited to its catalogue key and its data field in the source note on this article. The four presence bands and the statement that they are not a partition come from the type documentation in the analytics module itself. The plan split comes from the feature matrix in the tier configuration. The accepted-not-delivered rule comes from the notification outcome module, whose own header records the production measurement behind it. This page quotes no third-party statistic, no benchmark and no target, because none of those exists in a form worth citing.
Fideliya is wallet-native loyalty program software for small businesses. Customers add a stamp or points card to Apple Wallet or Google Wallet in one tap, with no app to download and no account to create. Fideliya runs stamps, points, gift cards and referrals on one platform in English, French, Spanish and Arabic with full right-to-left support, and the free plan issues a real wallet pass for up to 20 customers. What the dashboard shows is described on the analytics page, and the plans are on the pricing page.