Page request
The publisher page loads an AdsZon zone asynchronously, including the registered zone identifier and available context.
The AdsZon serving path is intentionally understandable: validate the placement, find eligible demand, compare the economics, return approved creative and measure the result.
The publisher page loads an AdsZon zone asynchronously, including the registered zone identifier and available context.
The network checks the site, zone, actual browser Origin/Referer and campaign eligibility before spending an impression opportunity.
Targeting, delivery dates, budget pacing and expected eCPM determine which campaigns can compete and how they rank.
Only approved creative can render. HTML creative is isolated in a sandboxed iframe rather than injected into the publisher DOM.
Signed, deduplicated events record impressions, viewability and clicks. Aggregation then feeds site, zone, campaign and financial reporting.
The public page only needs the placement container and the asynchronous AdsZon script.
<div class="adszon" data-zone="AZ-Z0001" data-context="entertainment"> </div> <script async src="https://adszon.com/az.js"> </script>
Direct CPM demand already speaks in eCPM. CPC and affiliate demand are converted into expected eCPM using observed performance so the decision can be made on a common basis.
See how AdsZon handles fraud controls, privacy and supply transparency.