Analytics
Who reads the public site, what they read, and how they got there, and the same for the app. Counted on my own server: a row holds a path, which of the two sites it was on, the host a reader arrived from and the time. No address, no cookie, no identifier of any kind.
Views per day
Every day in the range, including the ones with nothing on them.
Loading…
Which pages are read
Split by property, because "which of the two sites" is the first question and a merged list of paths cannot answer it.
Loading…
Where readers came from
The host only. A full referring URL can carry somebody's search terms in its query string, so the API keeps the host and throws the rest away before anything is written down.
Loading…