Ads in Chrome Extensions: What the Chrome Web Store Allows and Prohibits
Short answer: you can show ads in a browser extension. What you cannot do is inject them into the websites users visit or push them through browser notifications. Here is what the Chrome Web Store rules actually say and how to avoid a takedown.
What the official policies say
The Chrome Web Store Program Policies include a dedicated Ads section. It does not ban ads — it sets requirements for them:
- ads are considered part of your product and are reviewed with it, so they must follow the same content policies
- ads must match your extension’s content rating
- ads must be shown in context or clearly state which product they are bundled with
- users must be able to remove ads by adjusting settings or uninstalling the extension
- ads must not imitate system notifications or warnings
- users must not be forced to click ads or submit personal information to use the extension
- AdSense may not be used to serve ads in extensions
- an extension whose primary purpose is serving ads violates the quality guidelines
Bottom line: ads are allowed when your extension solves its own problem and ads are an add-on, not the point of the product.
The allowed scenario
Your extension has a core function and shows ads inside its own interface, while the user is inside your product:
- in the popup that opens when users click the toolbar icon
- in the side panel
- on extension pages: the welcome page, options page, or a dedicated extension tab
This is also how participants in a Chromium extensions group discussion describe acceptable monetization: ads inside your own product are permitted by the store.
Prohibited scenarios
Ads on third-party websites
An extension with a core function also injects ads into the pages a user visits — via content scripts or iframes. This violates the Single Purpose Policy: the Quality Guidelines FAQ explicitly says ad injection cannot be bundled with other functionality. It is a violation even if your extension’s feature also runs on that page.
Ads through notifications
The Spam and Abuse policy prohibits abusing browser notifications to send spam, ads, promotions, or other unwanted messages.
At a glance
| Scenario | Allowed? | Rule |
|---|---|---|
| Banner in the popup, side panel, or extension page | yes | Ads section of the Program Policies |
| Ads injected into third-party websites | no | Single Purpose Policy |
| Ads in browser notifications | no | Spam and Abuse |
| An extension that exists only to serve ads | no | Quality Guidelines |
| Serving ads through AdSense | no | Ads section |
Other rules to keep in mind
- Affiliate links. Since June 2025, they are allowed only when they provide a direct and transparent benefit to users. The affiliate program must be disclosed on the store listing, in the interface, and before installation, and the link or cookie may be applied only after a user action (policy update).
- User data. If ads rely on any data, such as the user’s country detected from the IP, declare it in the Privacy tab of the developer dashboard and in your privacy policy.
How ExtAds follows these rules
ExtAds works only in the allowed scenario:
- the banner appears only inside the extension interface — in the popup, side panel, or extension page
- ads are never injected into third-party websites or sent as notifications
- publishers choose campaigns themselves, and every campaign is moderated — no gambling, betting, scams, or malicious offers
- the SDK uses the IP only to detect the user’s country; the IP is not stored or shared, and publishers declare Location in the Privacy tab
We tested banners for 2 months on 8 of our own extensions with a combined audience of over 70K WAU. There were no complaints and no takedowns.
Important: Chrome Web Store rules change, and the extension owner is responsible for compliance. Both parties are responsible for how ExtAds is used, so read the current policies before integrating.
See the terms on the For Publishers page, or message our manager on Telegram: @extads.