Repository navigation
Description
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_cutoffapplies (3.3, oninstallment.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_assignmentsinget_media_buys, so the buyer can see which creative is set for which drop. - A capability gates it, for example
media_buy.installment_creative_assignmentinexperimental_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
- Date windows as well? An optional
valid_from/valid_untilon 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. - Placement routing too? Should
installment_refscombine withplacement_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.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsShipped
Activity
docs(reference): add the rc.0 installment experiments, with dependenc…
bokelley commentedon Nov 13, 2026
Implementation for 3.3: #8972. It targets 3.3 rc.0 as experimental (
media_buy.installment_creative_assignment).It adds
installment_refsto thesync_creativesassignandreplaceoperations, with readback onget_media_buyspackages[].creative_approvals[]andlist_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 returnsVALIDATION_ERROR. A change past an installment'schange_cutoffis refused withCREATIVE_DEADLINE_EXCEEDED. Buyers send the field only to sellers that list the feature (versioning rule 4).Two choices are worth a look in review:
core/creative-assignment.json, which is the row of the deprecatedcreate_media_buy/update_media_buy(fix(schema): keep 3.3 additions off the deprecated create_media_buy and update_media_buy (#8501) #8767).assignment_operationsis atomic and has no per-operation outcome to report the latter.Date windows (Q1) remain a follow-up, so this issue stays open.
docs(reference): describe #8972, per-installment creative assignment,…
docs(sync_creatives): validate the installment example in its test, n…
bokelley commentedon Nov 13, 2026
Proposed for 3.3 rc.0 (Mon Nov 16) as an experimental, capability-gated feature. Implementation: #8972. Buyers send
installment_refsonsync_creativesassign/replaceonly to sellers that listmedia_buy.installment_creative_assignment. It's optional, it's additive on schemas #8866 opened, and it doesn't touchcommercial_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
docs(reference): add the rc.0 installment experiments, with dependenc…
docs(reference): describe #8972, per-installment creative assignment,…
docs(reference): add the rc.0 installment experiments, with dependenc…
11 remaining items
docs(reference): add the rc.0 installment experiments, with dependenc…
docs(reference): describe #8972, per-installment creative assignment,…
bokelley commentedon Nov 13, 2026
Implemented in #8972, merged 13 November and included in
v3.3.0-beta.6:installment_refson thesync_creativesassignandreplaceoperations, experimental undermedia_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.fix(training-agent): refuse installment_refs with UNSUPPORTED_FEATURE (…
docs(reference): add the rc.0 installment experiments, with dependenc…
docs(reference): describe #8972, per-installment creative assignment,…
docs(reference): add the rc.0 installment experiments, with dependenc…
docs(reference): describe #8972, per-installment creative assignment,…
docs(reference): add the rc.0 installment experiments, with dependenc…
docs(reference): describe #8972, per-installment creative assignment,…
docs(reference): add the rc.0 installment experiments, with dependenc…
docs(reference): describe #8972, per-installment creative assignment,…
docs(reference): bring the 3.3 release docs to 3.3.0-rc.0 (#8883)