How feed-native formats work in AdCP
A platform that hosts feed-native ads implements a creative agent with formats that define buyer-provided assets only. The platform handles rendering at preview and serve time, wrapping the buyer’s content in its UI.Format definition
The format specifies what the buyer provides. Everything else — layout, typography, engagement UI — is the platform’s responsibility:renders array is optional for feed-native formats because the platform determines the visual dimensions at render time based on device, feed context, and layout rules.
Preview with platform chrome
When a buyer callspreview_creative, the platform renders a preview that includes the full feed experience — not just the buyer’s assets in isolation:
inputs let the buyer see how the ad looks in different community contexts — the platform’s rendering may change based on community theme, content density, or feed position.
Community guidelines and creative review
Social platforms enforce content policies beyond standard ad policy — community standards, category restrictions, and promoted content guidelines. These are surfaced through the standard creative review flow:rejection_reasoninlist_creativesorget_media_buysexplains which policy was violated- Community-specific rejections reference the community’s rules, not just the platform’s global policy
- Re-submission after fixing the issue follows the same
sync_creativesupsert pattern
Engagement and interaction models
Feed-native formats often support platform-specific interactions that go beyond click-through:| Interaction | How it maps to AdCP |
|---|---|
| Like / upvote / reaction | Platform-tracked engagement, not an AdCP creative asset |
| Comment / reply | Platform-managed, may appear in get_creative_delivery variant data |
| Share / repost | Platform-tracked, included in delivery metrics |
| Save / bookmark | Platform-tracked |
| Click-through | Standard click_url asset |
| Poll / quiz | Additional format assets (e.g., poll_options text array) |
get_creative_delivery via the ext field on each variant, since engagement types vary by platform.
Carousel and multi-card formats
Many social platforms support carousel or multi-card promoted posts. These use theasset_group pattern:
Generative feed-native
Platforms with AI-powered ad generation can offer generative feed-native formats. The buyer provides a brief, and the platform generates feed-native content that matches the community’s voice and visual style. This follows the brief-in-media-buy pattern. The key difference from standard generative creative: the platform has deep context about its community (trending topics, content style, audience behavior) that informs generation. A generative feed-native ad on a cooking community looks and sounds different from the same brief on a tech community. Preview withcontext_description inputs to see how the platform adapts the brief to different community contexts before launch.
Related documentation
- Implementing creative agents — Pattern 4: feed-native — Implementation guide for feed-native format agents
- Carousels — Multi-card format specifications
- Creative review — Approval flow including community guidelines
- Generative creative — AI-powered creative generation workflows