How-to guide
How to Choose Which Turns Show Ads in Chainlit
This guide shows how to choose which turns show ads in a Chainlit app, the goal being to control ad placement and frequency across a conversation. It builds on the Monetzly gRPC service (no Python SDK exists for this stack), so the approach is specific to how Chainlit produces and streams responses.
Overview
Not every turn in a Chainlit conversation should carry an ad. Placement and frequency shape both revenue and user experience: too many ads erodes trust, too few leaves revenue on the table.
You control this by deciding which responses you route through injection — for example, skipping very short replies or the first turn, and allowing ads on substantive answers where a recommendation is genuinely useful.
Chainlit apps are usually built for chat UIs for LLM apps, agent demos, and RAG chat frontends, so choose which turns show ads typically comes up while a user is mid-conversation, the moment where monetization has to be additive rather than disruptive.
How this works on Chainlit
Chainlit is Python. Drive the shipped tps_alter.proto gRPC service (or a Node sidecar) and stream injected tokens into a Chainlit Message via msg.stream_token(). Confirm the non-JS auth handshake before publishing.
Since Chainlit is a Python stack with no official SDK, this task runs through the shipped tps_alter.proto gRPC service (or a Node sidecar); the auth handshake for a direct client is still TODO_VERIFY.
Steps
- Decide your policy: which Chainlit turns are ad-eligible (e.g. skip trivial or first replies).
- Route only eligible turns through the injection call.
- Measure revenue and engagement, then adjust frequency.
Frequently asked questions
Start monetizing in about 5 minutes
Wrap your existing LLM response stream with the Monetzly SDK and earn on every session, no paywall required.