Overview
The night at a glance: what the engine read, what it decided for every customer, and what it has sent today.
Data as of 2 Nov 2026
Demo engine, invented data
Sends today
Since midnight in the brand's time zone (Europe/London). The engine sends in even slices every 20 minutes from 09:00 to 18:40 local time. Held-back customers are recorded but never emailed, so they are not counted.
Held back
The permanent control group the engine measures against.
5 percent of customers are held back permanently, by a stable hash of their id.
No engine route counts the held-back group or compares it with the emailed group yet, so the portal shows the design figure, not tonight's count. Each customer's own group is on their page.
Customer health
Display labels only: they follow your business-logic thresholds and do not change campaigns, scores or who is emailed.
- New1082.1%
- Healthy4489.0%
- At risk911.8%
- Churned3,54771.5%
- Never purchased76015.3%
Last build
Every night the engine rebuilds every table into a new database beside the live one, swaps it in at about 04:00 brand time, and restarts. The store export and the swap happen outside the run reported here.
Last night's build finished and is the data every page shows.
- Data as of
- 2 Nov 2026
- Started
- 3 Nov 2026, 03:00 Europe/London
- Finished
- 3 Nov 2026, 03:35 Europe/London
- Took
- 35 min 47 s
13 steps, in the order they ran
- Product recommendations1 min 55 s
- Order model52 s
- Cross-sell model1 min 25 s
- Subscription model1 min 5 s
- Campaign assignment2 min 15 s
- Database load17 s
- Analytics40 s
- Customer profiles1 min 35 s
- Product table6 s
- Customer table15 s
- Health and rhythm labels1 s
- Holds2 s
- Attribution13 s
How long each step took, as the engine reports it.