◇
One SDK, every format
Request, render, done. A single integration covers banner through rewarded video — no per-format libraries to maintain.
For developers
Earn more from every app you build.
One lightweight SDK, five ad formats, and demand that has already passed review. You keep 70% of every verified impression and click, settled straight to your PEP wallet.
Free to join. No minimum traffic, no exclusivity.
70%Your share of every verified event
5Ad formats, one SDK
Real-timeEarnings per app & placement
0Charge-backs on invalid traffic
Monetization that respects your app — and your users
PEP Ads is the ecosystem's own network. Every advertiser is verified, every creative is reviewed, and every dollar is traceable from the impression to your wallet.
✓
Approved demand only
Every creative you serve has already passed ministry review. You will never wake up to a complaint about what ran in your app.
◈
Revenue you can reconcile
Earnings are booked per event, per placement, and reconciled against what the PEP economy actually settled to you.
⌁
Built for real networks
Lean payloads, cached decisions and CDN-hosted creatives — designed for the devices and bandwidth your users actually have.
High-performing ad formats
Register a placement, pick its format, and the serving engine matches it to eligible approved campaigns. Mix formats freely across one app.
Banner
A persistent inline strip that refreshes while the screen is open. The simplest placement to add and the steadiest earner on high-session apps.
Best for: utilities, news, everyday toolsInterstitial
A full-screen unit shown at natural breaks — between levels, after a task, on return to the home screen. Higher value per impression than banner.
Best for: games, step-based flowsRewarded video
Users choose to watch in exchange for something — an in-app item, or PEP Points from the reward pool. Completion is verified server-side before anything is paid.
Best for: games, content unlocks, free tiersNative
Creative rendered with your own layout and styling, so sponsored items sit inside your feed instead of on top of it.
Best for: feeds, marketplaces, cataloguesSurveys
Short partner-verified questionnaires. Nothing is billed — and nothing is paid — until the partner confirms the response was completed.
Best for: apps with engaged, returning usersOffers & app trials
Task-based inventory: install and open an app, complete a signup, make a first purchase. Confirmed by postback before the event counts.
Best for: discovery surfaces, reward hubsLive in four steps
From account to first impression without a sales call.
Create your developer account
Sign up and verify your email. Same account as the QubStore developer console.
Register your app
Add the app you want to monetize. Apps published in the QubStore are matched automatically to your catalog entry.
Create placements
Each slot in your app becomes a placement with a format. You get a placement ID to reference from the SDK.
Drop in the SDK
Request an ad, render it, and the SDK reports the impression and click for you. Earnings appear in your dashboard as events verify.
Quickstart SDK v1 · preview
Three calls to your first impression
The SDK owns the serving contract: it requests an eligible ad for your placement, renders the creative, and fires the tracking events. You never call the tracking API yourself, and old builds keep working — the contract is versioned.
- Impressions and clicks reported automatically
- Graceful no-fill — your layout stays intact when there is no eligible ad
- Signed payloads, so your inventory cannot be spoofed by someone else
import { PepAds } from '@pep/ads-sdk';
// 1. identify your app once, at startup
await PepAds.init({ appId: 'app_7f21c9', sdkVersion: 'v1' });
// 2. request an ad for a placement you registered
const ad = await PepAds.request({ placement: 'home_banner' });
// 3. render it — the impression is tracked for you
if (ad) PepAds.render(ad, '#ad-slot');
else showYourOwnFallback();
Revenue
70% of every verified event
Your share is booked the moment an event passes verification — priced off the advertiser's CPM or CPC bid for that creative, not an opaque blended rate.
- Booked per event, per placement — no monthly black box
- Settled into your PEP wallet by the economy service
- Reports reconciled against settlements; gaps flagged, never absorbed
- Spend it, transfer it, or cash out through the wallet's own rails
Reconciled to the cent
Invalid traffic is our problem, not your liability
Fraud filtering happens on our side of the SDK, before an event is ever worth anything — so you are not billed back months later for traffic you never controlled.
◈
Verified before it pays
Every event must match an ad we actually served to that placement, arrive in a plausible time window, and clear duplicate and velocity checks.
✓
Reviewed creatives only
Campaigns serve only after approval, and stay revocable. If a creative is pulled it stops serving in your app immediately.
⚑
Clear rules, stated up front
No incentivised clicking, no hidden or stacked placements, no ads on screens the user did not open. Break them and placements are paused, not silently zeroed.
Developer questions
What exactly do I earn?
70% of the advertiser's bid for each verified event on your placement — their CPM bid divided across a thousand impressions, or their CPC bid on a click. Because the split is applied per event, your reporting shows the exact amount every impression and click contributed.
When and how do I get paid?
Earnings settle into your PEP wallet through the economy service, which is the sole authority on balances. From there you can spend inside the ecosystem, transfer, or cash out through the wallet's own rails, subject to the KYC tier on your account.
Does my app have to be in the QubStore?
Placements have to belong to a registered, approved app — that is what stops someone claiming impressions from an app that does not exist. Publishing in the QubStore is the fastest route, and it matches your catalog entry automatically.
What happens to invalid traffic?
It is dropped before it becomes revenue for anyone. Events that fail served-record matching, dedup, or fraud scoring never reach the economy service — so nothing is clawed back from you later. Sustained invalid traffic from a placement gets the placement reviewed, and you will hear from us about it.
How much control do I have over what appears?
You choose the format and position of every placement, and all demand has passed ministry review before it can serve anywhere. Category-level blocking for individual apps is on the roadmap alongside advanced targeting.
Which platforms does the SDK support?
Android and web at v1, matching where the ecosystem ships first; iOS follows the store's own iOS timeline. The serving and tracking contract is versioned, so an old build in the field keeps working after we ship a new one.
Start earning from your app
Create a developer account, register your first placement, and put the SDK to work.