- image — hero product photo + copy
- text — advertiser logo + copy, no hero image
Which mode applies
The Native request offers two image assets:| Asset id | img.type | Role |
|---|---|---|
| 4 | 3 (main) | Hero/product image |
| 5 | 1 (icon) | Advertiser logo |
| Asset 4 (main) | Asset 5 (icon) | Rendered as |
|---|---|---|
| Populated | Any | image — full card with the product photo. Logo (if sent) appears as a small brand mark. |
| Empty / omitted | Populated | text — compact card with the logo + copy. |
| Empty / omitted | Empty / omitted | Bid rejected — no visual to render. |
image

text

Publisher constraints
The mode the publisher accepts is encoded inimp[].tagid — there is no separate ext.thrad.config flag to parse:
*_image_v1— publisher accepts both modes. Asset 4 (main image) is optional; asset 5 (logo) is optional. Image preferred.*_text_v1— publisher cannot render images. The Native request omits asset 4 entirely and marks asset 5 (logo) as required. If your response includesimage_url(asset 4) on a text-mode request, the SSP drops it server-side before render — your bid still wins on the logo if asset 5 is populated, otherwise the bid is silently lost.

