What session id should I use in Chainlit?

Any stable identifier for the conversation — reuse your existing Chainlit session or thread id so turns are grouped correctly.

Is passing the prompt required for Chainlit?

It is optional but strongly recommended: the prompt is what makes the injected ad contextually relevant to the current turn.

How-to guide

How to Pass Session Context to Ads in Chainlit

This guide shows how to pass session context to ads in a Chainlit app, the goal being to supply session id, prompt, and metadata so injected ads are relevant. 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

Ad relevance in a Chainlit app comes from context. When you inject, you pass a session id, the live prompt, and optional metadata — that is what lets Monetzly match a recommendation to what the user is actually asking about in that turn.

The session id groups turns from the same conversation; the prompt drives per-turn relevance; metadata carries anything extra you want to target on. All are supplied per injection call.

Chainlit apps are usually built for chat UIs for LLM apps, agent demos, and RAG chat frontends, so pass session context to 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

Choose a stable session id for the conversation (reuse your Chainlit session or thread id).
Pass the current user prompt on each injection call.
Add optional metadata (topic, user type) to sharpen targeting.

Integration snippet

TODO_VERIFY: Chainlit uses the gRPC proto path, confirm the auth handshake with Monetzly before relying on this in production.

# No Python SDK. Generate stubs from tps_alter.proto and drive ProcessStream
# (see the FastAPI page for the full bidi loop), then in a Chainlit handler:
#
#   msg = cl.Message(content="")
#   async for token in inject(llm_tokens, prompt, session_id, api_key):
#       await msg.stream_token(token)
#   await msg.send()
#
# TODO_VERIFY: auth handshake (API key placement) for a direct gRPC client.