How-to guide
How to Choose Which Turns Show Ads in Flowise
This guide shows how to choose which turns show ads in a Flowise 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 Flowise produces and streams responses.
Overview
Not every turn in a Flowise 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.
Flowise apps are usually built for visual chatbot building, no-code RAG, and prototyping agent flows, 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 Flowise
Flowise runs on Node, so the Monetzly SDK can live in the layer that consumes a flow's prediction stream. Call the Flowise prediction API with streaming enabled, adapt its SSE token events to { content }, and pass them through sdk.inject() before relaying to your users. Confirm the streaming response shape for your Flowise version / deployment.
Because Monetzly's inject() accepts any async token stream, the Flowise side of this task is just mapping your output to it, no rewrite of your Flowise model call.
Steps
- Decide your policy: which Flowise 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.