- The ad catalog is compiled server-side at Brave, based on advertiser inputs from the self-service ad server.
- Advertisers set up their campaigns and contextual and interest-based targeting options similar to how they would in DoubleClick or other ad servers.
- The ad server will organize and compile the available inventory into the ad inventory catalog (server-side).
- The ad inventory catalog will consist of edge-cached URLs for every ad opportunity available, and will be broken out per region.
- The catalogs are pushed to the devices by geo-region on a recurring basis.
- On the device, the integrated ad platform will locally match the right ad from the ad catalog to the right opportunity at the right time, based on the local data, intent signals and search/browsing history.
- This matching is done on the client side, without calling the cloud (as opposed to the existing ad model, which relies on calling servers from the client and passing data for cloud-based matching for virtually every 3rd party ad impression).
- As each user has the ad serving platform and the inventory catalog hosted directly on their own device, this means that each user has a complete, secure ad server on their device.
- Furthermore, the data used for the matching is on your device, and is matched locally on the device, so there is no need to leak the data about the user to any third party
- This means that under Brave, the user is insulated from third parties.