The news feed.

Posted by on April 19, 2016
TL:DR; hosted sites (does not affect .org/self hosted sites) widgets were broken, now they are fixed.

A few days ago it was brought to our attention that widgets on hosted sites were no longer functioning and displaying an incorrect concurrent user count.(if you run your own install of WP on your own server this wouldn't have affected you).

What happened was that, in the latest update to the platform, the Photon functionality was turned on by default. Photon retrieves images embedded in your blog once and then hosts them off of Wordpress' servers to speed up blog serving time by reducing the number of locations your browser has to look for image assets. While this is a great feature in most cases it causes a problem for services like where we rely on the blog users loading the widget image from our servers so that they can be counted in the stats. With Photon proxying our widget images no one was getting counted in the stats for sites hosted on as the end users never requested the widget images from us directly.

We've been working with Automattic (the fantastic company behind Wordpress) over the past few days to find a solution that allows widgets to continue functioning on hosted blogs, and I'm happy to report that there is a solution now in place that allows the widget to work properly once again!

You shouldn't need to make any changes to your widget code, but if you are seeing a lot of "Unknown" users in the readers list on your stat pages you might want make a very small change to your widget code to serve the widget off of https and not http.

Example, if your widget code looks like:

<a href="">
    <img src="" width="81" height="29" border="0" title="Click to see how many people are online" />

Change it to:

<a href="">
    <img src="" width="81" height="29" border="0" title="Click to see how many people are online" />

The only difference is the  http  in the img tag has been converted to  https .

As always, if you have any questions don't hesitate to contact us.
Posted by on June 26, 2014
We've had a number of different widget codes over the years and as such we like to make sure our long time users update their codes to ensure they are getting the best performance possible from the widgets on their site.

About 3 years ago we converted the Javascript code from the traditional synchronous (sync) style to the newer asynchronous (async) style. The async version has the advantage of never blocking loading of page elements on your site, which would have been possible with the sync version.

Although the async code has been available for many years we are still seeing lots of sites using the sync version, so we'd like to provide this message to assist users in determining what sort of code they are running.

If the widget code installed on your site looks something like the following code you are using the old sync version and we recommend you convert to the async version. Note: the code below is an example only, it shows a dummy site identifier (123456789012) and is for the small widget, the other types have slightly different formats.

<script type="text/javascript" src=""></script>
<script type="text/javascript">WAU_small('123456789012')</script>

If your code looks something like the following (again, this is an example, it will vary from widget style to widget style) then you are using our async code and all is good :)

<script id="_wau3b8">var _wau = _wau || []; _wau.push(["small", "123456789012", "3b8"]);
(function() {var s=document.createElement("script"); s.async=true;

We'd be happy to help you convert the code on your site to the async version if you are still using the sync version, feel free to <a href="">contact us</a>.

If you need a new widget code, just grab one from <a href="">the showcase</a> to ensure you have the latest code!
Posted by on March 19, 2014
We've added a pie chart to your stats dashboards showing the breakdown of user devices to your site. We've broken the device down to the critical ones (phone, tablet, and desktop) so you can get a sense as to what devices your users are accessing your site with.

We've also provided the data not just for the current moment but also for the past 24 hours so you can see how device usage changes on your site over the day.
Posted by on February 5, 2014
There have been reports of some users reporting that a widget is being added posts they make on their blogs or comments on forums, etc.

This is caused by a browser extension that users have previously installed that adds widget code to comments and posts. The extension often masquerading as Adobe Flash Player (which is not a browser extension/add-on, it is a plug-in) or some other video player type add-on/extension. Users should remove the extension if it is causing them problems, and please contact us with any details so we can get things sorted out.

We do not support adding our widget code to anything other than webpages, adding it to emails, browser extensions, or other software violates our terms of service and is not supported.

Don't hesitate to contact us with any questions you may have.
Posted by Christopher on October 8, 2013
It's with great sadness that we learned out friends at Wibiya have decided to shutdown their toolbar product. We've worked closely with them since near day 1 and we're honored to work with them by providing our services through their toolbar - even near the end where we were the only third party service provider on the toolbar!

We wish everyone at Wibiya all the best in their future endeavors.

For our users who are currently using through the Wibiya toolbar, don't worry you can still use our services! Simply grab a widget code from our showcase and replace the site id in the widget code with the site ID your Wibiya toolbar uses (contact us if you need help). By replacing the site id you'll retain all your existing stats.

If you are a PRO user, you can simply generate a widget code in the "Widgets" section of the PRO Control Panel, and install it on your site.