What session id should I use in Flask?

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

Is passing the prompt required for Flask?

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 Flask

This guide shows how to pass session context to ads in a Flask 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 Flask produces and streams responses.

Overview

Ad relevance in a Flask 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.

Flask apps are usually built for simple LLM web apps, chat endpoints, and prototype APIs, 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 Flask

Same as FastAPI: no Python SDK, so integrate via the shipped tps_alter.proto gRPC service (generate stubs, drive ProcessStream) or a Node sidecar. In Flask, stream the injected tokens back with a generator response. Confirm the non-JS auth handshake before publishing.

Since Flask 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 Flask 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: Flask uses the gRPC proto path, confirm the auth handshake with Monetzly before relying on this in production.

# Generate stubs once from tps_alter.proto (shipped in @monetzly/server-sdk):
#   python -m grpc_tools.protoc -I. --python_out=. --grpc_python_out=. tps_alter.proto
# Then drive TPSAlterService.ProcessStream: StartRequest -> TokenRequest* -> StopRequest,
# reading back injected TokenResponses. See the FastAPI page for the full bidi loop.
# In Flask, yield the injected tokens from a streaming Response.
# TODO_VERIFY: auth handshake (API key placement) for a direct gRPC client.