Loading Overview…
Sep 10 – Oct 9, 2026How Demo Store was used in the period
Plots this figure per day on the chart below.
190
+8.0% (+14) change vs. previous 30 days, until 18:52, better
signed in at least once
See identified visits124
−1.6% (−2) change vs. previous 30 days, until 18:52, worse
4.5% of 2,768 visits sent signup_completed · 124 conversion events
See converting visits2.3%
+0.5 pt change vs. previous 30 days, until 18:52, worse
45 of 1,950 writes failed
See failing routesPage views and named events, last 30 days
Page views8,979
Named events3,230
Previous period
| Page | Views |
|---|---|
| / | 2,011 |
| / | 1,394 |
| / | 1,206 |
| / | 1,042 |
| / | 659 |
| / | 569 |
| / | 547 |
| / | 455 |
| / | 347 |
| / | 269 |
Visits of last 30 days by the weekday and hour of their first page view.
FewerMore
Busiest: Monday, 19:00 to 20:00 (39 visits).
Download CSVActivity per dayTop pagesTop events
A visit is one browser tab, from its first event to its last; two tabs are never linked. An identified user is a distinct user id the site passed to identify(), usually when someone signs in; a visit without one is anonymous. A conversion is a visit that sent the project's conversion event at least once; the conversion events count every time it was sent. A write is a POST, PUT, PATCH or DELETE sent with trackRequest(). A failure is a status of 400 or above, or no response at all. A change is green or red only when the previous period counted at least 20 and it moved by 1.0% or more (0.5 points for the write error rate).