Sponsored Ads
activeSponsored Ads promote a seller's or advertiser's offering blended into the shopping experience — on product, category, search, and listing pages — rather than as a standalone display unit.
Why Sponsored Ads
Your store already has an audience with purchase intent — visitors browsing products, searching, and comparing categories. Sponsored Ads lets sellers and advertisers promote their products and brands on those high-intent surfaces (Search, Category, and Product Detail pages), increasing their visibility right where shoppers are already deciding what to buy.
The defining idea is that Sponsored Ads are contextual, not behavioral: they target based on where the user is and what they're browsing right now, not who the user is or what traits they have. The page context is the signal.
Before you start, complete the shared Retail Media setup: define your media property, your ad slots (choose the Sponsored Ads category), get your connection, credentials & host URLs, and — crucially — sync your catalog. Sponsored Ads promote real products, so the catalog is required.
Subtypes
| Subtype | Promotes |
|---|---|
| Product | A set of specific products |
| Brand | A brand: its logo plus some of that brand's products |
| Display | A banner whose link takes the user to a product, category, brand, or seller page |
Contexts
Every Sponsored Ads slot is tied to one or more page Contexts. The Context decides what
the runtime request must carry about what the user is browsing — see the full table in
Ad Slots & Formats. Product Listing Page is the one
exception: it fills from promotion targeting, and productId / categoryId / keyword are
ignored even if sent.
Setup recap
Sponsored Ads reuse the shared foundation. Same as Display Ads, you:
- Define the media property first — Define the media property.
- Define slots per media — Define ad slots, choosing the
Sponsored Ads category, a subtype (Product / Brand / Display), a
placementCount, and one or more Contexts.
What's extra for Sponsored Ads is the catalog — the platform can only promote products, brands, and sellers it knows about. See Catalog API.
Serving Sponsored Ads
Sponsored Ads have two serving paths, and unlike Display Ads the choice is less about who fetches the ad than about who owns the product card.
| Path | You provide | Binoban provides |
|---|---|---|
| Web SDK | The page context, and a container or your own card markup | The request, rendering (or your template), and all tracking |
| API | A backend call, your components, and your tracking calls | The auction and the ad data |
Both paths need the page context — a productId, categoryId, or keyword — because
Sponsored Ads are contextual. Neither can infer it for you.
Choose the SDK path when you want Binoban to own rendering and measurement. It still lets you keep your own markup: its data mode hands the placements back for your components to render while the SDK keeps tracking them.
Choose the API path when the ad request belongs on your backend — for server-side rendering, or to keep ad serving decoupled from a product and search UI that changes often. That decoupling suits marketplaces well, which is why this was the only path before SDK rendering existed.
Requesting sponsored ads (at a glance)
Endpoint: POST {rtbPath}/api/rtb/sponsoredAd
You provide the page context — at least one of productId, categoryId, or keyword
(priority in that order) — plus adSlotIds, mediaSource, and user. The response's
ads[] carry a type of BRAND, PRODUCT, DISPLAY_BANNER, or DISPLAY_NATIVE, each with
a bidId for tracking. See the Sponsored Ads API reference.
Track impressions & clicks
This step is required, exactly as it is for Display Ads — and uses the same shared flow
for both families. Once an ad is rendered you must report its impression and click
events, plus load, keyed by the bidId on each returned item.
On the Web SDK path these fire automatically, in both of its modes — you write no tracking calls. On the API path you render the ads yourself, so you also fire the events yourself, preferably through the Web SDK running on the page.
Both families route to the single shared page: Track ad impressions and clicks, with attribution via Web SDK reference → Identity.
Next steps
- Start here — Render Sponsored Ads with the Web SDK, or request them from your backend.
- Then — Track ad impressions and clicks, shared with Display Ads.
- Sync the catalog first — Catalog API; Sponsored Ads cannot be filled without it.
- Look up slot contexts and subtypes — Ad Slots & Formats.