Work through this checklist before going live. Each item links to the relevant guide or concept page.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.
- Use the latest SDK version. We ship improvements — fill-rate fixes, new ad formats, performance, support for new DSPs and demand partners — on a steady cadence. Pin to the current major and update minors regularly. See Changelog.
- Pass every message through
addMessage. Every user message is a preload opportunity for the SDK to fetch an ad — passing all of them can significantly improve fill rate. When you want to mute a specific turn, usetrackOnly: truerather than skipping the call. See Messages. - Collect IFAs. IDFA on iOS, GAID on Android. Both improve retargeting, frequency capping, and revenue. See IFA & ATT.
- Host
ads.txt/app-ads.txtwith our authorization line, and keep it up to date. Whenever we add new demand partners or change our seller-domain, we’ll send you an updated line — append it promptly so new DSPs can actually bid on your traffic. See ads.txt. - Integrate a TCF v2.2 CMP for EU / UK traffic. Required by GDPR and dramatically improves fill rate — most DSPs won’t bid without a valid consent string. See TCF & CMP.
- Configure SKAdNetwork on iOS. DSPs running install campaigns rely on SKAN attribution to measure performance — without their identifiers in your
Info.plist, they have less data to bid aggressively on your traffic. See SKAdNetwork. - Let us pace it. We’ve seen what works across our network and tune cadence per publisher. Tell us during onboarding — no app-side rules needed. Per-message
trackOnlyremains available for finer control. See Pacing. - Work closely with us on ad design. Great ads come from collaboration — share your style, brand constraints, and any content red lines so we can tune the creative to feel native to your app. The best-performing ads are the ones users love. Reach out via Support any time.