LightBlog

vendredi 2 juin 2017

Chrome Will Start Blocking Ads in 2018 on Sites Not Compliant with the Better Ads Standards

As society is moving toward a mobile-first world, more and more companies are trying to improve the user experience when it comes to browsing on a mobile device. Facebook worked on this with Instant Articles, Google has been rolling out their AMP project and then there’s Apple News specifically for iOS users. We’re even starting to see mobile web browsers building in ad-blocking technology into their browsers and enabling the feature by default.

A couple of months ago a report was published which claimed Google was even starting to build in ad-blocking technology into Chrome. Some ignored the report because Google is making billions from online advertising and to them it just didn’t make sense. However, this week the company has announced they have plans to start blocking ads in Chrome sometime in early 2018. Interestingly enough, this is actually a move that could make Google more money in the long run.

Google recognizes there are a number of people using ad-blocking software don’t actually want to block ads on every single website they visit. What tends to happen though, is there being a few websites out there which are implementing ads in such an annoying way that the person gets fed up and installs an ad blocker. This results in the person blocking ads on all the websites they visit and Google feels there is a better solution to the whole thing.

They feel that if annoying ads are stopped from the start, then the person won’t go out and seek solutions to the issue. So they’ve partnered with an industry group dedicated to improving online ads called Coalition for Better Ads. The group recently announced a Better Ads Standard that provides data on the types of ads people are truly fed up with. So, in early 2018, Google’s Chrome browser will start blocking ads site-wide on websites which are not compliant with the Better Ads Standard.

Source: The Keyword



from xda-developers http://ift.tt/2sxIrtY
via IFTTT

Aucun commentaire:

Enregistrer un commentaire