Retail Media
activeRetail Media is the Binoban capability that lets a marketplace or publisher monetize its audience by selling ad inventory to sellers and advertisers, who in turn promote products and brands right where shoppers are already buying.
How things are organized
Retail Media has a simple hierarchy, shared by both ad families below:
Publisher
└── Media property a website, app, or other ad-supported digital asset
└── Ad slot a designated space where one or more ads display
- A media property is a website, app, or other ad-supported digital asset you control.
- An ad slot is a designated space where one or more ads display. An ad slot belongs to exactly one media property.
- Slots carry common attributes: a name, the media property, a description, and an active status.
Two ad families
| Family | What it is | Slot types | Guide |
|---|---|---|---|
| Display Ads | Banner and Native placements served through RTB | Banner (templates: Banner / Slider / Sticky) · Native (templates: Simple / Content / Notification / Slider / Text) | Display Ads |
| Sponsored Ads | Promote specific products, a brand, or a display banner, blended into the shopping experience | Product · Brand · Display — each tied to a page Context | Sponsored Ads |
In both families the Web SDK runs on your surface for identity and event tracking, and it can render ads for you in both of them. Display Ads fill from a container the SDK finds on the page; Sponsored Ads need an explicit call carrying the page context, because they are contextual. Either family can also be served through the API and rendered by your own code. The full slot/format matrix — sizes, templates, contexts — is in Ad Slots & Formats.
To fill Sponsored Ads slots, the platform also needs your catalog — the sellers, products, variants, and categories behind your store. That's synced separately; see Catalog API.
What you integrate
Retail Media has a shared foundation, then a family-specific serving flow. Work through it top to bottom — it is the order the sidebar follows.
Set up your inventory — done once in the CDXP panel
Declare what you have to sell before anything can fill it: the media property, the ad slots inside it, and the credentials your surface authenticates with.
→ Define the media property · Define ad slots · Connection, credentials & host URLs
Sync your catalog
The sellers, products, variants, and categories behind your store. Required for Sponsored Ads — they promote real products — and it improves targeting across all of Retail Media.
Serve the family you're integrating
Each family has its own page, and two rendering paths beneath it: let the SDK draw the ad, or draw it yourself. On the Sponsored Ads SDK path you can also mix the two — the SDK requests and tracks the ads while your own components render them.
Report what happened
Impressions and clicks are what campaign delivery and billing run on. The SDK paths do this for you — including when you render Sponsored Ads yourself but let the SDK measure them. The API paths do not.
→ Track ad impressions and clicks
Next steps
- Start here — Define the media property
- Then pick a family — Display Ads or Sponsored Ads
- Look up slots, formats & contexts — Ad Slots & Formats
- Look up an endpoint — Ad Request API · Sponsored Ads API · Sync API
- Look up what's emitted — Ad events
- Lay the foundation first — Track customer data
- Run campaigns, wallets and ad supply in the panel — Dashboard guide