Native cards are responsive — they fill the container you give them, images scale, no horizontal scroll on mobile. Banners use fixed IAB sizes.
| Format | Billing | Sizes / count | Responsive |
|---|---|---|---|
| Native link — inline in the answer | CPA | 1 | yes |
| Product card (image, title, price, button) | CPA | ×1 / ×2 / ×3 | yes |
| Sponsored slot — in a results list | CPA | 1 | yes |
| Coupon card (promo code) | CPA | 1 | yes |
| Inline card | CPM/CPC | 1200×628 · 300×250 · 336×280 | fixed |
| Leaderboard | CPM/CPC | 728×90 · 970×250 · 468×60 | fixed |
| Right rail | CPM/CPC | 300×600 · 300×250 · 160×600 | fixed |
| Left rail | CPM/CPC | 160×600 · 120×600 · 300×600 | fixed |
Styling: cards are native — match them to your UI (fonts, colours, radius). Two things are mandatory and must not be removed: the visible "Sponsored" label and rel="sponsored noopener" on the link. That's what makes the format compliant.
"Do you support responsive ad units like Google's?" For native cards — yes, by default: one container, content adapts. For banners sizes are fixed today; auto-picking a size for a slot is configured during integration if you need banners specifically.
Which format when: shopping/product questions → product card or native link; deal/discount intent → coupon card; list-type answers ("top 5 hotels in Bali") → sponsored slot; layouts with space outside the message stream → rail/leaderboard banners.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article