Publisher Onboarding: What Networks Check Before You Go Live
Every serious ad network reviews publishers before paying them, and every rejection feels arbitrary from the outside. From the inside, the checks are predictable — networks are pricing risk, and risk has a short list of sources. Here is what gets reviewed, why, and how to arrive prepared.
Why the review exists
A network's product is trust: advertisers pay for human attention, and the network stakes its rates on that attention being real. One publisher sending emulator traffic through the exchange costs every other publisher on it, because advertisers reprice the whole supply on the evidence of its worst placements. The review is not gatekeeping for its own sake — it is how honest publishers' rates stay high.
Understanding this reframes the process. The reviewer is not looking for reasons to reject you; they are looking for evidence that your traffic is what you say it is. Everything below is a way of supplying that evidence. Publishers who arrive prepared — with numbers, store links and straight answers — typically clear review in days. Publishers who improvise their way through the same questions stretch it into weeks or quietly disappear from the queue.
Have your inventory story ready
The first questions are always the same: what is the app or traffic source, where does the audience come from, and how did it get there? For apps, this means store links, category, GEO mix, daily active users and session structure. For traffic networks and arbitrage operations, it means acquisition channels, formats and volumes per GEO.
Vague answers are the most common reason applications stall. 'Users find us organically' tells a reviewer nothing; 'sixty percent of installs come from tier-2 search ads into a puzzle game with four-minute average sessions' tells them exactly what they need. Pull the numbers from your analytics before you apply. Precision reads as legitimacy because it usually is.
Technical readiness
Reviewers check that integration is feasible before they check anything else. For app publishers this means knowing your stack: platform (iOS, Android, both), how the app is built, and whether an SDK integration is possible on your release cycle. For networks and DSP/SSP operations, it means your integration method — API, S2S, tags — and your capacity for passing the parameters measurement depends on.
Have your tracking story straight as well: how you measure your own traffic, and how you would pass postbacks or event data. You do not need to be an engineer to apply — but someone who can answer technical questions within a day needs to exist. Onboarding moves at the speed of the slowest answer.
Quality standards you will be held to
Approval is the start of measurement, not the end. Know the standards before you sign: invalid traffic is filtered and unpaid, and the definition includes emulator traffic, click farms, incentivized abuse beyond declared reward mechanics, and misrepresented GEOs. Reputable networks enforce this at placement level and share the evidence; if a partner will not tell you what their filters look for, ask harder questions.
Prepare your own quality hygiene in parallel: block accidental-click placements, keep your acquisition sources documented, and monitor your own invalid traffic rate so no report surprises you. Publishers who arrive with clean traffic and their own monitoring rarely have disputes — and when numbers are questioned, they have the data to resolve it in one email.
Commercial terms to clarify upfront
Before integration work starts, pin down the terms that otherwise surface as friction later: payout schedule and thresholds, the currency and method of payment, the reporting you will see (per-placement? per-GEO? daily?), and what happens to earnings in a dispute window. None of these are exotic requests — networks that work with professional publishers answer them routinely.
Also clarify demand-side protections you control: category blocks for ads that do not fit your audience, frequency policy, and the escalation path when a bad creative reaches your users. The answers tell you whether the network thinks of you as supply or as a partner. One more question worth asking early: who is your contact after onboarding — a named manager or a ticket queue. When a payment or fill issue appears mid-quarter, that answer decides whether it is resolved in hours or weeks. If you are ready to apply, our publisher registration takes minutes — the review conversation after it takes this checklist as its agenda.