Configure in the dashboard
Start with allowed surfaces, blocked industries, and a sandbox placement scoped to one AI feature.
In-product AI features
Monetize embedded AI without disrupting your product.
Add sponsored moments to AI sidebars, smart compose, and inline assistants while keeping the user's documents, tasks, and workflow output untouched.
Surface rule
The AI feature can be sponsored. The user's work product cannot.
Visual sponsored moments stay labeled, separate, and controlled by your app.
The sponsored moment
Where ads fit within embedded AI features.
Embedded AI lives inside bounded product surfaces. That makes it possible to sponsor the AI feature without turning the user's core work into an ad surface.
AI sidebar
Assistant panel
Smart compose footer
Inline assistant container
Result companion panel
Workflow sidebar
Place the sponsored unit inside the AI container or companion panel, not inside the user's document, task, or saved record.
The product boundary
The AI feature can be sponsored. The user's work product cannot.
See the shared delivery flowRecommended setup
Sidebar, composer footer, assistant panel, or companion card
Begin with one visual slot, one timing rule and clear disclosure. Keep sensitive product data out of the partner ad request.
Best placementSidebar, composer footer, assistant panel, or companion card
Best formatNative Ad with compact banner fallback
Best timingDuring generation, after response completion, or in an assistant panel state
Default signalProduct area, broad topic, locale, consent state
Data boundaryNo sponsor metadata enters user documents, prompts, or model context
Recommended first testAdd a native sponsored card inside the AI assistant panel
Why this surface works
- Embedded AI features already sit in bounded UI containers that product teams can control.
- Teams can isolate sponsorship to free, trial, or non-sensitive product moments.
- The core SaaS workflow stays intact because the sponsor never becomes part of the work product.
What stays untouched
- User documents
- Smart compose text
- Generated content
- Product database records
- Prompt and model context
- Core workflow state
Placement judgment
Good placements versus avoid.
The difference is whether the sponsor is clearly outside the AI output and easy for the user to understand.
Good
- Sponsor card in an AI sidebar after a response.
- Compact banner in an assistant panel footer.
- Sponsored resource beside an AI-generated summary.
Avoid
- Sponsored text inserted into a user's document.
- Sponsor metadata added to smart compose output.
- Ads inside mission-critical or sensitive workflow states.
Implementation path
Server-side match, client-side render.
The product keeps orchestration and policy control. wavebird returns a placement decision, then the hosted renderer handles media and beacons.
Developer API path
Bind placement requests to the product area and render only inside the assistant panel or companion shell.
Server-side matching
Send product area, broad topic, locale, consent, and format controls without forwarding documents or model context.
Client-side rendering
Mount the sponsored card in the AI panel and use fallbacks so the product flow never depends on fill.
Controls
Decide where sponsorship is allowed.
Your app controls eligible surfaces, allowed formats and categories, placement timing and fallback behavior. These choices remain subject to wavebird's consent and safety checks, partner rules and required ad labeling.
Eligible product areas
AI panel surfaces
Format defaults
Blocked industries
Relevance rules
Label text
Sensitive workflow opt-out
Operator kill switch
Related surfaces
Similar visible AI moments.
Sponsor the AI feature, not the product data.
Start with one assistant panel and keep every document, task, and workflow record outside the sponsor path.