Since we released video analytics last year, the number 1 request has been to add a library for tracking JW Player. Well, we just did that. You can find it on our video help page.
We've also been fixing a bunch of bugs recently, and adding a few minor new features. We don't normally make a blog post just for this type of junk, instead preferring to piggyback on top of another post, so here we go:
- NEW: Checkbox on the tracking code page to disable affiliate badge (for paying members)
- NEW: Email reports are now in your selected language, instead of English for everyone.
- NEW: go.mail.ru is a search engine, not a web mail domain - yes, we hear you :)
- FIXED: Tracking code "pings" now end at 10 minutes as stated in the docs, rather than 8 minutes and 40 seconds (this was a math fail on our end)
- FIXED: The "Flashy" widget was broken.
- FIXED: After editing site prefs, you may have seen a message about your site being disabled.
- FIXED: Y-axis text in charts was getting truncated for values over 6 digits.
- FIXED: Loading a site, changing to a different site, then choosing "Bigscreen" would load that for the FIRST site.
- FIXED: Non-paying users who use our Wordpress plugin, viewing stats within the WP admin area didn't count as a "login" so they were getting disabled after 60 days of no logins. Now we count that as a login, even though "technically" it is not, to avert this problem.
We've been working on a gigantic update to alerts, goals, and spy, and here it finally is. The most major update is to alerts, so we're pulling that out of the blackhole that is your site preferences and putting it front and center, as you can see on the right.
So what's new? Here's what the alert setup page looks like now, which should give you a nice overview of everything that's new:
Let's start with the new ways to be notified: Desktop, Sound, and ClickyTouch (our official unofficial iOS app). These are in addition to the previous methods, which are Email and Twitter. Any alert you setup can use any combination of these 5 methods, including all of them, so it would be pretty much impossible to miss an alert if you set it up right!
Desktop alerts - You may have seen some web apps using Google Chrome notifications (Tweetdeck, Rdio, etc). We explored this option, alongside using jGrowl for other browsers, but I'll be honest: The Chrome notification API is horrible and has very limited options and functionality. It's nice you can see them without having to have the browser in focus, but that's the only nice thing about them. So, jGrowl for all. (I'm aware the screenshot above mentions the ability to enable Chrome alerts - it is from a few days ago when that feature was still in place, so the shot is simply out of date and I'm way too exhausted to make a new one - sorry!)
Desktop alerts will appear in the bottom right corner of your browser window. Here's what they look like:
At the top is the alert name. If there's any revenue associated with this alert (from a goal), that will shown on this line too. Next line is brief details about the visitor: country, then IP tag OR custom->username OR organization OR IP address (in that order of preference), then their referrer. The last line is a link to view the session immediately on Clicky. And on the bottom right is a "mute" link, which is handy when you just want some piece and quiet to browse your stats. When alerts are muted, there's a "sticky" box in the bottom right corner (which you can see in the setup screen above) informing you of their muted status, with the ability to unmute them.
Sound - These add a lot of personality to alerts, and allow you to know an alert has been triggered even when you're looking at another tab or doing something else on your computer. Example sound: Cash register - perfect for goals where you make money! There's a total of about 20 sounds available.
ClickyTouch - The icing on the cake. ClickyTouch is a third party product for iOS that uses our API to give you a nice interface for Clicky on the go. We worked with Steve (the developer) to integrate push alerts into the app. So if you have ClickyTouch installed and check this box for an alert, you can get alerts immediately on your iPhone or iPad, wherever you are. And if you "view" the alert, it will pop open ClickyTouch and show you the visitor session that triggered it.
Important - to receive alerts on ClickyTouch, you must update to 1.5.2, which was just released in the app store alongside this release.
Email and Twitter - These are the original alerting methods we've had for over a year and they still work the same way. You can receive alerts via email or Twitter direct message. To get alerts via Twitter, you must be following Clicky on Twitter.
In addition to these new methods of being alerted, we've added two new types of alerts:
New visitors - This is an extension of new visitor sounds in Spy we added a few weeks back. That method only worked in Spy. This method works no matter what report or page you are viewing. But the option to toggle it on and off is still available in Spy as well. If you enable it via Spy, by default it will only be the traditional "ding" sound. But if you set it up in the alerts area instead (or edit it after enabling via Spy), you can have it to a desktop alert also or instead. To ensure we don't inadvertently hammer third party mail servers and APIs, this alert ONLY works with sound and desktop - the other three options are disabled.
Custom data / IP tags - We've had countless requests for alerts for when a specific visitor is viewing your site. This is the answer to that. Any visitor that you have "named" with IP tags, you can now create an alert for them. Even better, if you use our custom data tracking API (and if you're not, you're crazy - it's our best feature), then you can trigger an alert for ANY custom data that you add to a visitor session.
I want to talk more about desktop and sound alerts for a minute. To be clear, since these are integrated into the web site itself, these only work when you have our web site open. But if you're anything like us, that's pretty much 24x7, so no biggie, right?
Depending on how many alerts are queued up to show you, they are visible for either 6 seconds or 10 seconds. We only do one at a time though, so as long as there are less than 6 queued up (and 99% of the time, that should be the case, unless you are insane), then they'll be displayed for 10 seconds. Originally it was 6 no matter what but I found myself racing to find what an alert was for if I wasn't looking at the site when I heard the ding, so I decided it was much better to have them visible for a longer period of time when there's only a few to show.
When you are viewing reports for just one specific site (e.g. whenever you're inside the /stats/ directory), you will only receive alerts for that specific site. But if you are anywhere else on the site - user homepage, help, contact, etc - then alerts for ALL of your sites will be active. And in this case, we append the site's name to the end of the alert title, so you know what site it's for, as can be seen here:
We cleaned up the goal setup page quite a bit, so only the basic options that most of you need are up top, with the rest in the "advanced" section. And as you can see by this example alert name, we now allow "global" wildcards, meaning the entire goal can be just a wildcard. In this case, ANY page view will trigger the goal. You can do the same thing with funnels, as well as search and referrer alerts (which are different from the ones in goal, because in goals they can only be funnels. This is perhaps another area we could clean up a bit. It would be nice to setup a goal for a specific search instead of only being able to use that search as a funnel).
You can also see that we've added a shortcut to create an alert for a goal as well after you've saved it. This takes you to the alert setup page, with the alert name prepopulated to match the goal name, and the "goal" alert type with the proper goal preselected.
But wait, there's more! We thought it would be quite nice to actually highlight the goals in Spy as well. As you can see here, the row is highlighted, and the goal icon you chose is on the right hand side:
Desktop and sound alerts work the exact same way here as they do in the rest of Clicky, so I'm not including a screenshot of that here.
What about Bigscreen?
You don't think we'd leave one of our newest most popular features high and dry, do you? That's right, alerts even work in Bigscreen, as you can see below. We made the fonts extra big so you could read them from afar. The alert visible here is the new "new visitor" alert, mentioned above. As you can see, no visitor details are shown. I wanted to touch on this briefly. The reason is because there may be 100 new visitors every minute, so this is more of a "batch" alert. In other words, you can read it as "1 or more visitors have arrived since the last time you saw this alert". Because of this, it is a bit generic. Maybe we'll clean that up a bit in the future but for now, this made sense.
We've tested this very thoroughly but we do expect there to be some minor bugs, especially with the Spy stuff. So let us know if something doesn't work like you expect it to.
Last, when creating alerts, there's up to a 30 minute delay before they are fully active within the system, so be patient -- and enjoy!
Yes, there were some bugs. Just pushed an update that fixes them. Changes:
- FIXED: Spy was showing URL instead of Title in the top right content box
- FIXED: "Unmute" alert box was MIA because of last minute change to the way it works that wasn't fully testing before deploy
- FIXED: global alert bombardment when leaving /stats/ - now, all alerts are "reset" when you go to a non-stats page so you'll only get new ones that occur from that point onward.
- FIXED: clicking an alert URL was supposed to load via Ajax, but was not because of, well, it was dumb let's just leave it at that.
- FIXED: Minor goal processing bugs in Spy
- NEW FEATURE! You can use wildcards in the custom data alert type, including a "global" wildcard "*" to match a visitor with that variable of ANY value, e.g. username=ANYTHING.
Goals have always been "exact match" by default, and only used any kind of wildcard matching if you specifically added that in. We thought this was the best way to do it but over the years, we've found that the vast vast majority of support requests that have to do with goals are because the user is not using wildcards where they should, usually on the end of the string.
For example, a user might enter "/thankyou.php" as their goal URL, without realizing (or simply forgetting) that these types of pages typically have query parameters too. Then their goal wouldn't work, so they'd contact us, and adding a wildcard on the end was almost always the only change needed. Sometimes a wildcard is needed at the start though as well, but usually just the end.
So, as of now, all goals by default will be processed as if they had a wildcard at the start, and at the end. We know this won't work for everyone of course, so we added a new checkbox to the goal setup page called "exact match". This will force the old behavior, but it is off by default (based on our analysis of how you have setup goals, very few of you will need it). We also expect quite a few people who setup goals but they never worked to suddenly find them start working as if magic has occurred.
While we were at it, we also fixed a few long outstanding bugs: "https://" goals used to not work, and depending on how goals were setup, sometimes they were case sensitive which was quite obnoxious. These are both fixed.
When you set various options in Spy, such as zooming in the map or disabling the popups, used to be that it wouldn't remember any of it next time you came back. Fixed that! We store your settings in a cookie so they'll be restored everytime you visit Spy (on the same computer/browser). This is a Clicky-wide setting too, so any site you're looking at or any account you're logged into from the same computer - bam.
We've also added a request we've had more often than we would expect, which is having a sound effect play when a new visitor arrives. This is of course DISABLED by default. This feature will mainly be of interest for lower traffic sites, who don't always have visitors online, but would like to know immediately when someone shows up.
The HTML5 audio element is being for this (yay, no flash needed!), and we have both mp3 and ogg formats so the sound will play in all five major browsers. Of course you will need a browser released within the last couple of years for it to work, but thankfully our userbase is quite good at abandoning old, depressing technology. For example, less than 0.5% of you are still on IE6 - that's way better than average! It's because you are SO AWESOME!!