How-to guide
How to Choose Which Turns Show Ads in OpenAI Assistants API
This guide shows how to choose which turns show ads in a OpenAI Assistants API app, the goal being to control ad placement and frequency across a conversation. It builds on the Monetzly server SDK, so the approach is specific to how OpenAI Assistants API produces and streams responses.
Overview
Not every turn in a OpenAI Assistants API 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.
OpenAI Assistants API apps are usually built for hosted chat assistants, file-search agents, and tool-calling assistants, 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 OpenAI Assistants API
The Node OpenAI SDK streams run/completion events. Map each text delta event to { content: delta } and feed the generator into sdk.inject(). The Monetzly side is standard; the only framework detail to confirm is the exact delta event field for your chosen mode (Assistants run stream vs Chat Completions).
Because Monetzly's inject() accepts any async token stream, the OpenAI Assistants API side of this task is just mapping your output to it, no rewrite of your OpenAI Assistants API model call.
Steps
- Decide your policy: which OpenAI Assistants API 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.