Skip to main content

Google Chrome policy update restricts shady affiliate extensions, like Honey

Google Chrome has made a policy update today that restricts how browser extensions can interact with affiliate codes, effectively banning the behavior of the controversial PayPal Honey extension.

On the Chrome for Developers website, Google has made an update today which changes how extensions are able to interact with affiliate codes within the browser. Specifically, Google says (via Artem Russakovskii) that extensions cannot add “affiliate links, codes, or cookies” without “direct and transparent user benefit.”

Google explains:

Affiliate links, codes, or cookies must only be included when the extension provides a direct and transparent user benefit related to the extension’s core functionality. It is not permitted to inject affiliate links without related user action and without providing a tangible benefit to users. Some common violations include:

  1. Inserting affiliate links when no discount, cashback, or donation is provided.
  2. An extension that continuously injects affiliate links in the background without related user action.

    This directly targets the behavior of PayPal’s Honey extension, which was exposed last year for hijacking affiliate codes if users interacted with the extension in any form whatsoever. Honey uses affiliate codes to subsidize its service of collecting coupon codes (which it was also exposed for not doing as promised), but the extension was caught inserting its affiliate code – and preventing others from working – even if the user didn’t apply a code from Honey. Even if users simply clicked on a button to close Honey, the extension was caught inserting its affiliate at that time.

    Advertisement - scroll for more content

    Google’s new policy directly bans this practice.

    The policy update goes on to explain that extensions that inject affiliates must do so following “related user action,” again effectively targeting Honey’s practices.

    Related user action is required before the inclusion of each affiliate code, link, or cookie. Some example violations include:

    1. An extension that updates a shopping-related cookie without the user’s knowledge while the user is browsing shopping sites.
    2. An extension that appends an affiliate code to the URL or replaces an existing affiliate code in the URL without the user’s explicit knowledge or related user action.
    3. An extension that applies or replaces affiliate promo codes without the user’s explicit knowledge or related user action.

    Extensions are also required to disclose the use of affiliate programs in their Chrome Web Store listing. Many extensions like Honey have used affiliates behind the scenes for years, but didn’t directly disclose that behavior. That led to backlash that partially overshadowed Honey’s main problems, such as taking over codes without any actual referral as mentioned, as well as working with businesses to limit the number of coupon codes shown through the extension.

      Honey is still available in the Chrome Web Store as of today and has over 17,000,000 users, down from 18,000,000 earlier this year. When a YouTube video first exposed the extensions tactics, Honey lost around 3,000,000 users.

      More on Chrome:

      Follow Ben: Twitter/XThreads, Bluesky, and Instagram

      FTC: We use income earning auto affiliate links. More.

      You’re reading NewGeekGuide — experts who break news about Google and its surrounding ecosystem, day after day. Be sure to check out our homepage for all the latest news, and follow NewGeekGuide on Twitter, Facebook, and LinkedIn to stay in the loop. Don’t know where to start? Check out our exclusive stories, reviews, how-tos, and subscribe to our YouTube channel

      Comments

      Author

      Avatar for Ben Schoon Ben Schoon

      Ben is a Senior Editor for NewGeekGuide.

      Find him on Twitter @NexusBen. Send tips to schoon@9to5g.com or encrypted to benschoon@protonmail.com.