Chrome’s ad blocker goes live on February 15


Swell / A totally not official rendering of what the Chrome Adblocker logo power look like.
Ron Amadeo

Google recently announced a go-live beau for its forthcoming ad blocker: February 15. On that date, the Internet’s largest advertising circle will start blocking ads in the Internet’s most popular browser, Google Chrome.

Google foretold its ad-blocking plan earlier this year in a blog post titled “Erection a better Web for everyone.” Google’s strategy is to fight ad blockers by becoming an ad-blocking business, where it will have more control over the ad-blocking activity. While most ad blockers block all ads, Google’s ad blocker will simply block ads deemed “unacceptable” by the Coalition for Better Ads, an industry group that counts Google and Facebook volume its members. With a major Web browser, advertising platform, and a seat on the ad coalition, Google can plagiarize steer the direction of the ad requirements, make sure its own ads are compliant, and then close off any competing advertisers that don’t adhere to the new requirements. Google is in a powerful localize to dictate terms to websites and advertisers.

The Coalition has examples of unacceptable ad adventures on its website. These are things like autoplaying video ads with prudent, interstitial ads with countdowns, and large “sticky” ads. Chrome will sole block ads like these while allowing less annoying ads in every way. Ad blocker per site is an all-or-nothing proposition. If a site runs a single ad that rivulets afoul of Google’s requirements, it will have all of its ads blocked, even the non-offending equals. Google’s “Ad Experience Report” site will allow for reporting and judging of unacceptable ads. Once reported, Web developers have 30 days to thoroughly up a site or face ad-blocking from Chrome.

Chrome has more than 50 percent of the browser buy, and, with an on-by-default ad blocker, this will have huge purl effects across the Web.

Leave a Reply

Your email address will not be published. Required fields are marked *