Ad Slots & Formats
activeReference for every retail-media ad slot a publisher can expose — Display Ads (Banner and Native formats), Sponsored Ads (Product/Brand/Display), the contexts they appear in, and the full slot matrix.
Display Ads
Labelled General Ads in the CDXP panel's slot-category picker; these docs say Display Ads throughout.
When defining a position for Display Ads, the user has two main choices: Native or Banner.
-
Banner: This allows selection of display templates — Banner, Slider, or Sticky — each with a fixed size.
Size Dimensions Skyscraper 120 × 600 Wide Skyscraper 160 × 600 Medium Rectangle 300 × 250 Full Banner 468 × 60 Leaderboard 728 × 90 Billboard 970 × 250 Custom sizesThese are standard industry sizes. As the publisher, you can also define a custom size to fit a placement — for example
1218×144,300×100,300×200,300×300, or600×400are all valid. -
Native: This supports formats like:
- Simple
- Content
- Notification
- Slider
- Text
Native slots have no fixed dimensions — you render the returned assets into your own layout.
placementCount
Slider banners and all Native slots can carry a placementCount — how many ads
the slot shows.
Both Native and Banner types share common attributes: a name, the associated media property, a description, and an active status.
Sponsored Ads
Sponsored Ads are separated from the general API and include three subtypes:
- Product: Designed to promote a series of specific products.
- Brand: Intended to promote a brand and its associated products.
- Display: Used to show a banner ad.
All of these share common attributes: a name, the associated media property, a description, placementCount (indicating the number of ads to display), and an active/inactive status.
In addition, Sponsored Ads incorporate Contexts (explained below).
Contexts
On the publisher side, there's a concept called Context, which defines the environment or page type where each ad slot will appear. This determines what the runtime ad request must carry about what the user is browsing.
Contexts are mandatory when creating a Sponsored Ads slot and must be selected from the following options:
| Context | Page type | Request must carry |
|---|---|---|
| Product Page | A product detail page — comments, ratings, related products; typically has a productId in the URL. | productId |
| Category Page | A list of products within a specific category; typically has a categoryId in the URL. | categoryId |
| Search | A list of products related to the user's search term. | keyword (the search query) |
| Product Listing Page | A custom page with lists of products without a specific context or order — promotion pages, curated collections. | nothing about the user — see below |
Three of the four contexts require a signal about what the user is browsing right now.
Product Listing Page is the deliberate exception: it fills from promotion targeting
instead, so productId / categoryId / keyword are ignored even if sent. Use it for
curated or promotional pages that have no single product, category, or search context.
Runtime handle
Every slot you create gets a numeric ad slot ID. Pass the IDs you want filled as
adSlotIds in the Ad Request or
Sponsored Ads request — or, for a Display Ads
slot you want the SDK to render, place the ID in a data-bob-id container attribute (see
Render Display Ads with the Web SDK). SDK rendering covers Display Ads only; Sponsored Ads
slots always go through the API.
Slot matrix
Every slot you can create, and what each combination carries:
| Type | Format | Templates | Size | placementCount | Context |
|---|---|---|---|---|---|
| Display Ads | Banner | Banner, Sticky | One fixed size per slot | — (single ad) | Not used |
| Display Ads | Banner | Slider | One fixed size per slot | ✓ | Not used |
| Display Ads | Native | Simple, Content, Notification, Slider, Text | None — you lay out the returned assets | ✓ | Not used |
| Sponsored Ads | Product, Brand, Display | None | None | ✓ | Mandatory — one of the four above |
Sizes come from the standard list or a custom size you define. Beyond the columns above, every slot also carries a name, its media property, a description, and an active/inactive status.