#Clicky clicky update
#Clicky clicky manual
#Clicky clicky windows 10
#Clicky clicky code
#Clicky clicky windows

But seriously it’s so long overdue that it feels surprisingly good to have finally done it.

I know, you are shocked to your very core.

We may add a link for you to do this more easily, like we do with organizations.Īnd there’s another “while we were at it” task that’s been long overdue – renaming “iPhone OS” to just “iOS” now. And if you copy/paste any of them into Google, you will find out what the actual model is. But the OS icon will at least give you a clue, e.g. Now, there are a lot of mobile device IDs, and some of them are kinda cryptic as you can see. With this, we’ve brought back the hardware report we removed a while ago because it had basically devolved into just a mirror of the mobile OS report.īut now look how much great data there is now, if you use this new option! But the good news is, if you set this up, we also request the hardware model if a visitor is on a mobile device.

Unfortunately we couldn’t make this work with the new site preferences UI method, so it has to be done manually. So we added a new clicky_custom option, also called getHighEntropyValues (we’re using the same name to highlight the relationship), to do just that.

#Clicky clicky windows

We don’t ever want to do something by default that would pop up a permissions dialogue, but at the same time we know some of you really want Windows 11 data. No browser is doing this now, but it’s designed to allow for this. Anyways, it uses an asynchronous Javascript promise so that it could pop up a permissions dialogue to a visitor when this data is requested. This API is only supported by Chromium browsers, but that’s most of them. There is an API to request more data from a user agent though, called getHighEntropyValues().

#Clicky clicky windows 10

Microsoft decided to hide Windows 11 identification from user agent strings by default, so we’ve reported them as Windows 10 this entire time, as have all other services as far as I can tell.

#Clicky clicky manual

You can still set these options with Javascript if you want, and we let the manual Javascript one take precedence if an option is set in both places to allow for overrides – but most people will be excited to see these options, which are under the new “advanced” area of site preferences: ones that should apply to all visitors and pages) to be settable via the UI. While we were at it, we moved every single clicky_custom option that made sense (e.g.

#Clicky clicky code

We had to change the way tracking works in order to allow cookies be controlled by the database rather than manual Javascript code on your site. Although we think today’s obsession with “privacy” is a bit overblown, we must change with the times, or we’ll end up like Grandpa Simpson. We’re killing third party cookies entirely now, so we’ll just ignore this one 100% of the time.ĭid you know that Clicky is older than the first iPhone? Can you even remember what life was like before smartphones? It was basically the stone age, but that’s the era that Clicky started from. We also had a single third-party cookie (“cluid”) we used for cross-domain tracking, for those of you with multiple sites. Otherwise they’ll still be sent to us, but they’ll be ignored, and they’ll eventually expire naturally. Check out our privacy policy (scroll down about half way) to see all tracking cookies and their purposes.Īs for existing tracking cookies out in the wild now, we’ll only use them if a site has enabled cookie tracking. With cookies, we were able to sample per visitor, but without cookies, that randomness can only be per pageview. Also heatmaps – this is the one piece of data we log that’s sampled, since it takes up a lot of extra storage and bandwidth. UID tags and filters will now be mostly useless. Unique visitors, new visitors, and returning visitors won’t be nearly as accurate. There are some downsides to not using cookies of course.

#Clicky clicky update

(You don’t need to update anything to get this new functionality, but you may want to double check your current privacy settings (see link above)). You could disable them manually before, but now it’s the default. we’ve been anonymizing IP addresses since GDPR became law, but tracking cookies were the one exception. We’re happy to announce that our tracking is now 100% cookie-free by default, which means Clicky is now privacy-friendly out of the box.