> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adxensor.com/llms.txt
> Use this file to discover all available pages before exploring further.
# How AdXensor Works
> From a single ad request to money in your wallet — the complete lifecycle of an AdXensor impression, and where you can influence it.
Every time a visitor loads a page on your site, AdXensor runs a real-time decision in a few milliseconds: **which ad — if any — should fill this slot right now, for this exact visitor?** This page is the map of that decision. The pages that follow zoom into each stage and show you the levers you control.
**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
```mermaid theme={null}
sequenceDiagram
participant V as Visitor's Browser
participant SDK as AdXensor SDK
participant Core as core.adxensor.com
participant Wallet as Your Wallet
V->>SDK: Page loads, slot found
SDK->>Core: GET /v1/ad?zone=SIZE&site=ID
Note over Core: 1. Filter bots & invalid traffic
Note over Core: 2. Resolve country (IP) + device (User-Agent)
Note over Core: 3. Match campaigns + frequency cap
Note over Core: 4. Run revenue auction
Core-->>SDK: Winning creative + tracking token
SDK-->>V: Ad rendered
V->>Core: Impression beacon (ad visible)
Note over Core: Verify → count → charge advertiser
V->>Core: Click (optional)
Core-->>V: Redirect to advertiser
Note over Core,Wallet: Nightly: valid events → your earnings
```
## The six stages
The SDK finds each `` 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.
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](/publishers/how-it-works/ad-selection)
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](/publishers/how-it-works/ad-selection)
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**.
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](/publishers/how-it-works/traffic-quality)
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](/publishers/how-it-works/earnings)
## What the platform guarantees you
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.
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.
A rendered impression is counted **once** and billed **once**, even though multiple beacons may fire — kept in lock-step by shared per-token guards.
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.
## Where you have influence
You don't control which advertiser wins any single auction — but you control the **inputs** that decide how much demand reaches your slots and how much each impression is worth.
| What you control | Why it matters | Deep dive |
| ------------------------- | --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| **Ad sizes & placements** | More supported sizes = more eligible campaigns competing for the slot | [Ad Receiving Strategy](/publishers/how-it-works/ad-selection) |
| **Traffic quality** | Invalid traffic is never paid and directly lowers your reputation | [Traffic Quality & Scoring](/publishers/how-it-works/traffic-quality) |
| **Reputation score** | Higher reputation increases how much your inventory is valued when advertisers plan campaigns | [Traffic Quality & Scoring](/publishers/how-it-works/traffic-quality) |
| **Payout tier** | Determines your earnings hold and minimum payout | [Earnings & Payouts](/publishers/how-it-works/earnings) |
| **Integration hygiene** | If the impression beacon doesn't fire, you don't get counted or paid | [Optimization Playbook](/publishers/how-it-works/optimization) |
New here? Read these four pages in order — Ad Receiving Strategy → Traffic Quality & Scoring → Earnings & Payouts → the **[Optimization Playbook](/publishers/how-it-works/optimization)**, which turns everything above into a concrete checklist. Keep the **[Glossary & Key Metrics](/publishers/how-it-works/glossary)** open in a second tab for every term and threshold in one place.