Skip to content

🧭 Quick Start

Welcome to AWAvenue Ads Rule. This page helps you decide whether it fits your setup and builds the right subscription through three choices.

Finish in three steps

  1. Choose the tool or format that will import the rules.
  2. Decide whether to block privacy telemetry and unwanted network behavior.
  3. Copy a subscription from a mainland mirror, the official source, or a fallback route.

Choose your tool

Already know what you use? Open its subscription questionnaire directly. Your choice carries over to the next page.

Have not chosen a tool yet?
  • For direct use on a phone or computer, start by learning about AdGuard.
  • If you already use a proxy client, choose a format supported by that client.
  • For network-wide filtering, look at AdGuard Home, MosDNS, Dnsmasq, or RouterOS.
  • To modify the system hosts file, choose the hosts / AdAway format.

AWAvenue Ads Rule is not designed for accessibility auto-click tools or browser extensions such as AdGuard for Chrome.

Current release and visit counter

Current release

Loading…

Updated: Loading… UTC

View this release

Release data comes from GitHub. Try another network if it does not load.

Visit counter

Thanks for every visit

Counting since June 2024. The counter service may occasionally be unavailable.

AWAvenue Ads Rule website visit counter

What can AWAvenue Ads Rule do?

AWAvenue Ads Rule blocks advertising and related requests at the network layer. It does not require click rules for every app, and it balances hit rate, list size, and hardware overhead across many filtering tools.

It can help withIt cannot guarantee
Ad delivery, bidding, creative, and attribution requestsAds served from the same domain as normal content
Analytics, telemetry, crash reporting, and device fingerprintingRemoving empty spaces left in an app interface
Forced updates, P2P/PCDN, push, and remote configurationRewards that require watching an advertisement
Network-wide filtering across devices and routersEvery advertisement in every app and region

Four subscription profiles

The builder asks two plain-language questions instead of making you memorize technical filenames:

Display nameIncluded contentBest for
Full protectionAds + privacy + unwantedThe complete default experience
Ads onlyAdvertising onlyCompatibility and minimal intervention
Ads + unwantedNo privacy categoryKeeping analytics and telemetry
Ads + privacyNo unwanted categoryKeeping updates, push, and related connections

Before you subscribe

  1. AWAvenue Ads Rule does not account for rewards that require watching ads.
  2. Network filtering cannot remove interface elements, so some apps may leave empty spaces.
  3. Privacy or unwanted categories may affect a few analytics, update, or push features; the builder lets you choose.
  4. No filter list covers every advertising domain. False positives are especially important to report quickly.

Before subscribing

Read the User Protocol and Usage Guide. Results for AdGuard, Quantumult X, Shadowrocket, and Loon also link to their specific guides.

Why network-layer filtering?

FeatureNetwork filteringAccessibility clickingXposed Hook
Cross-platform and router useSupportedMainly AndroidMainly Android
Whether ad assets still downloadUsually noUsually yesDepends on implementation
Setup difficultyLowerLowestHigher, usually requires root
Ongoing app adaptationLowerMust follow interface changesMust follow code changes

These methods solve different problems and can be combined, but a filter subscription cannot be imported directly into an accessibility auto-click tool.

Need help?