Integration & Monetization
As a publisher, you integrate your website or app's ad slots into ADBNK at pub.adbnk.co and earn revenue by showing ads. The whole process has four steps: add a site → create a zone → grab the embed code → track revenue.
Flow overview
Step 1: Add a site
A site is one of your websites or apps. When creating one, submit:
| Field | Description |
|---|---|
| Site name | Required |
| Domain | Required for the web type; must be a valid, unclaimed domain |
| Type | Website, App or Telegram Mini App |
| Category / Content category | The site's category and its top-level content category, which decides the ads that can serve on it. Choosing an adult category marks the site as adult |
| Adult content | A toggle that marks the site as an adult site; it switches on automatically when you pick an adult category. Pick the real content category — ad slots on adult sites are flagged and only adult ads serve there |
| Description | Optional |

Pick the media type first (website / mobile app / Telegram Mini App) — a site belongs to exactly one platform type — then fill in the name, domain and category.
After submission the site enters PENDING review. For a web site, use Verify in the site list to prove you own the domain: deploy the verification credential using any one of the methods shown, then click Verify now.
For a Telegram Mini App site, enter the Mini App URL and the bot username instead of a domain; we look up the Bot ID for you. It is verified in three steps (domain, bot description, opening it once in Telegram) and then reviewed manually — passing verification does not approve the site on its own. See Telegram Mini App.
A site must be approved before opening zones
Only APPROVED sites can create and submit zones. Make sure you own the domain and the content is compliant.
Step 2: Create a zone
A zone is a specific ad slot on a site's page. Creating one takes three steps — Select type → Basic info → Advanced settings:
| Setting | Description |
|---|---|
| Site | Required; pick one of your approved sites. The site's media type decides which zone types you can choose |
| Zone type | The format served in this slot (Banner / Native / Video / Push / Popup, etc.), see Ad Formats. Each type has a preview |
| Zone name | Required |
| Zone size | Fluid (recommended) or a fixed size from a short list (e.g. 300×250), depending on the type. Fullscreen, video and push types size themselves and don't ask |
| Platform | Serving device: All (PC + Mobile) / PC / Mobile; pre-filled from the zone type, you can change it |
| Floor Price (eCPM) | Minimum revenue per 1,000 impressions, in $. Ads below the floor are not served; enter 0 for no floor |
The Advanced settings step covers options such as refresh interval, fallback content (shown when there's no ad), lazy loading and the close button. A zone's content orientation is inherited from its site's category, so there's nothing to set. You can label a zone's on-page position later, when editing it.
Each zone automatically gets a unique zone_key, the identifier used to grab embed code and serve ads.
One floor price, in eCPM
You don't pick a billing model — advertisers do (CPC / CPM / CPA / CPV). Every bid is converted to eCPM (expected revenue per 1,000 impressions) before the auction, so a single eCPM floor is all you need. Setting a reasonable floor filters out ads that bid too low and protects the revenue quality of your traffic.
Step 3: Get the embed code
When you finish creating a zone, the success page shows its embed code right away if the zone is approved; otherwise it tells you the code becomes available once the site or zone is approved. You can always get the code later from the zone list. Pick a tab and paste the code into the right spot on your page:
| Method | Traits |
|---|---|
| JavaScript (recommended) | Loads asynchronously, non-blocking, supports auto-fit |
| Async Loader | Good for multiple zones on one page |
| iFrame | Best compatibility, but not responsive |
Video zones also offer VAST / VMAP tags for your video player.
Telegram Mini App zones offer a tag snippet (banner, native, floating) or a programmatic snippet (rewarded, interstitial) instead of the methods above — see Telegram Mini App.
JavaScript example (data-zone-id is your zone_key):
<ins class="adsbyadbnk" data-zone-id="your-zone-id"
style="display:inline-block;width:300px;height:250px"></ins>
<script src="https://js.adbnk.co/sdk.js" async></script>Unapproved zones can't get code
A zone must be APPROVED to get embed code, preventing unreviewed slots from going live early. For more JS integration usage, see SDK Docs.
Step 4: Track revenue and withdraw
Once the code is live, ads start showing and revenue accrues:
- The console lets you view impressions, clicks, CTR, and revenue by site/zone (a near real-time estimate refreshed every few minutes).

Statistics reports estimated earnings, ad requests, coverage (fill rate), impressions, clicks, CTR and eCPM for a date range. Group rows by day, hour, site, zone, ad format, country, device, OS or browser, add up to four breakdowns, filter, compare against a previous period, and export to CSV or Excel.
- The platform settles at a revenue-share ratio (70% to the publisher by default). Revenue first enters "pending" and becomes withdrawable once the hold period ends.
- Once you meet the minimum withdrawal amount, you can request a payout.

Finance → Withdraw shows your withdrawable balance and the minimum payout amount; pick a payment method, fill in the receiving account, and submit the request.
Settlement rules, revenue share, hold period, and payout methods are detailed in Settlement & Payouts. To earn extra rewards via invitations, see Referral Program.
Zone review status
| Status | Meaning |
|---|---|
DRAFT / not submitted | Created but not submitted for review |
PENDING | Submitted, awaiting review |
APPROVED | Can get code and go live; can toggle enabled/paused |
REJECTED | Not approved, with a reason; resubmit after fixing |