Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kontext.so/llms.txt

Use this file to discover all available pages before exploring further.

​
Two sources of demand

Every ad that fills on your traffic comes from one of two sources our engine aggregates into a single auction per slot: Direct partners. Advertisers and ad networks we have direct relationships with. Their campaigns are pre-vetted by us, often run on negotiated pricing, and tend to have higher fill rate and tighter contextual relevance — we control the integration end-to-end. Demand-side platforms (DSPs). Programmatic demand. DSPs are the tools advertisers use to buy ad inventory at scale. We aggregate many DSPs into the same auction, adding breadth of demand, broader geo coverage, and competitive bidding. Both sources compete in the same auction per ad slot; the winning bid is what your user sees.

​
What this means for your integration

  • SKAdNetwork. Each DSP has its own SKAN identifier — list them all in Info.plist so DSPs can attribute installs. Direct partners don’t need extra SKAN IDs. See SKAdNetwork.
  • ads.txt / app-ads.txt. DSPs check this file before bidding; it must list our authorization line. See ads.txt.
  • Fill rate. Higher when more DSPs are eligible to bid on your traffic. We add demand sources over time — keep your config in sync (SKAN identifiers, ads.txt) so new partners can actually bid.
  • Geo coverage. Different DSPs serve different regions. If a region looks empty in your dashboard, it usually means we’re still working on demand for that geo.