Repository navigation
Description
Summary
core/assets/card-asset.json makes a card's cta a closed set when the parent format declares one: "When the parent format declares cta_values (allowed CTA labels), the per-card cta MUST be one of those values." formats/canonical/image_carousel.json doesn't declare cta_values, so a carousel option can only carry it as an undeclared extra parameter on the open params object. On #8628, Brian agreed the carousel should declare it and that it's tracked as a schema change separate from the wording fixes, which are now in #8949.
Proposal
Add an optional cta_values to image_carousel, with the same type as cta_values on native_in_feed and image:
"cta_values": {
"type": "array",
"items": { "type": "string" },
"description": "Permitted values for each card's `cta` (e.g., ['SHOP_NOW', 'LEARN_MORE']). When set, every card's `cta` MUST be one of these values, and a seller refuses any other value with `CREATIVE_VALUE_NOT_ALLOWED`, with `error.field` pointing at that card's `cta`. When absent, a card's `cta` takes free text, and a seller does not refuse it as `CREATIVE_VALUE_NOT_ALLOWED`."
}plus x-added-in for the release it ships in. It's additive on an open params object, so it's a minor, like card_image_sizes in #8937.
Docs:
docs/creative/channels/carousels.mdx: showcta_valuesin the declaration example and say that it governs each card'scta.core/assets/card-asset.jsonctacan then point atimage_carouselcta_valuesby name instead of "the parent format".
Compliance
A step like native_in_feed's reject_cta_not_in_enum would grade it: a carousel option declaring cta_values, and a creative whose cards are all valid except one card's cta, which is outside the set. The same creative with that cta set to a declared value is the accepted control.
Activity
feat(schema): image_carousel declares cta_values for each card's cta (#…