Compare
Compare separate SSP and DSP platforms
Separate SSP and DSP platforms can preserve established partner relationships, but your team must reconcile their configuration, reports, and billing. Riptide runs supply, demand, and ad delivery through one serving plan and auction, with integrations for external partners.
| Area | Separate SSP and DSP platforms | Riptide |
|---|---|---|
| Auction | Coordinate each platform's eligibility and pricing rules | Resolve direct campaigns, programmatic bids, and deals in one auction |
| Reporting | Match events, time windows, and definitions between reporting systems | Reporting and billing use a shared event stream |
| Integrations | Maintain connections between your supply and demand platforms | Supply and demand share a serving plan; external partners connect through demand routes and adapters |
| Custom logic | Check which extension interfaces each platform supports | Serving plugins, model-registry Decisioners, and reporting APIs |
| Agent access | Check tool support and permissions for each platform | Admin APIs and MCP tools with shared permissions and audit records |
Migrate in stages
Start with one role and a limited set of traffic. For example, move supply onto Riptide's SSP and connect existing demand partners through supported routes and adapters. Compare delivery, reporting, and billing before expanding the migration.
A single platform may simplify operations; separate platforms may still suit your partner or feature requirements. Check those requirements against the standards guide and demand integration guide.
Plan your migration
Share your expected traffic, ad formats, and the systems you need to connect. We can help you choose a plan and identify the setup work.