Publisher integration overview
A publisher integration starts with one approved placement surface. Keep the first launch narrow: one app ID, one placement key, one visible sponsor container, and a clear no-placement state.
Setup sequence
01
Create publisher app
Confirm the app record, environment, and public app ID.
02
Register placement
Define the UI surface where a recommendation may appear.
03
Install SDK
Load the browser SDK or wire the placement API.
04
Verify events
Confirm impression and click events contain publisher, placement, and offer metadata.
Required configuration
| Field | Example | Required before launch |
|---|---|---|
| App ID | conv_dev_xxx |
Yes |
| API base URL | https://api.dev.conversaic.io |
Yes |
| Placement key | answer_footer_sponsor |
Yes |
| Allowed categories | developer_tools, productivity |
Yes |
| Blocked categories | medical, gambling, crypto |
Recommended |
| Disclosure label | Sponsored |
Yes |
| Review owner | Product or growth owner | Yes |
Context payload planning
| Context field | Use |
|---|---|
prompt |
Main user request or summarized user intent. |
topic |
Optional normalized topic label. |
placement_key |
Maps the request to publisher policy. |
language |
Filters offers and copy. |
country |
Filters geography-restricted offers when available. |
Pre-launch checks
- The sponsor container does not shift layout when empty.
- The disclosure label is visible before click.
- No-placement responses render no sponsored UI.
- Impression events fire only after the placement becomes visible.
- Clicks route through the tracked redirect path.
- Blocked categories suppress otherwise eligible offers.