As originally thought, there are no significant changes in 7.0.816 which are obvious to most users, just bug fixes. Leah reports three main points:
Tab Clicks Not Being Tracked
None of the v7 clients (i.e. v7.0 beta clients, v7.0.0777, or v7.0.0813) were generating the reports that measure Tab usage. We were unable to track when any v7 client user clicked on any of our Tabs. This bug seriously impacted our Tabs business. We faced losing revenue from existing Tab partners, and we had no accurate data to use to attract prospective new Tab partners.
For those who are familiar with the tab config data, when you click on a tab, the URL specified in hiturl is requested. Grab a ZIP file of the request information here. I think this is the first time I’ve ever seen the hiturl URL ever be used.
Extended characters not displaying in the CVR Toast message.
All extended characters in the text of optional CVR toasts were either not displaying at all, or displaying as gibberish. In particular, users with Simplified Chinese, Traditional Chinese, Japanese, Korean, Russian, Greek, Arabic and Hebrew clients in were receiving toasts that looked much more like viruses than they did encouragements to upgrade to v7.813!
Fix issues with Login reporting
Our data collection was telling us that users were experiencing far fewer successful logins to the v7 client than they did to the v6.2 client. That’s not good. Also not good was the fact that the data that was being reported was not specific enough to help us figure out why so many failed logins were apparently occurring. We added new datapoints to help us get more granular information about what is really going on with logins.
Hopefully this login reporting change will help improve things for many users in the long run.
0 Response to “Changes in MSN Messenger 7.0.816”