The one-sentence model. Your ad slots are supply. Advertiser campaigns are demand. AdXensor is the real-time exchange in the middle that matches the two, protects both sides from fraud, and splits the revenue — defaulting 60% to you.
The lifecycle of one impression
The six stages
Request
The SDK finds each
<ins class="adxensor"> slot and asks the core server for an ad, passing only the ad size (zone) and your Site ID. Country is resolved server-side from the visitor’s IP, and device type from the browser’s User-Agent — no personal data leaves the browser.Match
The server intersects live campaign pools by country, device, ad size, and language, then checks creative-availability, budget, and flight window. Only campaigns that can actually serve this visitor survive. → Ad Receiving Strategy
Auction
Surviving campaigns compete in a weighted-random revenue auction. Better-funded, higher-value ads win more often — but budget pacing is preserved so no single campaign starves the rest. → Ad Receiving Strategy
Serve
The winner’s creative is returned with a one-time tracking token. If no paid campaign qualifies, a house ad or built-in banner fills the slot instead — so your inventory is essentially never blank.
Measure
When the ad renders, an impression beacon fires. Every event passes through the invalid-traffic (IVT) shield: bots are recorded but never counted, never charged, never paid. → Traffic Quality & Scoring
Credit
A nightly job aggregates the day’s valid impressions and clicks, computes revenue, applies your revenue share, and credits your wallet — with a 3-day self-healing window so no day is ever lost. → Earnings & Payouts
What the platform guarantees you
Slots almost never go blank
When house fill is enabled, a house creative or an always-fill banner covers the slot for standard ad sizes — and house fills still earn you 50% of the house CPM. Only a non-standard size with no house creative can return empty.
Fraud never costs you
Bot and invalid traffic is filtered on four separate paths. Flagged traffic is preserved for your reports but excluded from every count, charge, and payout.
No double-counting
A rendered impression is counted once and billed once, even though multiple beacons may fire — kept in lock-step by shared per-token guards.
Fair, paced demand
The auction weights by remaining budget × expected value, so demand is spread across the day instead of a few advertisers exhausting their budgets by noon.