AD NETWORK PARTNERS

One placement.
A clean protocol.

LoopBar accepts managed provider-supplied banner ads through a server-to-server HTTPS feed and is preparing its initial supply relationship with Numatec. Third-party scripts never run inside the browser extension.

Standard banner format

Loading placement: exactly 728×90 desktop (75 KB max) and 320×50 mobile (50 KB max).
Persistent right rail: exactly 160×600 desktop artwork, up to 150 KB.
PNG, JPEG, or WebP static images only—never executable ad code.
The artwork contains the advertiser logo, message, and call to action.
HTTPS destination URL and CPM supplied in USD micros.

Privacy-safe inventory

Requests identify the placement and creative limits only. LoopBar does not send AI prompts, AI responses, browsing history, readable account emails, or extension device identifiers to the ad provider.

Verified events

The loading placement needs 2.5 seconds of continuous 50% viewability; the right rail needs five seconds. Impression and click callbacks carry a unique provider event token and idempotency key so retries cannot create a second Wallet entry.

Safe provider connection

Public HTTPS ad-decision endpoint and bearer credential.
Public HTTPS impression callback and optional click callback.
Protocol 1.5 fixed-image creative response—never executable ad code.
Authenticated payable receipts must confirm the exact gross amount before network earnings enter a Wallet.
Test mode first, which reports events but creates no payable Wallet balance.
Written approval for cash-rewarded browser-extension inventory before live mode.

Open the machine-readable protocol →

Google is not the publisher connector

Google Ads is for buying ads. Google Ad Manager’s rewarded format requires affirmative opt-in and Google’s reward policy prohibits direct monetary rewards, so it is not compatible with LoopBar’s current cash Wallet. LoopBar instead exposes one provider-neutral server feed for a network that approves this inventory in writing.