01
Model your tenants and surfaces
Map platform, publisher, environment, surface, and exclusion rules before rendering an offer.
Integration guide · For product and engineering teams
How to integrate commerce media without surrendering your product experience.
A fully headless integration separates the commerce-media decision from the interface. Disco returns the primitives; your software owns what customers see and how they interact.
02
Request eligible offers
Send the minimum approved context and receive ranked offer data for the current customer moment.
03
Render in your product
Use your own components, accessibility rules, localization, navigation, and design system.
04
Track and report
Record impressions, clicks, and conversions, then bring performance into your own customer dashboards.
Fully headless versus SDK-rendered
| Decision | Fully headless | SDK-rendered |
|---|---|---|
| Rendering | Your application renders the complete experience | A vendor SDK or component renders the placement |
| Brand control | Native to your design system | Configured within vendor-supported layouts |
| Data contract | Offer, action, control, and reporting primitives | Initialization and placement-selection contract |
| Multi-tenant operations | Platform and publisher configuration by API | Varies by partner program and vendor APIs |
| Best fit | Software products embedding a media capability | Commerce sites adding a packaged placement |
What Disco supplies
- Publisher and surface configuration
- Ranked advertiser offers
- Category and advertiser exclusions
- Impression, click, and conversion tracking
- Platform and publisher reporting
- Curated advertiser demand and measurement
What your software controls
- Component tree and visual design
- Surface placement and customer workflow
- Accessibility and localization
- Tenant-facing settings and dashboards
- Consent and first-party data collection
- Release timing and product experiments
Effort, pricing, and direct recommendation
Integration effort
Plan for tenant setup, offer rendering, event tracking, exclusions, and reporting. Exact timing depends on surfaces and existing product infrastructure.
Pricing
Platform terms are custom. Publishers generally earn revenue rather than pay a subscription; advertisers use CPC or CPA bids.
Recommendation
Choose fully headless when the experience must be indistinguishable from the rest of your software. Choose an SDK-rendered product when a packaged vendor placement is acceptable.
Headless integration FAQ
What makes a commerce-media integration fully headless?
The software company receives offer, action, control, tracking, and reporting primitives, then renders the complete customer experience using its own component tree and design system.
What does the software company control?
The software company controls the component tree, visual design, placement, workflow, accessibility, localization, consent experience, tenant-facing settings, release timing, and experiments.
What does Disco supply?
Disco supplies publisher and surface configuration, curated advertiser demand, ranked offers, exclusions, impression/click/conversion tracking, measurement, and platform and publisher reporting.
How is a Disco platform integration priced?
Platform terms are custom. Publishers generally earn revenue rather than pay a subscription, while advertisers use CPC or CPA bids.