Platform Overview
This page introduces ADBNK's core concepts, account model, and the full data flow of an ad from request to settlement.
Core concepts
On the advertiser side, serving objects are organized hierarchically, refined from top to bottom:
On the publisher side, it's sites and ad zones:
| Concept | Belongs to | Description |
|---|---|---|
| Campaign | Advertiser | The top-level serving unit. Carries the pricing model, bid, daily/total budget, serving dates, targeting, and rotation mode. |
| Ad | Advertiser | The actual serving unit. Each ad has its own landing page, copy, and bid (uses the campaign's default bid when empty). |
| Creative | Advertiser | Pure media assets (image/video/HTML), reusable across multiple ads. An ad can also rotate multiple creatives. |
| Site | Publisher | One of your websites or apps; must pass review. |
| Zone | Publisher | An ad slot on a site's page. Determines the ad format and size served in that spot, and has a unique zone_key. |
Pricing and bids
The campaign sets the pricing model, and every ad in it uses the same one. Each ad can have its own bid; if left empty, the campaign's default bid is used.
Pricing models
| Model | Billed on | Best for |
|---|---|---|
| CPC | Per click | Performance ads, traffic acquisition |
| CPM | Per thousand impressions | Brand exposure |
| CPV | Per view | Video ads |
Account model
The platform serves two account types, each logging in to a different console:
| Role | Console | What you can do |
|---|---|---|
| Advertiser | advertiser.adbnk.co | Top up, build campaigns/ads, upload creatives, target and serve, view spend and performance |
| Publisher | pub.adbnk.co | Build sites, open zones, get embed code, view revenue, withdraw |
An advertiser account holds a balance (spend is deducted from it); a publisher account holds a withdrawable balance and a pending balance.
Data flow: from request to settlement
An ad goes through the following stages from request to final settlement:
- Ad request — a visitor opens a publisher page, and the ad zone requests an ad from the platform.
- Match & serve — among all approved, actively serving, and targeting-matched ads, the platform runs an auction and returns the best-fit ad to display (an Impression).
- Click — the visitor clicks the ad and is redirected to the advertiser's landing page. The platform records the click and can append tracking macros (
{click_id},{country}, etc.). - Conversion — the visitor completes a target action (purchase, sign-up, etc.) on the landing page, reported back via Pixel / JS SDK / S2S Postback. See Conversion Tracking.
- Traffic quality — invalid traffic is filtered out and not billed. See Traffic Quality.
- Settlement — valid traffic is billed and credited to the publisher; invalid traffic is not billed. The settlement statement is final. See Settlement & Payouts.
Reported data ≠ settled data
Console performance data is near real-time; your balance follows the settlement statement, so small differences are normal.