14 DAY TRIAL // News broke a few days ago about an issue with Google AdMob for Windows Phone, which dropped fill rates and ad revenues for developers.
The issues suspiciously started to affect Windows Phone developers soon after Microsoft's BUILD 2015 conference.
During the event, Microsoft announced that Android support would be implemented in Windows 10 Mobile. In addition, the Redmond-based company announced two projects that will allow iOS and Android developers to port their apps on Windows Phone much easier.
Many Windows Phone developers took it to Google's forums to express their frustrations about the massive drop in fill rate and ad revenue, but they did not receive any answers from the search giant.
“My CPM rates and CPC reduced starting on 7/5, really is this error from admob? I am very confused because my revenue dropped more than 50% :(,“ said one developer.
Another developer confirmed the problem, as well as the date when his revenues started to fall: “Same here, the fill rate now is kissing the floor. 99% to 7% in one day, also starting on 7/5 (yesterday). May be a bug on AdMob network (or a Google conspiracy).”
It's not a conspiracy, but a major bug affecting AdMob for Windows Phone
It turns out that Google is not trying to kill Windows Phone platform by hurting those who develop apps for Microsoft's operating system. Or at least that's what the company claims in its latest tweet.
According to Google AdMob, the company is already aware of the fill rate issues for Windows Phone and they are now actively investigating and working to fix them.
So this seems to be a bug in the AdMob network which happened to affect Windows Phone developers right after Microsoft's BUILD 2015 conference.
Google promised to share more details on the matter soon, but that sounds more like PR. They will probably send another tweet when things are fixed. Hopefully, that will happen sooner rather than later.
We're aware of fill rate issues for Windows Phone in AdMob. We're actively investigating and working to fix this, more details soon.
— Google AdMob (@admob) May 18, 2015