Skip to content

RFC: Creator and show cards — images, sample content, audience stats, and a typed talent link on collections #8092

Closed

Description

@bokelley

Problem

When a proposal answers a brief with creators or shows, the buyer (a person or an agent) wants a card for each one: a picture, a few sample videos or a sizzle reel, audience stats (for example 55% male, mostly 18–26, 1.2M subscribers, 400K average views) and topics. Most of this has nowhere to go in AdCP today.

Need Today
Picture or thumbnail No image field on collection. product_card images are product-scoped.
Sample content, sizzle reel product_card_detailed.reference_assets[] has no sample-content role. Sellers have to use other.
Audience composition audience_evidence defines only an age dimension. Gender needs a provider-specific URI.
Subscriber and follower counts, average views None outside forecast metrics.
Topics collection.genre[] with genre_taxonomy, and installment.topics[]. These are fine.

There's also no typed link between the channel and the person. talent[].brand_url is a loose URL. The person's likeness and endorsement rights live in brand.json as a rights-holder brand (right_type: talent), but a collection can't point at that brand with a {domain, brand_id} reference. So a buyer can't connect "this channel" (what's being sold) to "this person" (whose rights are being licensed).

Proposal

  • collection.images[]: thumbnail and banner.
  • collection.sample_content[]: {url, kind, published_at}, plus a sample_content role for reference_assets.
  • collection.audience_stats: follower count per distribution, average views per installment, measured_at and source.
  • A standard gender dimension in audience-characteristic.
  • talent[].brand_ref ({domain, brand_id}) alongside brand_url.

This is the display and audience slice of #1839, which triage asked to split into separate identity, trust and audience issues. Related: #6538.

Activity

  1. added
    rfcProtocol change — auto-adds to roadmap board
    schemaJSON Schema source-of-truth: definitions, codegen artifacts, validation, hygiene
    brandIssue concerns the brand protocol domain
    on Oct 9, 2026
  2. added
    claude-triagingTriage routine is actively working on this issue (1-3 min)
    on Oct 9, 2026
  3. added this to the Spec Backlog milestone on Oct 9, 2026
  4. bokelley commented on Oct 9, 2026

    @bokelley
    ContributorAuthor

    Triage

    Classification: Feature request (RFC)
    Bucket(s): spec / protocol, brand, schema
    Status: ready-for-human
    Milestone: Spec Backlog

    What the experts said:

    • ad-tech-protocol-expert: All 5 proposals are non-breaking (minor); brand_ref cleanly reuses /schemas/core/brand-ref.json; gender needs a value-set definition and GDPR Art. 9 scoping note before conformance tests can be written; audience_stats needs an immutability-model decision and a MUST NOT targeting-predicate clause.
    • adtech-product-expert: images[], brand_ref, collection.sample_content[] are clean with zero adoption cost; audience_stats as a standalone object creates fragmentation alongside audience-evidence.json — recommends a lightweight seller-declared evidence profile instead; sample_content role on reference_assets is the wrong layer (creative-brief construct, not a seller catalog field — drop it, rely on collection.sample_content[] alone); gender needs explicit WG governance sign-off due to GDPR/CCPA special-category implications.

    My take: Three of five proposals (images[], collection.sample_content[], talent[].brand_ref) are schema-coherent, non-breaking, and agreed upon — ready for WG ratification as a narrow first PR. Two proposals (audience_stats shape, gender vocabulary) have open design questions that need your call before they can be conformance-tested.


    Decision 1 — audience_stats shape — experts disagree; @bokelley, your call: A or B?

    Option A — standalone lightweight field on collection (what the RFC proposes):

    {
      "audience_stats": {
        "distributions": [
          { "platform": "youtube", "followers": 1200000 },
          { "platform": "instagram", "followers": 430000 }
        ],
        "avg_views_per_installment": 400000,
        "measured_at": "2026-09-01T00:00:00Z",
        "source": "seller_declared"
      }
    }

    Simple to produce; intentionally mutable/display-only (no hash/attestation ceremony). WG must add a MUST NOT targeting-predicate clause. Introduces a third audience-data bucket alongside audience-evidence and ext.

    Option B — seller-declared profile inside existing audience-evidence[]:

    {
      "evidence_id": "yt-followers-2026q3",
      "snapshot_id": "snap-001",
      "content_digest": "sha256:...",
      "evidence_type": "seller_declared",
      "relationship": "reach_estimate",
      "value": 1200000,
      "unit": "count",
      "audience": { "dimension": "age", "range": { "min": 0, "max": 99 } },
      "measurement_window": { "start": "2026-09-01", "end": "2026-09-30" }
    }

    Reuses existing schema machinery; buyer agents see one coherent audience-data shape. Some audience-evidence required fields (baseline, methodology, subject_type, provider) would need to be relaxed for this profile to avoid ceremony overload.


    Decision 2 — gender dimension vocabulary — @bokelley, your call: A or B?

    Option A — canonical AdCP gender dimension (what the RFC proposes):

    { "dimension": "gender", "value": ["male", "female", "nonbinary"] }

    Simpler wire; maximally interoperable. Requires AdCP to define and own a demographic vocabulary — a protocol stance with GDPR Art. 9 special-category implications that should be an explicit WG ballot, not an incidental schema addition.

    Option B — delegate to provider taxonomy (already works today):

    {
      "dimension": "https://iabtechlab.com/taxonomy/2.1#50001",
      "value": "male",
      "taxonomy": { "system": "https://iabtechlab.com/taxonomy/2.1", "version": "2.1" }
    }

    AdCP stays neutral on demographic vocabulary; providers choose their taxonomy URI. Less interoperable — buyer agents must know each provider's taxonomy to compare gender splits across sellers.


    Recommendation: A narrow first PR for images[] + brand_ref + collection.sample_content[] can open immediately (all three agreed, clean delta: core/collection.json, core/talent.json; also add deprecated: true to talent[].brand_url per the format_ids migration pattern). File a follow-up issue scoped to audience_stats + gender once calls 1 and 2 land.

    This is the display and audience slice of #1839 (Spec Backlog), related to #6538.


    Triaged by Claude Code. Session: https://claude.ai/code/session_01QWfeEzJBD435FLZ7jVVvtz


    Generated by Claude Code

  5. added
    claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.
    and removed
    claude-triagingTriage routine is actively working on this issue (1-3 min)
    on Oct 9, 2026
  6. modified the milestones: Spec Backlog, 3.3.0 on Oct 9, 2026
  7. bokelley commented on Oct 9, 2026

    @bokelley
    ContributorAuthor

    WG decision brief (3.3)

    Track: consent round. Objections by Fri 2026-10-16 23:59 UTC. Not on the live agenda unless someone objects. Draft PR: #8098.

    Recommended shape. No audience_stats object. Each card fact uses a surface that already exists:

    • Follower or subscriber count: new experimental distribution[].followers on core/collection-distribution.json. It $refs audience-size (range, precision, as_of) under feature id media_buy.collection_cards. It counts accounts, not people, so it is not summed or read as reach.
    • Audience composition: product audience_evidence as seller_declared and observed, with the platform as provider and a platform-audience baseline. No schema change. A worked example is in the draft PR.
    • Average views per installment: forecast views. No schema change.
    • Gender: held until feat(schema): add experimental portable core gender targeting #7925 merges, then a follow-up commit on the PR. If feat(schema): add experimental portable core gender targeting #7925 misses 3.3, this ships followers only and question 2 moves to 3.4.

    Adopter. Availnet (a creator marketplace) is the single adopter behind the experimental media_buy.collection_cards surface.

    Questions

    1. Replace the proposed audience_stats object with distribution[].followers (audience-size), composition through audience_evidence (seller_declared), and average views through the forecast? Or ship audience_stats as proposed? Recommend yes. One audience-data shape per meaning, reusing feat(schema): report audience size as a range on sync_audiences #8024's range-and-precision model.
    2. Add a canonical gender dimension to audience-characteristic using feat(schema): add experimental portable core gender targeting #7925's value set (female, male, non_binary, hoisted to enums/gender.json)? Or keep provider URIs only? Recommend yes. Population-level composition is not personal data. feat(schema): add experimental portable core gender targeting #7925's sex_gender restricted-attribute classification governs targeting, not evidence. Comparing gender splits across sellers is the point of a card. Evidence stays non-targeting, and feat(schema): add experimental portable core gender targeting #7925's by_demographic stays age-only.
    3. Is the forecast views metric an acceptable home for "average views per installment" in 3.3? Or does the WG want a trailing-window metric (median views over the last N installments, with the window stated)? Recommend yes for 3.3. It is a projection for the proposed buy, not a trailing average, and the forecast has no per-installment unit. The draft says so and tells sellers to state the basis in the product description. Revisit in 3.4 if adopters need a measured trailing figure.

    Open points noted in the PR:

    • followers lives on collection objects, which publishers author in adagents.json. That has no capabilities response, so the experimental_features rule is worded for a seller that serves or relays collections.
    • audience_evidence carries digest-pinned snapshots, which is heavy per creator.

    Default if no objection by Fri 2026-10-16 23:59 UTC: the recommendation as drafted.

  8. bokelley commented on Oct 11, 2026

    @bokelley
    ContributorAuthor

    Slice C filed as #8137: return full collection objects in get_products and proposal responses, add collection.url, and resolve people through talent[].brand_ref to their brand or rights agent (get_brand_identity) rather than copying identity into the collection.

  9. removed
    needs-wg-reviewBlocked on a working-group decision — surface in WG meeting agendas
    on Oct 28, 2026
  10. bokelley commented on Nov 6, 2026

    @bokelley
    ContributorAuthor

    Done for 3.3, as experimental: collection cards in #8094, follower count in #8098, and full collection objects in #8141 (slice C, #8137). Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    brandIssue concerns the brand protocol domainclaude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.rfcProtocol change — auto-adds to roadmap boardschemaJSON Schema source-of-truth: definitions, codegen artifacts, validation, hygienespec / protocol

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions