Skip to content

RFC: Assign a creative to specific installments of a package #8968

Closed

Description

@bokelley

Problem

A package that buys several installments can't give each one its own creative. A creator package with two posts is the clearest case. The first post carries the awareness brief, and the second, three weeks later, carries the call to action and a discount code. The same holds for a podcast host read that changes by episode, or a print ad that changes by issue.

Creative assignments today have a weight, a rotation group, a sequence position and placement routing, but no installment and no dates (core/creative-assignment.json, and the assign and replace operations in sync_creatives assignment_operations). So a buyer either splits the work into one package per installment, or swaps the creative by hand between drops and hopes the swap lands before the seller's cutoff.

This comes from buyers planning in waves: an awareness push, then a performance push, with the creative and the call to action changing between them. A creator package often spans both.

Proposal

An optional installment_refs on a creative assignment: an array of core/canonical-installment-ref.json.

  • Present, the assignment applies only to those installments of the package. Absent, it applies to every installment, as today.
  • Within one installment, the existing rotation rules (weight, group, sequence, placement routing) work unchanged over the assignments that apply to it.
  • Each ref must be an installment the package bought. In 3.x that's the purchased product's installment set (see RFC: Choose specific installments in 3.x without opening commercial_terms #8967 for choosing slots). A seller rejects any other ref with a validation error naming it.
  • The installment's change_cutoff applies (3.3, on installment.deadlines). An assignment change for an installment past its cutoff is refused, or the seller says it won't take effect for that installment. It is never silently accepted.
  • Readback: the same field on creative_assignments in get_media_buys, so the buyer can see which creative is set for which drop.
  • A capability gates it, for example media_buy.installment_creative_assignment in experimental_features, so a buyer only sends the field to sellers that list it.

It sits on objects #8866 opened (creative-assignment.json, the assign and replace branches), and it doesn't touch commercial_terms. Creative assignment is trafficking, not a signed term, so nothing about it needs a major.

Creator briefs and draft review

For a creator deal, the "creative" the buyer assigns is often the brief: talking points, claims to avoid, the required disclosure, which the creator then turns into a draft. Scoping that to one installment is the same field. The draft review records in #6348 then hang off the right post, and the disclosure check in #8276 can be read per post.

Questions for the working group

  1. Date windows as well? An optional valid_from / valid_until on an assignment would cover packages with no installments that change creative mid-flight, such as social or display between two waves. It's a different mechanism, and I'd keep it to a follow-up unless someone needs it now.
  2. Placement routing too? Should installment_refs combine with placement_refs (this creative, in this break, of this episode)? I'd say yes, as an intersection, but I'd like a broadcast seller's view.

Target: 4.0, alongside #8275 and #8276, with #6348 in 4.x. It's additive, optional and capability-gated, so under #8704 it could also ride in 3.3 if the working group wants it before the RC.

Related: #6348, #8275, #8276, #8967, #7777, #8116.

Activity

  1. added this to the 4.0 milestone on Nov 13, 2026
  2. added
    rfcProtocol change — auto-adds to roadmap board
    media-buyIssue concerns the media-buy protocol domain
    on Nov 13, 2026
  3. modified the milestones: 4.0, 3.3.0 on Nov 13, 2026
  4. bokelley commented on Nov 13, 2026

    @bokelley
    ContributorAuthor

    Implementation for 3.3: #8972. It targets 3.3 rc.0 as experimental (media_buy.installment_creative_assignment).

    It adds installment_refs to the sync_creatives assign and replace operations, with readback on get_media_buys packages[].creative_approvals[] and list_creatives. Absent means every installment. Placement routing intersects with the installment scope. Each ref must be an installment of the purchased product, otherwise the seller returns VALIDATION_ERROR. A change past an installment's change_cutoff is refused with CREATIVE_DEADLINE_EXCEEDED. Buyers send the field only to sellers that list the feature (versioning rule 4).

    Two choices are worth a look in review:

    Date windows (Q1) remain a follow-up, so this issue stays open.

  5. bokelley commented on Nov 13, 2026

    @bokelley
    ContributorAuthor

    Proposed for 3.3 rc.0 (Mon Nov 16) as an experimental, capability-gated feature. Implementation: #8972. Buyers send installment_refs on sync_creatives assign/replace only to sellers that list media_buy.installment_creative_assignment. It's optional, it's additive on schemas #8866 opened, and it doesn't touch commercial_terms. Moved from the 4.0 milestone to 3.3.0.

    Objections by Sun Nov 15. If there are none, it ships in rc.0. Date windows (Q1) stay a follow-up.

    🤖 Generated with Claude Code

  6. 11 remaining items

  7. bokelley commented on Nov 13, 2026

    @bokelley
    ContributorAuthor

    Implemented in #8972, merged 13 November and included in v3.3.0-beta.6: installment_refs on the sync_creatives assign and replace operations, experimental under media_buy.installment_creative_assignment. Date windows on an assignment (question 1, valid_from / valid_until) were not part of it. Anyone who needs them should open a separate issue.

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

    creativemedia-buyIssue concerns the media-buy protocol domainrfcProtocol change — auto-adds to roadmap board

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions