It seems the email report didn't get sent out for weekly or monthly.

Have to check it up.

I guess it's an awesome feature and people love it.
It should be an optional feature though because people who don't need it, shouldn't be suffering performance-wise.

There are also JS libraries that are doing this alreadyand they even have wonderful live demos (i.e. simpleheat demo, webgl-heatmap blog post, heatmap.js demo or this PoC). Of course there are also some SO threads, like this or this that give good insights.

Maybe it might be a killer feature that helps to gain visibility against the other analytic application.
Because apps like PostHog, Plausible, Ackee, Fanthom and Shynet doesn't seem to have it.
Countly. and Matomo have it only as a premium feature.

EDIT: Maybe it would also help to have a look how OpenWebAnalytics implemented this.

User agent can be seen as personal information for some. Let's not save it and also use it for the one-way hash for more accuracy.

move the marketing website, with the marketing pages and future blog out from the app and maybe move the application to the app. domain.

It should be pretty easy, and it is good to do this asap.

Domains dropdown, when logged in, won't show domains for subpages, only add domain when clicking on it.

Let's add domains on the subpages as well.

Track events, like goals or signups.

I saw that you are using Postgres for now. I thought that it might be of interest for you that Yandex created a database exactly for analytics data for their service Yandex.Metrica. It is called ClickHouse and uses Apache 2.0 license.

It is probably easy to integrate something like this in the beginning, otherwise it might be difficult at a later point (i.e. like it happened for Countly).

There are also a few crystal shards already: clickhouse.cr, clickhouse-table and clickhouse-crystal.

I'm just curious: any reason why the method is timedout instead of timed_out? 🤔

Same goes for timespent vs time_spent

Now when a device type is not found, it returns an empty string or nil.

Let's add a fallback using screen width to determine device type.

Make to metrics can be public with a sharable link.

Maybe using a token or a slugified url.

Add a way to use server-side tracking - first for pageview.

events will be supported later.

Hi Håkan,

I saw that you even created a Dockerfile but I can't find it at Docker Hub.

Maybe it would make sense to build releases automatically with GitHub Actions?

PS: Kindmetrics looks awesome so far!

Lucky 0.23.0 handles sessions and cookies better and has some nice things.

Let's upgrade lucky to 0.23.0 soon.

I have thought of some redesign to make it more clean and better structure of the subpages of an domain metrics.

What I will do:

• clean up header and navbar
• Add subnavbar for domains
• Change colors a bit to make it more clean

Find a good way to show details on pages, countries and more.

alternatives (maybe more):

• Modal
• own sub-page (having a tab)

Add so you can see how much up or down it have gone since last period in percentage

Like:
▲ 35%

or

▼25%

ANd show with colours if it is good or bad. Like for bounce, it is good if it goes down when the rest is bad if it goes down.

Add support for sessions so you can get:

• length user spent on the page
• bounce rate

And more things later, like:

• average page visits
• Average sessions per user

Change periods of the data in a simple way.

Current there are

• unique visitors
• page views
• bounce rates
• top referrers

And maybe it would be great to add some of the overview details also to the page details (i.e. countries and devices).

Also things like load time and session time would be interesting.

Here's an example from Shynet (IMHO it's not a page detail view but I guess you get the idea):

I'm not quite sure what "Duration" and "Load time" mean here.
I guess it would also be interesting to have

• median time (not avg, otherwise a single user behaviour might tamper all numbers)
• maximum time
• Pages Per Visit (I saw this in Open Web Analytics and I think it could be useful)
• Dom Clicks per Page?

Check if the client is a bot and don't save it as a pageview.

Maybe save it but don't count it on pageview.

See amount of users that are on the website live.

Should be able to see that through sessions without length set.

Recode it to be more flexible and prepare it to handle events.

Idea is to load it and be able to call window.kindmetrics.track('sign_up') to send custom events.
Pageview should work as usual.

Should be able to delete a domain in settings.

Same goes to the user, then all data will be removed, including domains and events.

Add secret for generating user hashes (ids)

Now it is done by a fixed string ("kindmetrics") Which is not so good security-wise.

When total counts are above thousand, let's type it as 2.3k instead of 2321

It makes it more readable.

Decide what to do with the referrer that is same domain:

Either:

• hide it
• Show it as (direct)

Add support to be able to host the track.js code on own subdomain.

Maybe even let it host the API there as well for extra based.

Have a today as period option where you can see the hours so far have gone today.

Also, add a custom period support where you can pick to and from dates.

It's probably good to have such things on the roadmap for later.
The current device overview doesn't seem to provide details like resolution and (i'm not sure how useful this is) something like carriers etc.

A general screen resolution overview would probably be nice as well.
This is how it looks in Ackee:

The URL in the confirmation email is wrong and is sent as an empty <a> tag.

It becomes <a>click here</a>

Probably because I use UserConfirmations::Show.url(token: @user.confirmed_token) instead of UserConfirmations::Show.with(token: @user.confirmed_token).url

Build support to send email reports, weekly (Mondays) or monthly. (first day of a new month)

These will be summaries the previous period with all the data we show on the dashboard in a nice way.

Should be able to add an email address to send to. So people don't need to share accounts or something.

• HTTP errors (i.e. 5.., 4.. status codes)
• JavaScript errors — it seems that Google Analytics is able to do this as well
  • FancyTrack
  • jsErrLog
  • JSNLog
  • or maybe even an easier self written solution
  • …

Clean up the classes, remove duplicated code.

Make an parent class for action and pages with prepared methods and params.

Browsers also store and send language preferences and I guess it would make sense to track & show this as well.

This is how it looks in Ackee:

Add the most common metrics for analytics.

• Unique visitors
• Pageviews
• Top Referrer
• Top pages visited (your own pages)
• Countries
• Devices
• Browsers
• OS

As usual there's also already something available 😉

• https://github.com/philnash/crotp
• https://github.com/SushiChain/crystal-two-factor-auth

Add payments for plans

It will be one of these:

• Stripe
• Paddle

Plans rules:

1. 9 EUR? - 50k page views per month
2. 15 EUR? - 200k page views per month
3. 39 EUR? - 1milj page views per month
4. QUOTE? - 1milj+ page views per month

Now referrer can get duplicated

One is the name and one is the domain of the referrer.

As example:

• Reddit
• reddit.com

Probably some bug in referer-parser.

Adding a bit stronger privacy on how identifying users.

Now we can see when a user come back after any time, 1 hour, 1 day, 1 week.

We should add a timeout to the user_id so we can not identify the user after he comes back.

My idea is to set a temporary user_id that is the same as we have now but gets removed after 30 minutes of inactivity, and then it will only have this time-based user_id.

we need it temporary to map a unique visitor for that moment.

Another issue for better visibility.
It seems that it needs those things to be fulfilled:

• Automate building a single node image for droplet on DigitalOcean
• Get approved to be added as partner on DigitalOcean Marketplace
• Check and submit Image for approval
• Image approved
• Test one click deploy

PS: I found this idea in the PostHog issues
PPS: Same goes for Heroku and Linode

We can add support to for medium.

It will be gathered from:

• utm_medium
• referer-parser's medium

in that way, you can group them.

Add authorization rules for domains and events with lucky_can

It would be nice to send configurable notifications when there are traffic spikes or dips.

for instance via:

• email
• XMPP (I simply love XMPP)
• Slack
• IRC
• Customizable webhooks
• […]

PS: It wasn't my idea. I got inspired by this shynet issue.

Making it easier to handle params for all queries.

Every query won't be called, but it will use common filtering/where like periods, domain_id scoping and stuff.

The bounce rate seems to acting weird and becomes zero in some cases.

It might be issue with the query and the cast to an integer. It might format wrong.

I refreshed a few times but I didn't got anything.

EDIT: Ah, I might have forgotten about the DNT setting! I guess that was the reason then?

Will DNT lead to a request in general?
I'm not sure how compliant this is but would it make sense to have a minimal request that counts non-tracked requests? Like an API call that just increases a number?

Make it a bit nicer to onboard and start tracking

something like this (I just took the first random image that matched):

Hi, just found about Kindmetrics. Looks nice.

Any plans to allow filtering metrics by path? (eg click on /foo and view pageviews and referrers for that specific URL)

Adding API for at least the data on the dashboard. Giving more value and more "ownership" to people over their data.