Skip to content

RFC: declare which changes a sales agent applies to a live creative, and refuse the rest #8404

Closed

Description

@bokelley

Problem

sync_creatives is an upsert: a buyer may change any field of a creative at any time. In practice, which changes a sales agent can apply to a creative that is already live depends on the ad server under it. A creative is live when it has at least one assignment on a media buy that has not ended. Two examples:

  • Google Ad Manager can edit a creative's click-through URL, third-party trackers or tag snippet in place. It cannot change a creative's type, and in practice not its size.
  • Other ad servers may treat a trafficked creative as immutable, and change it only by trafficking a new one and swapping it in.

Today a buyer has no way to learn this before it sends a change, and a seller has no specific way to refuse one. The nearest codes are UNSUPPORTED_FEATURE, which says to check get_adcp_capabilities although nothing there describes live creatives, and CREATIVE_REJECTED, which is a content-policy verdict. So sellers do one of three things:

  • accept the change and silently keep serving the old version;
  • traffic a second copy alongside the first, so both rotate;
  • return an error the buyer can't act on.

All three break the buyer's expectation that a creative_id is one creative.

Proposal

1. Capability. Add media_buy.live_creative_updates to get_adcp_capabilities. It declares which kinds of change the seller applies in place to a live creative:

"live_creative_updates": {
  "in_place": ["click_through", "trackers", "asset_content"]
}

The change kinds are a closed enum:

Kind Means
click_through A changed landing or click-through URL.
trackers Added, removed or changed impression, click or event tracker URLs.
asset_content Replacement content for an asset, keeping the same format and dimensions: a new image or video file, new tag markup, or a new VAST URL.
format A change of format, format option or dimensions.
metadata The name, tags and other fields that are not served.

An empty in_place list means live creatives are immutable. If the block is omitted, the seller makes no claim, which is today's behavior.

2. Semantics of an in-place update.

  • A creative_id is one creative. An accepted in-place change applies to every assignment of that creative, on every media buy.
  • The seller MUST NOT leave a prior version serving alongside the new one.
  • If the seller's review re-runs because of the change, the item's status reflects it, as it does for any update today. Keeping the prior version serving during that review is out of scope here; it belongs to staged activation (Scheduled and held activation for creative swaps (remainder after #8488) #6780).

3. Refusal.

  • A sync item that makes a change outside in_place to a live creative MUST fail with a new error code, CREATIVE_LIVE_UPDATE_UNSUPPORTED.
  • The seller MUST leave the creative unchanged and SHOULD return error.details.change_kinds naming the refused kinds.
  • Recovery is correctable: sync the changed content as a new creative_id, then swap it in atomically with assignment_operations replace (replaces_creative_id).
  • A creative with no live assignment keeps today's plain upsert behavior.

4. Dry run. sync_creatives with dry_run: true returns the same refusal, so a buyer can check a change before sending it.

Why this shape

  • It reuses what 3.2 already has. A change the seller can't make in place becomes a replace, a mechanism that already exists. The proposal adds only the declaration and a precise error.
  • It is coarse on purpose. The declaration is per kind of change, not per field or per format, so a buyer agent can plan with it without modelling each ad server.
  • It doesn't overlap the revision work. supports_revisions (Creative revisions: immutable identity, re-review, and delivery correlation #6347) is about immutable revision identity; this proposal is about what a seller does when the content behind a creative_id changes while it serves.

Open questions

  1. Should the declaration also be overridable per product, for sellers whose products sit on different ad servers?
  2. Should asset_content be split by asset type (image, video, markup, VAST)?
  3. Should a seller report which assignments an in-place update reached, for example through the creative.assignment_changed relationship notification?

Related: #6347 (revision identity), #6780 (staged activation for live revisions).

Activity

  1. added
    rfcProtocol change — auto-adds to roadmap board
    media-buyIssue concerns the media-buy protocol domain
    on Oct 22, 2026
  2. bokelley commented on Oct 25, 2026

    @bokelley
    ContributorAuthor

    Revised design and implementation are in #8488. It is experimental, gated on creative.live_updates, and labelled needs-wg-review.

    What changed from the proposal above

    • The premise. The current spec does not let buyers change any field at any time. Updates to creatives on active packages are refused with INVALID_STATE, and the recovery advice ("pause the package") doesn't work on ad servers that lock trafficked creatives. A declaring seller now returns CREATIVE_LIVE_UPDATE_UNSUPPORTED instead.

    • Location. The capability lives under creative, not media_buy.

    • Serving modes. Each change kind declares a serving mode rather than a bare in_place list:

      • uninterrupted: decided inside the sync call.
      • staged: the prior approved version keeps serving until the change is approved, then it is promoted. On rejection the seller either keeps the prior version or stops serving (on_rejection: keeps_prior | stops).
      • paused_for_review: today's lifecycle.

      staged is the "replace upon approval" case, handled by the seller behind the scenes under the same creative_id. That folds in the core of Scheduled and held activation for creative swaps (remainder after #8488) #6780.

    • Detection before sending. The capability is a floor. Per-creative live_updates on list_creatives gives the exact answer, and a dry_run returns the exact outcome of a specific change.

    • What counts as live. A creative is live when it is approved and assigned to a non-canceled, non-ended package on a non-terminal buy, whether or not the package is paused.

    • Always accepted. name and tags changes are always accepted.

    • Testing. Two storyboards cover this (creative_live_updates and creative_live_update_refusal), and the training agent's /sales tenant implements it.

    The open questions above are answered in the PR's "For the working group" section:

    1. Per-product overrides are deferred. The floor plus the exact per-creative readback covers sellers that run several ad servers.
    2. asset_content is not split by asset type.
    3. Reporting which assignments a change reached is replaced by a rule: staged review is one decision across all assignments, so a creative is never partly promoted.
  3. added this to the 3.3.0 milestone on Oct 26, 2026
  4. bokelley commented on Oct 30, 2026

    @bokelley
    ContributorAuthor

    Consent closed (2026-10-30), no objections. The Session C decision stands. Live creative updates ship in 3.3 as experimental. #8488 lands once it's rebased; the review points from @KonstantinMirin and @pkras are addressed on the branch (a new staged-outcome event, the original wording kept for sellers that don't opt in, no per-creative readback, and the edit-or-swap line: anything measured separately gets its own creative_id).

  5. bokelley commented on Oct 31, 2026

    @bokelley
    ContributorAuthor

    Shipped in 3.3 (experimental) via #8488, first in 3.3.0-beta.3: creative.live_updates with serving modes, CREATIVE_LIVE_UPDATE_UNSUPPORTED, dry-run refusal and the creative.staged_update_changed event. Consent closed 2026-10-30: #8404 (comment).

    Out of scope in that PR: per-product overrides, scheduled activation and held multi-buy assignments. #6780 is the open tracker for the scheduled and held-activation remainder; it overlaps this work and should be retitled to that remainder.

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 boardspec / protocol

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions