Overview
See where your size charts need attention, then review how shoppers use Mirraya.
Needs attention
Chart gaps in your reporting period, plus setup and all-time return-data checks.
Loading chart and return evidence…
Shopper activity
Usage shows engagement. Fit outcomes below show what happened after purchase.
Loading overview…
Loading product insights…
Products to review
Largest chart gaps first. A chart warning is a range mismatch, not a confirmed fit failure.
| Product | Recommendations | Outside chart | Needed size | Actions |
|---|
Understand this selection
Every count and distribution below uses the same product and category filters.
Size labels can mean different measurements across products. Select a product to review its chart.
Where shoppers needed a size outside the available chart.
Recommendations within this selection.
Kept (inferred) means no return is recorded; it does not confirm that the size fitted.
| When | Garment | Size we gave | Size bought | What happened | Reason |
|---|
Products
Charts are shared across a product's colours.
| Product | Sizes |
|---|
New size chart
Advanced fit settings
Optional stretch, cut and other fit settings. Existing values are kept when you save.
Widget key
PublicIdentifies your store. Safe to publish; it only works from your allowed domains.
Allowed domains
Only these sites can use your public widget key. Include every site where you install the widget.
Currently allowed
One host per line, or separated by commas. For example: shop.alder.com.
Advanced key management
For key rotation and server integrations.
All keys
Multiple keys can be live at once. Install a new key on your storefront before revoking the old one. Revoking takes effect immediately and cannot be undone.
Secret key for server integrations
Most stores only need the public widget key. A secret key (mk_live_…) is for your backend only. Treat it like a password: it is shown once and cannot be retrieved again.