I updated Brave and now I saw many ads but the number of ads is not increased

Brave Rewards Brave-Ads Support
1
  • Brave version: Brave 1.92.134 (Official Build) (arm64)
  • Brave Rewards Profile currently connected to a custodian.
  • I have been able to successfully receive payments in the past.
  • I have never used a VPN on Brave browser.
  • I am in a supported region.
2

@Acerola_Cherry

Please DO NOT share any personal/vital info here. I am posting this reply, only in order for you to investigate on your own - to study, prior to when Brave Support may show up (probably after the weekend).

According to Brave Search (Answer with AI):

The brave://rewards-internals/ page provides a detailed technical log of the Brave Rewards system, allowing users to diagnose why specific ads are not contributing to their BAT balance. By navigating to this page, a user can inspect several critical data points that explain discrepancies between ads viewed and rewards earned.

Key Information Revealed

  • Ad Logs and Status: The Logs tab displays verbose entries for every ad attempt. Users can identify why an ad was not served or counted by looking for specific error messages, such as “Notifications not allowed” or “Ad notification not served: Not allowed due to permission rules.” This indicates that system-level notification permissions or internal Brave flags are blocking the ad.

  • Wallet and Payment ID Status: The page displays the user’s Rewards Payment ID, which is essential for tracking earnings. It also reveals if the wallet has been created; a message stating “The wallet has not yet been created” suggests a synchronization issue or that the user has not completed the necessary setup to receive rewards.

  • Ad View Counts: Users can see the raw count of ads viewed versus those that actually generated BAT. Recent updates distinguish between connected users (where ads with 0.0 BAT value are excluded from the count) and non-connected users (who may see a full count regardless of value).

  • Verbose Logging: If the logs appear empty, users can enable verbose logging via brave://flags by setting “Enable Brave Rewards verbose logging” to Enabled. This is crucial for seeing detailed permission rule failures, such as issues with allow_notifications or custom ad notifications flags.

Common Diagnostic Findings

  1. Permission Issues: Logs often reveal that ads are blocked because notifications are not allowed in the browser or OS settings.

  2. Flag Conflicts: Incompatibilities between enabled options in brave://flags can cause ads to appear without counting. Resetting flags to standard often resolves this.

  3. House Ads: The system may display “house ads” (promotions for Brave itself) which pay 0 BAT and do not increase the rewards counter, even if they appear in the ad history.

  4. View Limits: If a user has reached the maximum number of paid ads for their OS and region, they will predominantly see non-paying house ads, which are visible but not counted.

Actionable Steps

  • Check the Logs tab for specific error codes related to permissions or flags.

  • Ensure Rewards Payment ID is present and the wallet is created.

  • Enable verbose logging in brave://flags if logs are empty.

  • Verify that system notifications and custom ad notifications are enabled in brave://flags and OS settings.

  • Reset brave://flags to default if flag conflicts are suspected.

(AI-generated answer. Please verify critical facts.)