Skip to main content
During onboarding you receive two publisher tokens:
  • A development token ({publisher}-dev) for integration and testing. It returns Kontext’s test creatives for every format, never a live campaign, and has no usage limits: request, load and show as many ads as you need.
  • A production token that participates in the real auction and generates revenue.
Everything behaves the same with both: the same prices on the ad (test prices with the development token), the same no-fill reasons, the same events. When you are ready to ship, swap the token in Configuration and nothing else changes.

​
The example app

The example app has one video per format: open one and its ad shows a few seconds in, with the last delegate callback on screen. Running it with logLevel: .debug next to your own integration is the fastest way to see what differs.

​
Logging

Set logLevel: .debug in Configuration while integrating. Every request, ad, event and end reason is logged to the console. See Debugging.