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

① Add a site (Site)     submit domain / app info, wait for review
② Create a zone (Zone)  pick format, size, floor price
③ Get the embed code    JS / async / iFrame, paste into your page
④ Track revenue & withdraw   hourly settlement, withdrawable after the hold period

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	WEB (website) or App and other media types
Category	The site's industry, to help match ads

After submission the site enters PENDING review. The web type automatically registers your domain (including *.domain wildcards) for origin validation during serving.

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. When creating one, set:

Setting	Description
Zone name	Required
Parent site	Required; must be an approved site
Ad format / type	The format served in this slot (Banner / Native / Video / Push / Popup, etc.), see Ad Formats
Size	The zone's width and height (e.g. 300×250)
Position / device	Layout position, serving device (All / PC / Mobile)
Billing type	Supported billing methods (e.g. CPC, CPM)
Floor price	CPC floor / CPM floor; ads below the floor are not served

You can also configure advanced options: refresh interval, fallback content (fallback HTML/image/redirect shown when there's no ad), lazy loading, close button and delay, and more.

Each zone automatically gets a unique zone_key, the identifier used to grab embed code and serve ads.

A floor price protects your revenue

Setting a reasonable CPC/CPM floor filters out ads that bid too low, protecting the revenue quality per unit of traffic.

Step 3: Get the embed code

Once the zone is approved, you can get three kinds of embed code. Pick one and paste it 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 no auto-fit

JavaScript example (data-zone-id is your zone_key):

<ins class="adsbyadbnk" data-zone-id="zone_xxxxxxxx"
     style="display:inline-block;width:300px;height:250px"></ins>
<script src="https://js.adbnk.co/js/sdk.js" async></script>

iFrame example:

<iframe src="https://ad.adbnk.co/ad/render/zone_xxxxxxxx"
        width="300" height="250" frameborder="0" scrolling="no"></iframe>

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 roughly every 5 minutes).
• The platform settles hourly 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.

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 admin
APPROVED	Can get code and go live; can toggle enabled/paused
REJECTED	Not approved, with a reason; resubmit after fixing