Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
"adcontextprotocol": minor
---

Withdraw the 3.3 additions to the deprecated `get_products` task and the deprecated `sync_creatives` `assignments[]` row, and move execution readiness to `list_products` (adcp#8501, entries 20–25 and the `get_products` rows of the deprecated-task table). 3.3 adds no field that exists only on a deprecated task. Where a live task lacks the capability, it moves there or waits for 4.0.

**All of these shipped in 3.3 betas and are removed after `3.3.0-beta.5`.** This is a beta-to-beta change, not a change to a stable release. The betas are immutable, so a seller or SDK built from a beta bundle has the surfaces below to remove.

**Exact-package forecasts on `get_products` (#8468, beta.1 to beta.5).** Removed: `refine[].package`, `media-buy/package-forecast-input.json`, the request rule tying `package` to `buying_mode: "refine"` and to non-finalize entries, and `refinement_applied[]` `result_product_id`, `resolved_start_time` and `resolved_end_time` with their `applied` rule. `refinement_applied` is optional again for every request. The forecast has no 3.3 home; where it belongs on the compact lifecycle is an open working-group question.

**`get_products` `filters.target_audiences` (#8215, experimental, beta.1 to beta.5).** Removed from `core/product-filters.json`, with its `dependencies` entry. It is planned for `list_products` `offer_filters` and `buy_products` purchases in 4.0 (`purchase_target_audiences_required_in_4_0`).

**Collection cards on `get_products` (#8141, experimental, beta.0 to beta.5).** Removed: the `include_collections` request flag, the response-level `collections` array and its `dependencies` entry, the `collections` branch of `get-products-rejected.json`, and `include_collections` in the `wholesale_feed_version` scope. `list_products`, `request_proposals` and `refine_proposals` keep both.

**Execution readiness (#7934, experimental, beta.1 to beta.5) moves to `list_products`.** `include_execution_readiness` leaves the `get_products` request and the `execution_readiness` map leaves its response. Both are added to the open `list_products` request and response, with the same shape and rules; the map is versioned independently of `feed_version` and is absent on an `unchanged` outcome. The `media_buy.execution_readiness` storyboard now drives `list_products`. `binding_field` now names the `buy_products` paths, `purchases[].optimization_goals[].event_sources[].event_source_id` and `purchases[].catalog_ids[]`, instead of the legacy `create_media_buy` `packages[]` paths, and `execution_requirements` documents the purchase binding beside the legacy one.

**`price_adjustments` on `get_products` pricing options (#7955, experimental, beta.1 to beta.5).** Removed from the `cpm`, `vcpm`, `cpc`, `cpcv`, `cpv`, `cpp` and `flat_rate` options with their `dependencies`, along with `pricing-options/price-adjustments.json`, `error-details/price-adjustments-mismatch.json`, the product rule that a placement-selection row requires `overlay_support.placement_selection`, the `price_adjustments_resolution` verifier constraint on `product-purchase.json`, and the `price-adjustments` test vectors. A seller stops listing `media_buy.price_adjustments`. The design is kept for the canonical pricing option in 4.0 (`canonical_price_adjustments_required_in_4_0`).

**`sync_creatives` `assignments[]` `landing_page_url` and `trackers` (#8180, #8220, beta.0 to beta.5).** Removed from the deprecated row, which now rejects them by name. The `assignment_operations` `assign` operation keeps both.

The consumed changesets for these PRs stay in `.changeset/pre/` as history. The 3.3 release notes, What's new, the 3.2 to 3.3 migration guide, and the 3.3 beta page say what to remove under "Withdrawn from the deprecated tasks".
2 changes: 1 addition & 1 deletion docs/building/by-layer/L3/error-handling.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -533,7 +533,7 @@ The wire-level `recovery: "correctable"` on the sandbox-only path is the registe
| [`AUDIENCE_TOO_SMALL`](/docs/building/verification/compliance-catalog#error-code-audience-too-small) | correctable | Audience segment below minimum size | Broaden targeting or upload more audience members |

{/* /schemas/latest/ link: schema unreleased; switch to the v3 alias after the next release. */}
For `UNSUPPORTED_FEATURE` rejecting an unsupported or removed targeting dimension, details SHOULD follow [`error-details/unsupported-targeting-dimension.json`](https://adcontextprotocol.org/schemas/latest/error-details/unsupported-targeting-dimension.json); see [Rejected targeting dimensions](/docs/media-buy/advanced-topics/targeting#rejected-targeting-dimensions). For an `INVALID_REQUEST` that rejects a buyer-supplied `pricing` differing from the price a `price_adjustments` table resolves to, details SHOULD follow [`error-details/price-adjustments-mismatch.json`](https://adcontextprotocol.org/schemas/v3/error-details/price-adjustments-mismatch.json). For `REQUOTE_REQUIRED`, details SHOULD follow [`error-details/requote-required.json`](https://adcontextprotocol.org/schemas/v3/error-details/requote-required.json). For [`ACTION_NOT_ALLOWED`](/docs/building/verification/compliance-catalog#error-code-action-not-allowed) with `reason: "not_supported_on_buy"`, the existing [`error-details/action-not-allowed.json`](https://adcontextprotocol.org/schemas/v3/error-details/action-not-allowed.json) shape also permits `decline_reason`. Sellers SHOULD emit the coarse reason when they have a structured seller-policy classification and disclosure does not expose private thresholds or enforcement controls. Buyers MUST tolerate its absence and MUST NOT infer that an undisclosed policy does not exist. Structural action denials SHOULD omit it.
For `UNSUPPORTED_FEATURE` rejecting an unsupported or removed targeting dimension, details SHOULD follow [`error-details/unsupported-targeting-dimension.json`](https://adcontextprotocol.org/schemas/latest/error-details/unsupported-targeting-dimension.json); see [Rejected targeting dimensions](/docs/media-buy/advanced-topics/targeting#rejected-targeting-dimensions). For `REQUOTE_REQUIRED`, details SHOULD follow [`error-details/requote-required.json`](https://adcontextprotocol.org/schemas/v3/error-details/requote-required.json). For [`ACTION_NOT_ALLOWED`](/docs/building/verification/compliance-catalog#error-code-action-not-allowed) with `reason: "not_supported_on_buy"`, the existing [`error-details/action-not-allowed.json`](https://adcontextprotocol.org/schemas/v3/error-details/action-not-allowed.json) shape also permits `decline_reason`. Sellers SHOULD emit the coarse reason when they have a structured seller-policy classification and disclosure does not expose private thresholds or enforcement controls. Buyers MUST tolerate its absence and MUST NOT infer that an undisclosed policy does not exist. Structural action denials SHOULD omit it.

**Implementation note (non-normative).** Repeated out-of-envelope controls can be used to map a seller's exact share-of-voice, notice-window, frequency, or commitment thresholds. Consider rate-limiting these deterministic probes using the same posture as [`refine_proposals`](/docs/media-buy/product-discovery/proposal-negotiation#log-for-audit-without-leaking-terms), and omit `decline_reason` when even the coarse category would disclose sensitive enforcement logic.

Expand Down
2 changes: 1 addition & 1 deletion docs/creative/channels/broadcast.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -227,7 +227,7 @@ This works today with four gaps. Read them before building on it:

- **The demo is bound on the forecast, not on the price.** A CPM pricing option has no demographic parameters, unlike a CPP option (`parameters.demographic_system`, `demographic`). `measurement_terms.billing_measurement` binds the vendor, the window, and the variance, but has no demographic field.
- **The guaranteed volume has no typed definition.** `purchases[].impressions` is the contracted volume, and a buyer can require a floor on it with `refine_proposals` `constraints.impressions` (a hard minimum summed across purchases). The schema does not say that number counts measured audience, in which demo, from which vendor, or on which window. Those facts sit on the forecast and `billing_measurement`, and the forecast is outside `commercial_terms`, so it is not covered by `terms_digest`. Treat the demo as a term agreed in the human contract outside AdCP, not one a protocol agent can verify.
- **:30 equivalization is only partly expressible.** Rate-side spot-length indexing is expressible through [`price_adjustments`](/docs/media-buy/advanced-topics/pricing-models#selection-dependent-price-adjustments) (a rate row keyed to the spot's format option). Impression-side :30 equivalization and demo-bound CPM remain open and are tracked for 3.4 in [#8001](https://github.com/adcontextprotocol/adcp/issues/8001). Nothing declares whether a :15 impression counts as half a :30 unit or the factor to apply, so on a buy that mixes :15 and :30 spots the impression-side rule is a term to settle outside the protocol.
- **:30 equivalization is not expressible.** Rate-side spot-length indexing needs a separately priced option or product per spot length; a rate table for it is [planned for 4.0](/docs/reference/migration/v4-compatibility#canonical_price_adjustments_required_in_4_0). Impression-side :30 equivalization and demo-bound CPM remain open and are tracked for 3.4 in [#8001](https://github.com/adcontextprotocol/adcp/issues/8001). Nothing declares whether a :15 impression counts as half a :30 unit or the factor to apply, so on a buy that mixes :15 and :30 spots the impression-side rule is a term to settle outside the protocol.
- **No under-delivery trigger, and the schedule on the wire is experimental.** `makegood_policy` does not name a volume shortfall as a trigger. A seller may report the planned schedule as `scheduled` rows in `by_spot`, but that field is experimental and seller-declared, so a buyer cannot assume one. See [Makegoods](#makegoods).


Expand Down
Loading
Loading