Jive acquires Filtrbox

Jive Software, who makes fabulous collaboration tools for both internal Enterprise use, and external communities announced today that they are acquiring Filtrbox.

TechCrunch notes:

Jive says that Filtrbox’s social media real-time monitoring technologies will be absorbed into Jive’s platform to help businesses and brands harness the power of the real-time web from within Jive’s collaborative software.
...
Jive is wise to boost its offerings as it is going to be competing with Salesforce’s Chatter and other social offerings. But the company is ready for the fight.

RWW notes:

How companies leverage the cloud will determine how they fare in the market. The ability to crunch large amounts of data is vital for understanding the real-time nature of how conversations flow. Jive seems to understand this and appears to be moving more toward a cloud-based strategy.

Initially, Jive will market Filtrbox through its Jive Market Engagement solution along side Radian6. Jive and Radian6 formed a partnership back in September. Here's what Jeremiah Owyang and his colleague, R "Ray" Wang had to say about the partnership.

Radian6 and Filrtrbox are essentially in the same space. it is unclear how the relationship between Jive and Radian6 will be affected by the Filtrbox purchase.

This definitely muddies the waters with Radian6. It'll be interesting to see what happens there.

Not only is this a social monitoring play, but there are analytics implications here as well. An interesting move, and one we'll watch closely! Congrats to my friends over at Jive!

Flurry Makes Another Move - Mobile App Analytics Revenue with comScore

Flurry has just announced a smart deal with comScore... Gagan Biyani over at MobileCrunch has the scoop:

Flurry wins because comScore’s sales force will sell Flurry’s data analytics software, generating an initial revenue stream for Flurry. According to Director of Community Peter Farago, clients will pay comScore to have Flurry’s SDK installed on their applications, and Flurry will make a revenue-share for each client. ComScore is adding reporting and charting software on top of Flurry’s analytics. Flurry is traditionally free for developers, but comScore is going to charge clients to use Flurry because of the additional reporting and charting they add.

This news is getting a lot of attention. As it should. This is a good deal for Flurry who, as a young company trying to make a living in the already crowded Analytics space, have figured out two revenue models already.

I agree with Om Malik though:

The way I see it, it’s only a matter of time before someone like comScore or The Nielsen Co. buys out Flurry and its rivals. It’s becoming increasingly evident that the mobile web and mobile apps are part of new usage behavior that goes beyond today’s plain-vanilla web.

There are plenty of smart folks in the Analytics and #measure space that know full well what is required to make their holistic, powerful solutions work for brands around the world. This is a wise move by both companies to make a big play in this rapidly expanding space. 2010 will be a great year for Analytics in mobile measurement. Bring it on!

HTML5 rel=noreferrer and Analytics

Phillip Lenssen over at Blogoscoped notes this interesting HTML5 nugget from Mark Pilgrim's DiveIntoHTML5 site that suggests that there will be a new relation attribute (rel="noreferrer") for links that will force browsers to drop the referrer from the header when selecting links.

This is how Mark describes it in the semantics section of his site:

rel="noreferrer" “indicates that no referrer information is to be leaked when following the link.” No shipping browser currently supports this, but support was recently added to WebKit nightlies, so it will eventually be showing up in Safari, Google Chrome, and other WebKit-based browsers. [rel="noreferrer" test case]

This is an interesting use of rel in HTML, changing the behavior of the browser. Especially a default behavior like this that has been around since the stone age (early stone tablets had a referrer of course...).

The impact to the Analytics community could be quite far-reaching. Referrer information is obviously quite important to a lot of base reporting dimensions. We'll all be interested to see if this specification will actually make it into HTML5.