Skip to main content

What’s new in AdCP 3.3

3.3 is at its first release candidate. The latest checkpoint is 3.3.0-rc.0, published 2026-11-16, after seven betas. A prerelease is SDK-backed only after SDK support for its exact bundle is published. Use the release candidate in development and staging, and read the 3.3 prerelease program before testing. This page lists only what has merged; it is refreshed at each prerelease cut.Three features that shipped in the betas are withdrawn after beta.1: definition pins (beta.0 and beta.1), purchase rights, and installment selection (both beta.1). All three wait for 4.0, because commercial-terms stays closed within 3.x (details). The closed-schema triage removes further beta fields at rc.0, mostly 3.3 additions to deprecated tasks (details).
AdCP 3.3 lets scheduled, human-gated, and offline media run through the same buy as programmatic. A booking can say when it will be confirmed. A proposal request can target a vendor-measured outcome, and a governance plan can budget by period. Products, audiences, and delivery reports can carry what a linear-TV, print, or DOOH seller actually knows: spot lifecycle and makegoods, break position, print proof of insertion and circulation, structured DOOH location, property-grain rollups, and audience sizes as honest ranges. Minute-level dayparts, broadcast mezzanine formats, and the NMO and VideoAmp demographic systems fill in the TV edges. Around that, 3.3 tightens the places where two conformant 3.2 implementations could still disagree: discovery never provisions an account, one agent-resolution rule covers every signing surface, required_for is enforced over A2A with its hardening clauses required, and reporting_webhook.operation_id correlation fails closed. Catalog intake becomes an optional declaration, verifiers can advertise A2A required_for enforcement through request_signing.operation_sources, and ext.adcp becomes a reserved namespace. New single-adopter surfaces ship as experimental, so 3.4 can reshape them without breaking stable integrations. No stable field, enum value, or task is removed. Two result fields, one usage, the principal kind field, the account identity-rekey machinery, the boolean form of demographics, and the RFC 9421 signing profiles are deprecated. All remain functional throughout 3.x and are expected to be removed in 4.0. They are seller_id on event source and audience results (use platform_id), and the natural key as the account reference after provisioning. They also include account.identity_updates, operator_identity, ACCOUNT_MOVED, ACCOUNT_IDENTITY_CONFLICT, and account.stable_account_id (use account_id), principal_kind and expected_principal_kind (a bound principal is always buyer_agent), demographics: true (send { "age": true }), and the RFC 9421 profiles (use the experimental Web Bot Auth profile). 3.3 adds optional fields, enum values, and capability declarations. Schema-valid 3.2 messages stay schema-valid except for the new domain identifier format, and unless they already used a name 3.3 now defines with a different shape; the list is in the migration guide. The normative narrowings are recorded in Versioning and governance and lead the migration guide.

New in rc.0

rc.0 (2026-11-16) is the first release candidate. Its main changes since beta.5 open the schemas that were closed by accident and settle which beta features stay in 3.3. Most of it first shipped in 3.3.0-beta.6 (2026-11-13), cut for SDK testing ahead of rc.0. New in rc.0 itself: the guidance on prerelease pins, unpinned discovery, and anonymous capabilities; the declared assignment operations (#8997); audience targeting without member push (#8996); carousel card CTA values (#9001); the by_package guidance (#8970); the scope and signing_keys rules for several matching authorized_agents entries (#9011, #9017); three renamed experimental values (#8989); an omitted human_review_required in campaign governance (#9007); inline submitted branches that match their published status files (#8934); compliance gates for audience_buy_flow and inline_creatives_without_sync (#9013, #9005); the public test agent’s 3.3-beta.6 preview (#9018); reserved-word-safe enum replacements (#8915); and the Instagram, Facebook, Snapchat and X distribution identifier types (#8995). Schemas are open by default (#8866, DR-0036, decided 2026-11-09). Closing a schema only breaks validators that hard-code it, so 3.x opens the schemas that were meant to be open: 744 of the 859 closed locations in the 3.3 schemas. 115 stay closed. Most have a structural reason, such as unions told apart by key presence, join keys, privacy clamps, and trust.json. The nodes inside commercial_terms, with proposal-budget-constraint, are held closed until 4.0.
  • Every payload that was valid stays valid. Where closure also rejected a specific field, the opened schema rejects it by name.
  • Generated types change. TypeScript types gain index signatures, Pydantic models stop forbidding extra fields, and Zod validators accept unknown keys where the schema opened.
  • A strict validator built from 3.2.10 or earlier still rejects 3.3 fields, so send them only to 3.3 peers. 3.2.11 (#8864) opens the same locations in 3.2.
  • A minor adds to open schemas and adds nothing to a schema that stays closed. See Schemas are open by default.
What stays and what leaves (#8501). Features withdrawn from the betas only because their schema was closed stay in 3.3. They include review_sla on media-buy actions, signing_profile on notification configs, and trackers and landing_page_url on assign operations.
  • Deprecated tasks. Fields the betas added to deprecated tasks and rows leave: refine[].package, include_collections, and filters.target_audiences on get_products; lineage, the creative start gate, and target_audiences on create_media_buy and update_media_buy; and assignment trackers and landing_page_url on sync_creatives assignments[]. The live tasks keep those features where they already carry them, and execution_readiness moves to list_products.
  • Commercial terms. Fields that would extend the commercial terms, which are held closed until 4.0, wait for 4.0: metric_id on performance standards, price_adjustments, counting_mechanisms, and target_audiences on purchases. The last three are out of rc.0. The metric_id withdrawal (#8854) is in review, so rc.0’s schemas still carry it.
  • The migration guide lists every field and what to do if you built from a beta.
The boolean form of demographics is deprecated (#8866, from #8772). In product overlay_support and in required_overlay_support, demographics: true is the 3.2 shorthand for { "age": true }. Senders MUST send the object form. Receivers MUST accept true and read it as { "age": true }, so it satisfies an age requirement and never a gender requirement. It is planned for removal in 4.0 (#8778). The rules for what changes between releases (#8704). The versioning page now opens with them. A minor only adds. A replaced field is emitted alongside its replacement until the next major. Removals and breaking changes happen in a major. A fourth rule keeps a field off a mutating request in a minor when an older seller that ignored it would commit to something different, unless the field ships behind a capability the seller declares. Wire behavior is unchanged. Version negotiation and anonymous discovery. A buyer MUST send a prerelease adcp_version only to a peer that advertises that exact value, SHOULD send the discovery get_adcp_capabilities call without a pin, and SHOULD retry without a pin or at a listed version on VERSION_UNSUPPORTED. A seller SHOULD serve get_adcp_capabilities without credentials, which becomes a MUST in 4.0. On MCP, a gateway that allow-lists methods SHOULD let server/discover, initialize, and tools/list through without credentials. See the migration guide. Also in rc.0.
  • Installments (experimental). A buyer can ask for specific installments of a product through refine_proposals installment_changes (media_buy.installment_refinement, #8974), and the seller answers with a product that declares exactly those installments, so nothing new goes into commercial_terms and binding the slots themselves stays a 4.0 item (Choose installments). installment_refs on a sync_creatives assign or replace operation limits the assignment to those installments of the package, with readback on get_media_buys and list_creatives (media_buy.installment_creative_assignment, #8972); see Assigning to specific installments.
  • Three experimental values renamed (#8989). input_required → input-required (media_buy.execution_readiness), click_through → clickthrough (creative.live_updates), and underdelivery → under_delivery (media_buy.delivery_projection), each the spelling its stable or sibling counterpart already uses. There is no alias, so an implementation built from a beta bundle changes to the new spelling. See Three experimental values renamed.
  • Reserved-word-safe enum values (#8915). Six enum positions get a replacement that no SDK target language reserves, and the originals are deprecated, not removed: pass → passed in enums/binary-verdict.json, get_media_buy_artifacts local_verdict, and the registry feed’s compliance tracks status; global → all in the RATE_LIMITED details scope; and name → full_name in onboarder.match_keys on core/signal-definition.json and core/signal-definition-enrichment.json. Both spellings are valid through 3.x, and 4.0 removes the originals. Send a replacement only to a peer served 3.3 or later. See Reserved-word-safe enum replacements.
  • Origin-only agent URLs (#8939). An origin-only authorized_agents[].url in adagents.json authorizes the agent at that origin, whatever its path. An entry with a path still matches only that URL. When several entries match one agent, its scope is the union of theirs, and a signing_keys pin holds only if every entry that matches and authorizes the message pins keys (#9011, #9017).
  • Declared-option conformance (#8941). A seller accepts a creative that conforms to the format option it targets, and enforces only the limits it declared. See Format conformance.
  • Signed terms bind every member (#8884). Accepting signed commercial terms binds a party to every member terms_digest covers, including members it does not recognize, so a party that cannot interpret one declines (unrecognized_terms) or rejects (UNRECOGNIZED_TERMS) instead of accepting. See Verify terms independently.
  • Reporting without buyer secrets (#8793, experimental). Reliable Reporting managed delivery authenticates as the seller for every pattern, and a seller never holds a caller-issued secret such as an API key, bearer token, or signed URL. Rows pushed in an HTTP body use reporting_webhook. A new https_put file_transfer transport writes immutable objects and a manifest to a buyer HTTPS endpoint, with every request signed under the Web Bot Auth profile and a signed probe before ready.
  • Per-package report rows (#8983, experimental). Reliable Reporting report definitions gain contract_version 1.2: a 1.2 definition whose dimensions include media_buy_id MUST include package_id, so a buyer that bills, caps, or reconciles per package can split a buy-level revision without guessing. 1.0 and 1.1 are unchanged, and a seller MUST serve callers pinned below 3.3 1.0 or 1.1 offerings. See Configuration and capabilities.
  • TMP cache isolation (#7446, experimental). Context Match caches partition by trusted evaluation namespace, and warm hits re-authorize. See the migration.
  • Smaller additions. The optional creative.supports_registry_policy_enforcement capability gates the policy-backed rejection storyboard (#8857). Video asset requirements accept 3gp, mpeg, and m4v containers (#8668). image_carousel gains optional card_image_sizes (#8937, below). Seventeen attestation and reporting URL patterns check only the https scheme (#8792). media_buy.supported_delivery_types lets a seller declare guaranteed, non_guaranteed, or both (below, #8458). Targeting can carry display names beside its geographic codes, geo_value_labels for ISO codes and value_labels on metro and place entries, so a package or audit log shows “New York” next to 501; sellers never target from them (#8966, Geographic Restrictions). distribution-identifier-type adds Instagram, Facebook, Snapchat and X, so a creator’s social channels can be listed in collection.distribution[].identifiers instead of platform_channel_id: instagram_account_id, facebook_page_id, snapchat_profile_id and x_user_id are the canonical identifiers, and instagram_handle, facebook_page_handle, snapchat_handle and x_handle are discovery aliases that registries compare as @ plus the lowercased name, like youtube_channel_handle (#8995). get_media_buy_delivery sellers SHOULD return at least one by_package row per media buy, one per package, and SHOULD omit a buy they can’t report and return an error rather than an empty by_package. by_package: [] stays valid in 3.x, and requiring a row is proposed for 4.0 (#8970, #8973). Experimental campaign governance accepts a sync_plans plan that omits human_review_required, deriving it from the plan’s policies, and states two validation rules for flight order and policy-ID uniqueness (#9007). Conformance. The dependency-impairment storyboards skip their image-creative phases for sellers whose format option is not an image format (#8841). The signal-targeting storyboards run only for sellers that support wholesale discovery for both media buys and signals (#8838). Legacy inline creative manifests are built from the captured format’s exact required slots (#8798).

New in beta.5

beta.5 (2026-11-07) is a small cut: two minor and four patch changes since beta.4. Match keys for cross-publisher frequency capping (experimental, media_buy.match_keys, #8446, #8375). A seller declares which identifiers it can match on, and for what.
  • A key (core/match-key.json) names a uid_type, an optional vendor brand, the scopes it resolves at, and its uses: audience_include, audience_exclude, frequency_cap, identity_match, and conversion_attribution.
  • Keys appear seller-wide as media_buy.supported_match_keys on get_adcp_capabilities, per product as Product.identity.match_keys, which is authoritative for that product, and on TMP provider registration as match_keys beside uid_types.
  • frequency_cap covers caps the seller enforces itself. identity_match declares that a product forwards the key to buyer-side TMP Identity Match, the only place a cap can count across sellers. Two keys are compatible at a scope when they share a uid_type, both list the scope, and their vendors match when both declare one.
  • A product without a persistent identifier cannot declare frequency_cap or identity_match keys, and vendor is required where a scope comes from an identity graph. A change to match keys is a material capability change, signalled through adcp.capability_changes and capabilities.changed.
  • Match keys stay experimental at 3.3 GA; the conformance coverage that graduation needs is #8451. enums/uid-type.json, supported_uid_types, and TMP routing on uid_types are unchanged. Product.identity is closed in 3.2, so send match_keys on it only to callers served 3.3. See Match keys and cross-publisher frequency capping.
sales-fixed-rate is a stable specialism (#8445, DR-0028). The storyboard is unchanged and fully graded, and an independent fixed-price seller passes it, 19 of 19 steps. A passing claim now counts toward the AAO Verified media-buy badge, so a seller whose only claim is sales-fixed-rate no longer reports no_declared_specialisms. The Public Suffix List is bundled (#8702, DR-0037). Verifiers compute eTLD+1 with a Public Suffix List bundled with the verifier, covering the ICANN and PRIVATE sections, never fetched at runtime, and refreshed through normal dependency updates. AdCP names no reference snapshot, so two verifiers on different list versions are no longer non-conformant against each other. On the trust-record path, a verifier whose list lacks a newly added PRIVATE suffix fails closed. Conformance. The deterministic_testing storyboard pins its fixtures and controller calls to one sandbox account, so lifecycle controls can’t target the wrong account (#8731). Legacy creative fixtures get a gated, offline test-kit catalog with exact format references, and media-buy-only sellers need no Creative Protocol tools to run them (#8684).

New in beta.4

beta.4 (2026-11-05) settles the reporting-subscription coverage rule against both SDKs, fixes how assignment operations treat trackers and settings, and adds the storyboards that grade the experimental hold, account-request, and reporting-subscription surfaces. Reporting subscriptions (media_buy.reporting_subscriptions).
  • Two coverage rules change (#8718). A package added to a confirmed buy carries added_at on get_media_buys, and a seller advertising the feature MUST include it on every such package: the package is owed from the period that contains added_at. A grant reduced to tasks that omit get_reporting_status is a loss of reporting authority, exactly like a revocation; restoring the task is a re-grant. Both are detailed under Reporting subscriptions on the principal.
  • Reference model fixes (#8681). A package_ids exception that names every package resolving an offering removes the buy’s periods for it, and an account removed from a subscription in place keeps its periods from before the removal. Both SDKs already computed these from the spec text.
  • Probe reset (#8717). reset_state unpins the caller’s sandbox clock and discards the grant and timezone changes the reporting_subscription_probe made. A seller that lists the probe MUST also list reset_state. set_account_timezone returns a defined result, and the owed_periods_match check compares only over the seller’s retention window.
Assignment operations.
  • replace transfers the replaced assignment’s settings (#8688). On sync_creatives assignment_operations, the replacement inherits the replaced assignment’s weight, placement routing, rotation_mode, group_id, sequence_position, assignment trackers, and landing_page_url override. The seller validates them against the replacement and rejects the atomic request rather than drop or partially apply one. Before, the spec was silent, so a swap could silently stop assignment measurement or send clicks back to the creative’s own destination.
  • Tracker slots only where a format declares them (#8715). Tracker-slot limits apply only when the effective format declares at least one tracker slot. A format that declares none, such as canonical image, makes no slot claim, so a seller doesn’t reject an assignment tracker for lack of a slot; it fires every accepted tracker or rejects the assignment.
Smaller additions.
  • BUDGET_TOO_LOW details can name the constrained budget_field, its basis (daily or lifetime), the constraint that set the floor, such as product_minimum or effective_bid_floor, and a contributing related_field, so a buyer can tell a daily minimum from a lifetime one and a bid-dependent floor from a rejected bid (#8710).
  • creative.supports_provenance, default false, declares product policy publication, per-creative provenance enforcement, and trusted-verifier checks. Hosting a creative library or keeping provenance metadata does not imply it (#8703).
  • An explicit-package create_media_buy can carry opportunity for account-scoped planning-cycle correlation. It never changes opportunity status or consent, and a buyer sends it only to a seller serving 3.3 or later (#8709).
  • A sender SHOULD NOT emit a property the served release does not define, except under ext.{namespace} or inside x-adcp-open-payload fields: a misnamed field is silently ignored, and on get_adcp_capabilities it reads as the field’s default. The runner reports such properties through the always-advisory undefined_properties check (#8156).
Storyboards. account_requests exercises request_account end to end (#8677). media_buy_seller/reporting_subscription_coverage and media_buy_seller/reporting_subscription_capacity drive principal-level subscriptions over the probe’s sandbox clock, with the advisory owed_periods_match check (#8680, #8724). Six storyboards grade hold acceptance (hold_policy_bounds, hold_policy_terms_only, hold_policy_version_gate, hold_unavailable_batch, hold_extension, and hold_ranking), with the advisory instant_offset_within check (#8696). media_buy_seller/assignment_replace_transfers_settings checks the replace transfer (#8695). Unsupported stateful forcing now skips its dependent observations as unavailable coverage (#8642).

New in beta.3

beta.3 finishes the reporting-subscription and account-request surfaces, both experimental, against what the TypeScript and Python SDK implementations found. Coverage is now computable from the wire alone, and canonical coverage vectors with an independent reference model pin it. The account change outcomes and the owed confirmation period first shipped in beta.2; they are summarized here with the rest. Account changes (request_account, account.requests).
  • A change request resolves one of three ways: updated on the named account, matched to an account the caller already holds, or created as a separate account carrying the change. created happens only when the buyer opts in with allow_separate_account: true; otherwise a seller that would only accept the change on a new account refuses with ACCOUNT_CHANGE_REQUIRES_NEW_ACCOUNT.
  • A request that resolves matched or created now MUST carry account, with its billing, billing_entity, and payment_terms, because they can differ from the terms requested. Adopter action: sellers that omitted account on these resolutions now fail validation (#8620).
  • An updated request that changed money terms carries effective_at, when the new terms take effect. A created separate account lists in not_carried_over the account-level configurations it doesn’t have.
  • currency and timezone change through request_account only on sellers that list them in account.requests.changeable_attributes; otherwise the change is refused with UNSUPPORTED_FEATURE.
Losing authority means losing access (#8607). After the caller loses authority for an account, every reference to it fails like an unknown identifier, receipts and consumer statuses included. A seller that wants a buyer to finish reconciling, for example after an agency change, keeps a reduced grant listing only the reconciliation tasks instead of revoking. A partial grant that lists get_reporting_status but not sync_reporting_receipts or sync_reporting_status keeps the account covered, and the missing tasks fail with SCOPE_INSUFFICIENT (#8619). Reporting subscriptions (media_buy.reporting_subscriptions).
  • Which periods are owed. A buy owes the period in which it is confirmed, in full (#8593). A deactivated subscription reads inactive in subscription_coverage, with deactivated_at, while its obligations are retained (#8613). The flight’s stop time uses the new cancellation_effective_at, the delivery stop, so delivery through a cancellation notice period stays owed, and a seller delivers on a buy only inside its flight, extending end_time first for a make-good (#8617).
  • Billing stays contiguous. When a cutover hands a billing feed to a schedule with no boundary at the handoff, the stretch is owed as one stub obligation (stub: true) instead of going unreported. This covers account timezone changes, and it applies to account-level sync_accounts billing configurations too (#8617).
  • Computable from the wire. authorization.regranted_at, a media buy’s flight_history of retroactive flight edits, each package’s reporting_delivery_offering_ids fixed at confirmation, and available_from / withdrawn_at on offerings (#8618).
  • Deterministic. Resolution is per package and fixed per buy and version until the resolved offering is withdrawn; a buy owes the union of its packages’ offerings. max_accounts admission is sticky and ordered by authorization.authorized_at, then account_id in byte order. Billing subscriptions use match: exact with dimensions (#8619).
  • At agency scale. destination_overrides[] routes accounts to other destinations inside one subscription. Adding or removing accounts no longer needs a new subscription_version: membership edits apply in place as excluded_by_buyer intervals. The readback lists 16 prior versions and 1,000 accounts inline, with totals, and get_principal pages the rest through reporting_subscription_page. Several pacing or analytics subscriptions may cover one account; billing stays one per account. Managed-delivery row schemas declare account_id and key on it (#8619).
  • Period arithmetic. A local date’s first instant is always a boundary, so PT24H equals P1D and days nest in sub-daily schedules even where midnight doesn’t exist. Two cutovers inside one period and reactivation after a change made while inactive never owe a period twice. billing_cycle needs a date component, P7D weeks under utc, account_timezone, and source_timezone start on Thursday, status_retention_days counts exact 24-hour days, and a utc offering matches a period_timezone override only when it is exactly UTC or Etc/UTC (#8622).
  • Test assets. Canonical coverage vectors and an independent reference model live in static/compliance/source/test-vectors/reporting-subscriptions/ (#8616), and comply_test_controller adds reporting_subscription_probe to drive grants, account timezones, and the clock against a remote seller (#8621).
Live creative updates (experimental, creative.live_updates, #8488). A buyer changes a serving creative by syncing it again under the same creative_id. The seller declares, per kind of change, whether it applies uninterrupted, staged (the approved version keeps serving until the update is approved), or paused_for_review, and refuses the rest with CREATIVE_LIVE_UPDATE_UNSUPPORTED. list_creatives shows staged_update, and the opt-in creative.staged_update_changed event tracks it. Every task response carries the envelope (#8547). Each task response and async status schema now composes core/protocol-envelope.json, so status, task_id, context_id, message, replayed, adcp_error, and the other envelope fields sit beside the body fields at the response root, and status is required. Before, 47 of the 124 response and status schemas did not compose it, and 18 closed roots rejected envelope fields outright, so generated SDK types could not represent a conforming response. The 18 are reopened. The async status payloads and the governance responses that omitted status now require it. A task-level message has one bound of 2,000 characters in core/task-message.json, and a seller whose text is longer MUST truncate it rather than fail the task. No body field is added, renamed, or removed.

New in beta.1 and beta.2

These shipped before beta.3 and are summarized here with the rest. Everything marked experimental is a registered feature id; a seller that emits it lists the id in experimental_features.
  • A principal is the bound buyer agent (#8443, beta.2). A principal is the buyer agent as the seller has bound it, and nothing else. principal_kind on get_principal and sync_principal responses, expected_principal_kind on sync_principal requests, and enums/principal-kind.json are deprecated and keep working through 3.x, because a bound buyer agent is always buyer_agent.
  • Webhook signing mode is the buyer’s choice (#8475, beta.1). The seller signs with the profile the registration’s signing_profile names, or adcp/webhook-signing/v1 when it is omitted. A buyer that needs legacy signing sends the deprecated authentication block. A seller with legacy_hmac_fallback: false rejects that block with UNSUPPORTED_FEATURE. Condition (b) of request_signature_required is deprecated with the block, and a JSON-RPC batch body is rejected with request_body_malformed (#8064).
  • Capabilities are bounded by structure (#8505, #8526). Every array, string, and keyed map in get_adcp_capabilities has a limit, enforced on new and experimental fields and annotated for 4.0 on fields that were stable before 3.3. Those bounds are the protocol’s limit, and agents MUST NOT design to a byte figure. MAX_CAPABILITIES_BYTES (64 KiB) is a receiver backstop and deployment guidance, not a protocol rule on senders.
  • Undisclosed rosters (#7948, beta.1). A product’s publisher_properties or collections can be [], which means the seller does not disclose the roster. There is no new field and no partial state. Allow lists may be accepted against it and cover only what the seller matches. Exclusion lists are the buyer’s choice, because the buyer sees the undisclosed roster at discovery: a seller that accepts one applies it to its full internal roster, and a seller that cannot rejects it with UNSUPPORTED_FEATURE. A seller serving a release below 3.3 never returns such a product. Buyers treat the roster as opaque and may refuse the product. See Roster coverage.
  • Canceled and completed buys keep their packages (#8467, beta.1). From 3.3 a seller retains packages on terminal buys, with stable identities, platform mappings, and the latest committed configuration, and discloses irrecoverable history through nonfatal errors instead of returning an incomplete list.
  • Mixed creative approval states at startup (#8485, beta.1). A seller keeps pending-review and rejected assignments and starts the approved ones by default. The optional start_requires_all_creatives_approved gate on control_media_buy package controls holds the start until every assignment is approved, and media_buy.features.creative_start_policy declares support. The gate’s copies on create_media_buy and update_media_buy packages are withdrawn at rc.0.
  • Review and escalation commitments (#8417, beta.1). Products can declare creative-review timing in elapsed time or in business time on a seller calendar. Every other SLA stays elapsed time, as in 3.2. report_media_buy_issue and get_media_buy_issue give a human acknowledgement and resolution status for a critical report.
  • Seller offers (experimental, media_buy.seller_offers, #8102, beta.2). A seller can propose a change to an accepted buy: a postponed or canceled installment, a preemption, under-delivery. The offer is a committed canonical proposal with proposal_initiator: "seller" and an offer_reason, read through list_proposals and announced by the identifiers-only proposal.offered notification. The buyer accepts, declines, or revises it with the existing tasks. At expires_at the signed terms stand, and silence is never acceptance. Sellers never send offers to callers below 3.3. See Seller offers.
  • Price adjustments (experimental, media_buy.price_adjustments, #7955, beta.1). A fixed-price pricing option can publish an ordered table of fee and discount rows keyed by format option, placement selection, or always, so a buyer computes the price of what it selects. The table is optional, and its resolution order and rounding are normative. Withdrawn at rc.0 and planned for 4.0 (New in rc.0); see Selection-dependent price adjustments (withdrawn).
  • Execution readiness (experimental, media_buy.execution_readiness, #7934, beta.1). A list_products request with account (a get_products request in the betas) can set include_execution_readiness: true to learn, per product and per execution_requirements entry, whether the account is ready, setup_required, selection_required, input-required, or unknown, with candidates whose resource_id fits the existing binding field. See Per-account execution readiness.
  • Signals (experimental). Signal pricing groups (signals.pricing_groups, #8058) let a seller price alternative age bands, for example, as one audience: pricing_group on a listing and signal_pricing_group_rules[] choose highest or each. See Signal pricing groups. Provider-initiated delivery (signals.delivery_methods, #8044) lets a signal agent declare the methods it can send over, a buyer pin one with delivery_method, and agent deployments report delivery_status. See Declaring delivery methods.
  • Gender targeting (experimental, media_buy.gender_targeting, #7925, beta.1). Core demographics.gender targeting with female, male, and non_binary values, an independent unknown group, product-scoped capabilities, and exact readback for gender-only and mixed age and gender targeting. 3.3 reports demographic delivery by age only, so a gender-targeted package has no gendered delivery readback. Buyers never send core gender fields on a 3.2 contract. See Core gender targeting.
  • Measurement provenance (experimental, media_buy.measurement_provenance, #7940, beta.2). A shared collection-mechanism vocabulary (set_top_box, acr, panel, server_logs, client_tracker, sdk) says what a count is built from: vendor_metric_provenance[] on delivery metrics. billing_measurement.counting_mechanisms[] on measurement_terms is withdrawn at rc.0 and planned for the canonical terms in 4.0. Sellers serving an older pin omit vendor_metric_provenance[].
  • Audience evidence targets (experimental, media_buy.audience_evidence_targets, #8215, beta.1). target_audiences[] names the audience a buyer wants evidence for, beside audience_evidence_requirements. A product satisfies a target only through an admissible evidence item for exactly that audience. A target never targets delivery. Withdrawn at rc.0: no 3.3 wire form remains, and sellers stop listing the feature id; purchases gain the field in 4.0. See Target audiences (withdrawn).
  • Invoice lines (experimental, account.invoice_lines, #8207, beta.1). get_account_financials invoices can carry lines[] that tie an amount to media buys, packages, and reporting revisions, plus invoice_kind (credit_note carries a non-negative amount) and adjusts_invoice_id. Lines are reference only and never settle an invoice. See Invoice lines.
  • Smaller additions. Exact pre-booking availability checks through structured package inputs on product-scoped get_products refinement (#8468, withdrawn at rc.0); an optional display name on measurement catalog metrics (#8437); an optional metric_id on performance standards (#8436); one delegation-chain rule for demand-side grants (#8473).
Version negotiation and closed schemas. A request that carries only adcp_major_version is served the oldest release the seller supports in that major, 3.0 where it is supported (DR-0034, accepted 2026-10-26). In practice that caller is a 3.0 buyer, so it is no longer answered in a shape its validator rejects. A buyer that wants newer behavior sends adcp_version. Schemas are open by default. 3.3 opens the schemas that were meant to be open, starting with the 3.2 proposal flow (#8531), and keeps the rest closed where closure is the contract, such as a join key or a privacy boundary. commercial_terms and the term objects inside it are held closed until 4.0. A minor adds to open schemas and adds nothing to closed ones (DR-0036, decided 2026-11-09; what opened).

Scheduled and human-gated buying

  • An account is its account ID. Sellers MUST return account_id from sync_accounts once the account is resolved, accept it on every account-scoped task, and never change it. A brand is its domain, plus brand_id where its brand.json lists several brands. Countries, currency, timezone, sandbox, and operator_unit are account attributes that a settings update changes without changing the account. Currency, timezone, and sandbox are set at opening, and a seller can review a countries change before applying it. A seller SHOULD return the existing account when a provisioning entry matches exactly one. Natural keys keep working throughout 3.x, but using them as the reference after provisioning is deprecated and planned for removal in 4.0. They remain the way to open an account and to look up its ID. account.identity_updates, ACCOUNT_MOVED, ACCOUNT_IDENTITY_CONFLICT, and account.stable_account_id are deprecated. See Account identity.
  • Expected confirmation time. The submitted envelope of create_media_buy, buy_products, and accept_proposal can carry expected_confirmation_at. A seller whose confirmation waits on a booking round or a manual review window SHOULD set it, and buyers SHOULD check status at that time instead of polling tightly. It is an estimate, not a commitment. refine_proposals can carry it too, on a submitted finalize whose hold waits on a person’s agreement, such as a creator or host. On buy_products, accept_proposal, and refine_proposals, send it only to callers negotiating 3.3. See Expected confirmation time.
  • Vendor-metric outcome goals. criteria.outcome_target.goal accepts kind: "vendor_metric", so a buyer can plan “5,000 store visits measured by a foot-traffic vendor”, optionally with a cost per visit. The seller answers in each forecast point’s vendor_metric_values[] and plans only (vendor, metric_id) pairs its products declare. Send it only on a negotiated 3.3 version. See Vendor-metric goals.
  • Governance budget periods (experimental). A campaign governance plan can split its budget by time with budget.periods[]. check_governance denies a dated action that straddles a period, sits in unallocated budget, or overruns its period. Governance agents declare governance.supports_budget_periods. Part of the experimental governance.campaign cluster. See Budget periods.
  • Holds you can plan and extend (experimental). Products and proposals can carry a hold_policy (media_buy.hold_policy), and refine_proposals extend_hold lengthens a committed hold without re-finalizing (media_buy.hold_extension). See Hold policy.
  • Delegated composition (experimental). A platform that owns the catalog can make product_ids the complete composable universe with criteria.product_ids_exclusive, and a seller that holds no inventory can declare terms_only finalize (media_buy.delegated_composition). See delegated composition.
  • Fixed-price, non-guaranteed sellers. The new stable sales-fixed-rate specialism covers sellers in any medium, digital or linear TV, that publish a fixed price, reserve no inventory, make no delivery commitment, and may hold a buy for review. get_media_buys can carry expected_confirmation_at while a buy is provisional (confirmed_at: null). See Choosing a sales specialism.
  • Renewal and replacement lineage (experimental). A new buy made through buy_products or accept_proposal can name the buy it succeeds with predecessor_media_buy_id and lineage_reason (renewal, terms_change, migration, sunset, replacement). The link is forward-only and same-account; the predecessor is never mutated. Feature id media_buy.lineage. See Media Buy Lineage.
  • Did a failed mutation apply? core/error.json can carry mutation_outcome (not_applied, unknown, applied), so a buyer knows whether to re-plan after a failed state-changing request. See Mutation outcome.
  • Operator fees. The operator_fee price adjustment kind lets an agency’s buying platform show a fee it keeps out of the advertiser’s budget without changing the seller’s price. Sellers never author it. See Operator fees.
  • Change cutoff. Installment deadlines can carry change_cutoff, the last moment a creative swap, pause, or stop still takes effect (traffic log close, posting-cycle lock, print issue close). See Installment deadlines.

Delivery data offline sellers actually have

  • Spot lifecycle, makegoods, and break position (experimental). by_spot[] rows can carry spot_status (scheduled, aired, preempted, makegood), scheduled_at, replaces_spot_id, and break_position. Sellers declare what they report, so a missing row is not read as non-delivery, and they never send scheduled or preempted rows, or the new capability fields, to callers pinned below 3.3. Feature id media_buy.spot_lifecycle. See Spot lifecycle.
  • Print proof of insertion and circulation (experimental). print_metrics on by_installment rows reports the page and position delivered, circulation and its basis (audited or seller_modeled), and a tearsheet evidence record. See Delivery evidence and circulation.
  • Property-grain rollups. media_buy.features.supports_property_breakdown and supports_installment_property_breakdown commit a seller to return by_property and by_installment_property on every product that declares the per-product flag. Two capability-gated scenarios grade it. See get_adcp_capabilities.
  • Structured DOOH location. Concrete screens can carry dooh_placement_attributes.location (lat, lon, structured address), and network products can carry dooh_inventory_summary.venue_counts[]. Both are disclosure metadata; location never changes placement identity. See DOOH.
  • Rows without impressions. Delivery rows may omit impressions when the seller did not measure them, for example on rows that report plays or downloads instead. Absence means not measured, never zero; receivers do not derive impression-based rates, and sellers never omit it toward callers pinned below 3.3. See Rows without impressions.
  • Delivery projection (experimental). Top-level by_package[] delivery rows can carry an advisory projection of lifetime impressions and spend with a projected_end_state and basis. It is a forecast, not a delivery record. Feature id media_buy.delivery_projection. See Delivery projection.
  • Installment lifecycle and proof of publication (experimental). by_installment[] rows can carry installment_status and a publication record (published_at, posts[], optional evidence), so a creator post, newsletter edition, or podcast episode reports whether and where it ran. Feature id media_buy.installment_lifecycle. See Installment lifecycle.
  • Report source custody. A Reliable Reporting report definition’s source can say whether the producer is the system_of_record or derived its figures upstream_derived.
  • Audience sizes as ranges. sync_audiences results can carry audience_size and targetable_size as bounded ranges with a precision, plus match_rate_basis. matched_count and effective_match_rate may now be absent, and buyers MUST NOT read absence as zero. See Audience size.

Creator and collection cards (experimental)

Collections can carry images, sample content, and follower counts, talent can link to its brand identity, and product and proposal responses can return full collection objects on request (media_buy.collection_cards, brand.collection_links). See Collection cards.

Open opportunities and later proposals (experimental)

A buyer can keep an opportunity open after the first response and let sellers send more. opportunity.later_proposals gives consent with optional until, max_count, and min_interval limits. Sellers then create draft-only later proposals, announce each with the identifiers-only proposal.created notification, and serve them through the new list_proposals read, which returns each snapshot beside its disposition. accept_proposal and buy_products accept an explicit opportunity.status: "open" so a buyer can buy part of a plan and keep sourcing. Everything is experimental under media_buy.open_opportunities and advertised in parts. See Open opportunities and later proposals and #8096.

Agent identity and buyer self-onboarding (experimental)

A buyer agent can now make itself known to a seller it has never spoken to. The new Web Bot Auth signing profile identifies the signer by its origin and verifies against that origin’s key directory, with no capabilities call and no seller-issued credential. The operator’s trust.json lists its agents; brands publish grants in theirs, and sellers publish their onboarding posture in account.agent_onboarding. get_principal reports relationship status and expiry. The RFC 9421 profile is deprecated in 3.3 and works through 3.x. See A buyer agent onboards itself and the agent identity migration guide. Account requests (experimental, beta.1). Where a seller supports account.requests, request_account is the one account write. Send brand and operator to open an account, or an account_id with the attributes to change (the brand’s countries, operator_unit, billing, billing_entity, payment_terms). Each write is a request that either resolves in the same response or goes in_review with one pending-action shape saying whose turn it is. A revision guards the change, and it is required when the change touches money. list_accounts reads open requests with include_requests and pages them separately from accounts through requests_pagination. The unreleased get_account_requests task is gone. sync_accounts stays stable everywhere: where account.requests is supported, buyers SHOULD use request_account, list_accounts, and sync_principal instead, and an entry carrying only subscription fields never provisions or reviews an account. In beta.2, a change request can also resolve to an account the caller already holds (matched) or, when the buyer sets allow_separate_account, to a new account carrying the change (created), leaving the named account untouched. A seller that would only accept the change on a new account otherwise refuses with ACCOUNT_CHANGE_REQUIRES_NEW_ACCOUNT. A sync_accounts settings update under review carries its request_id, so a refusal is visible. Two accounts that end up alike after a change are not a conflict, and countries decide products, prices, terms and reviews, never targeting; narrowing them never changes an accepted buy. See request_account.

Linear TV edges

  • Minute-level dayparts (experimental). A daypart entry can use start_time and end_time (HH:MM) instead of whole hours, and products declare the finest resolution they honor in time_granularity. A seller rejects a finer time with UNSUPPORTED_FEATURE and never rounds it. Feature id media_buy.daypart_granularity. See Minute-resolution dayparts.
  • Broadcast formats and currencies. demographic-system gains nmo (Netherlands) and videoamp. video_hosted gains the mxf container and the mpeg2, avc_intra, and xavc codecs as stable values, plus an experimental loudness object (feature id creative.broadcast_loudness). See Broadcast creative.
  • Broadcast TV guide. The broadcast guide now states the reconciliation contract between as-run logs and audience data and walks a CPM-on-demo buy end to end.

Playback events for hosted video and audio trackers

The pixel_tracker event enum adds start, first_quartile, midpoint, third_quartile and complete, so a buyer can attach quartile measurement to video_hosted and audio_hosted files instead of sending event: custom names no seller is obliged to recognize. Downgrades to 3.0.x sellers drop these trackers with an advisory, and 3.2 buyers send them as custom events named for the 3.3 value until they move. See the migration guide. image_carousel gains an optional card_image_sizes list of accepted { width, height } pairs for card images, the same shape as native_in_feed’s main_image_sizes. Card images match a listed pair exactly, video cards are not constrained, and a declaration whose sizes disagree with card_aspect_ratio is invalid. See Carousel ads and #8911. image_carousel gains an optional cta_values list, the same shape as cta_values on native_in_feed and image. When it is declared, every card’s cta MUST be one of the listed values, and a seller refuses any other value with CREATIVE_VALUE_NOT_ALLOWED, with error.field pointing at that card’s cta. When it is absent, a card’s cta takes free text. Before 3.3 a carousel option could only carry cta_values as an undeclared parameter. See Carousel ads and #8960.

Sellers declare the assignment operations they accept

A seller lists the sync_creatives assignment_operations it accepts in the new creative.assignment_operations on get_adcp_capabilities, any of assign, unassign, replace, and merge. The list is exact: the seller rejects any other operation with UNSUPPORTED_FEATURE and applies nothing. Buyers send only listed operations, and when a response served at 3.3 lists none, they send no assignment_operations at all. A seller that declares creative.live_updates MUST list replace, so the swap that CREATIVE_LIVE_UPDATE_UNSUPPORTED recommends always works. Error suggestions SHOULD name only operations and fields the agent accepts, so a buyer that follows a correctable refusal is not refused again. A seller that exposes buy_products or accept_proposal with a creative library MUST list assign, since a compact buy gets its creatives only that way. creative.supports_assignment_merge stays; when it is true, the list includes merge. See Which operations a seller accepts and #8933.

Platform object IDs have one name

sync_event_sources and sync_audiences results now use optional platform_id for the object’s ID in the seller’s ad platform, matching creatives and catalogs. A seller reporting this ID in 3.3 and later 3.x responses MUST emit both platform_id and the deprecated seller_id alias with identical values, including discovery responses. Buyers MUST prefer platform_id and fall back to seller_id only when the new field is absent. Continue using event_source_id and audience_id in AdCP requests. The aliases keep working throughout 3.x and are expected to be removed in 4.0. Seller identity in adagents.json and publisher identifiers is unchanged. See Deprecations.

Installments on the compact product lifecycle

For scheduled media the installment is the thing being sold — a slot in a creator’s upcoming video, a podcast episode, a sponsored newsletter issue. The canonical Product that list_products and the proposal lifecycle read had no installments, so a proposal could name the creator but not which slot, when it publishes, or its material deadlines. 3.3 adds installments[] of the new core/canonical-installment.json, whose identity is the (collection_ref, installment_id) tuple alone. Request it in fields; omitting it on a product that declares collections still means run-of-collection. A purchase buys the product as offered. Naming the exact slots a purchase buys, and dropping or swapping one through refine_proposals, was merged for 3.3 and is withdrawn to 4.0 (below). From rc.0, a buyer can ask for specific slots through refine_proposals (experimental media_buy.installment_refinement, #8974), and the seller answers with a product that declares exactly those slots; naming slots in the signed purchase itself stays a 4.0 item. See Choosing installments. See Installments in the compact lifecycle.

Tightened rules

These narrow what a conformant implementation may do. Each is detailed in the migration guide and recorded in Versioning and governance.
  • Discovery never provisions an account. Discovery and negotiation tasks MUST NOT create or activate an account or accept default terms. See Account references before provisioning.
  • One agent-resolution rule. Request signing, webhook signing, governance JWS iss, designated-task response signing, and rights attestations share one algorithm for which brand.json lists an agent and which keys it may sign with. Some signatures that verified under 3.2 now fail. See Agent resolution.
  • required_for over A2A, hardened. The A2A operation-resolution errata shipped in 3.2.3. Its hardening clauses were SHOULD in 3.2.x and are MUST from 3.3. Verifiers declare support with the new optional request_signing.operation_sources capability; a counterparty MUST NOT infer A2A enforcement from an absent field, and buyers sign every operation in required_for regardless of the marker. See Operation resolution over A2A.
  • reporting_webhook.operation_id fails closed. The seller echoes it into every media_buy_delivery webhook and sends none to a registration that omits it. See Reporting webhooks.
  • Advertise only the measurement terms you accept. See Advertise only what you accept.
  • Audience identifiers keep their wire form. uids[].value for uid2 and euid is the raw identifier, never the encrypted token, and is never case-folded or re-encoded.
  • brand.json fetch limits. The cap rises to 2 MiB, with new MUSTs for streaming enforcement, nesting depth, and bounded fetches.
  • Delivery rows may omit impressions toward 3.3 callers only, and receivers MUST NOT read absence as zero or derive impression-denominated values. The schema loosens; the rules around it narrow.
  • Receivers ignore aggregated_totals in delivery webhooks and do not reject a payload for carrying it.
  • Counterparty-asserted domain lists are bounded. media_buy.portfolio.publisher_domains and signals.data_provider_domains have a normative byte budget, with completeness flags for truncation; buyers never read absence from either list as a denial. See below.
  • Platform IDs under both names. A seller reporting an event source or audience platform ID emits platform_id and the deprecated seller_id alias with identical values. See Platform object IDs have one name.
  • Property domain identifiers have an enforceable format. domain and subdomain values must be lowercase ASCII hostnames; mixed-case, trailing-dot, and URL-shaped values are rejected. See the migration guide.
  • Property list references resolve through AdCP tasks. Issuers expose get_property_list over MCP and accept the reference’s list-scoped Bearer token; a custom download route alone no longer suffices. See the migration guide.
  • Flight start activates committed buys only. A provisional buy (confirmed_at: null) never auto-activates; it stays pending_start until the seller confirms or rejects it. See Provisional buys.
  • Seller revisions advance on every committed change. The media-buy revision advances on every committed change to the state get_media_buys reports, whatever its origin: an AdCP task, a seller operator, seller automation, another authorized principal, a connected platform, or a sync_creatives assignment. history entries for externally originated changes carry the same origin.kind vocabulary as account.change, and creatives gain an optional seller-maintained seller_revision that account.change.resource_revision carries. Buyers that send a stale revision will see more CONFLICT; that is intended. Recorded as DR-0031. See the migration guide.
  • Multi-qualifier metrics omit flat totals. When a buy’s packages report a metric under more than one qualifier set, such as viewability at mrc and groupm, the seller omits that metric’s flat carrier from buy and window totals; read the package rows. See the migration guide.
  • Refinement carries compliance forward. A build_creative refinement keeps the parent leaf’s required disclosures and prohibited claims, and a refined leaf never inherits approval. See the migration guide.
Two more guarantees loosen here, and the response-size default a third (below): a 3.2 verifier can reject a brand.json between 256 KiB and 2 MiB that a 3.3 verifier accepts, and a ready audience no longer promises match counts. Separately, reporting_webhook.authentication and artifact_webhook.authentication become optional on requests served at 3.3, so an integration can drop HMAC before 4.0 (details). Many new fields sit inside objects that 3.2.10 and earlier publish closed, so send them only to peers that negotiated 3.3; see Send only to 3.3 peers.

Optional declarations

  • Catalog ingestion. media_buy.features.catalog_ingestion declares accepted catalog types, ingestion modes, feed formats, content identifier types, an inline batch limit, and item-status granularity. A declaring seller rejects out-of-declaration requests with UNSUPPORTED_FEATURE before changing state. See sync_catalogs.
  • SDK implementation metadata. Agents can report adcp.implementation.sdks[]: package identifiers, exact resolved versions, and the server components they actually use. Missing metadata means unknown; sdks: [] reports none. It is self-reported, does not establish approval or change conformance obligations, and cannot justify certification shortcuts without independently trusted evidence. See implementation metadata.
  • Targeting error details. UNSUPPORTED_FEATURE for an unsupported or removed targeting dimension SHOULD carry the new unsupported-targeting-dimension details. No new error code. See Rejected targeting dimensions.
  • Assignment landing pages and trackers. A seller that declares creative.supports_assignment_landing_page accepts a per-assignment landing_page_url that changes one creative’s destination on one package without touching the library creative, and one that declares creative.supports_assignment_trackers fires assignment-scoped measurement trackers alongside the creative’s own. See Assignment landing pages.
  • Age determination basis on signals. Signal listings, definitions, and enrichment can carry an optional age_determination_bases (verified, declared, inferred) next to demographic_predicate, so a buyer who sets accepted_bases can tell a verified age cohort from a modelled one. A signal listing passes the basis test only when its age range is within it and every one of its bases is accepted; absent means no basis claim. The field is stable, completing the basis vocabulary already on the wire as accepted_bases, supported_bases, and applied_bases. On 3.2, carry it as ext.adcp.age_determination_bases. See Migrating from 3.2 to 3.3.
  • Several collection lists per package (experimental). collection_lists and collection_lists_exclude let a package run on the intersection of several lists and exclude their union. Feature id media_buy.collection_lists. See Combining several collection lists.
  • Signal readiness (experimental). get_signals results can carry signal_status (processing, ready, failed) and the source_audience_id a custom segment was built from. Feature id signals.signal_lifecycle. See Custom segments built from a seed audience.
  • Event source archive. A seller that declares media_buy.event_source_archive accepts archived on sync_event_sources items to archive or restore a source without losing its configuration. See Archiving an event source.
  • Creative and brand. list_creatives echoes creative-level provenance; brand.json gains a brand-wide prohibited_terms list; rights constraints can carry advisory channels[] and excluded_channels[] (experimental, brand.rights_lifecycle); and the HTML-markup legacy formats project to display_tag inline markup instead of html5.
  • Delivery types. media_buy.supported_delivery_types declares whether a seller sells guaranteed inventory, non_guaranteed inventory, or both, so buyers can skip sellers that don’t sell what they’re buying before calling get_products. A declaring seller returns only products with a listed delivery_type.
  • Audience targeting without member push (#8936). media_buy.audience_targeting now means the seller supports audience_include and audience_exclude and answers discovery-only sync_audiences, which a declaring seller MUST do. It no longer promises inline member push. The sync_audiences pattern in the experimental supported_activation_methods declares push, and when that field is absent push is supported, as in 3.2. A seller that lists other patterns but not sync_audiences can omit supported_identifier_types and minimum_audience_size, and rejects add / remove member deltas with UNSUPPORTED_FEATURE. This fits a platform that can target the audiences already on an account but can’t take a customer list. See Sellers without inline member push.
  • The ext.adcp namespace. ext.adcp is a registered, AdCP-owned extension namespace. Its first member is an optional opportunity binding for cooperating 3.2 get_products integrations. See AdCP opportunity extension.

Bounded agent responses

A seller agent that answers a discovery call with tens of megabytes is an availability attack on every buyer that reads the body before checking its size. 3.3 adds Response size bounds: clients SHOULD bound every AdCP response they read, enforce the bound while the body is received rather than after buffering or parsing, cover SSE per event and cumulatively, surface an oversized response as an error rather than truncating it, and bound JSON depth and node count once the byte cap passes — the byte cap bounds ingress, the parse bounds bound memory. The default is 4 MiB, matching what the SDKs and the hosted grader ship, and 4 MiB is the ceiling on what any default may be. This is a recommendation, not a conformance requirement, but the interop effect is real in both directions. A buyer adopting the default rejects a response it would previously have buffered, and the rejection arrives as a mid-body connection abort rather than an adcp_error. A buyer still on the older 1 MiB figure rejects a response a 3.3 buyer accepts. The seller-side counterpart matters more than the number: keep discovery responses small. tools/list, get_adcp_capabilities, and the A2A agent card are the first bytes a counterparty reads, and an oversized one makes an agent unreachable rather than slow. get_adcp_capabilities is the sharpest case for an agent that signs under the deprecated RFC 9421 profile: above MAX_CAPABILITIES_BYTES (64 KiB), that profile’s key discovery fails and your signing keys stop resolving too. Outside that path, the structural bounds are the protocol’s limit on the capabilities response, and 64 KiB is only a receiver backstop, not a design target. See Discovery responses stay small.

Bounded inbound push and webhook bodies

The response bound covers what a client reads on its own call path. 3.3 adds the receiver-side counterpart: Inbound body bounds. Receivers of A2A push notifications and AdCP webhooks (reporting, artifact, collection-list, and account notification subscribers) SHOULD pre-reject an over-limit Content-Length, count decoded bytes while streaming, apply the 64-deep, 100,000-member parse bounds after the byte cap and before RFC 9421 or Web Bot Auth verification, apply connect, idle, and total deadlines, and reject with HTTP 413 rather than truncating. The default cap is 4 MiB, generalizing the attestation task-body cap rather than adding a new number, and a tighter per-feature cap governs. This is a recommendation, not a conformance requirement.

Nobody else gets to write your capabilities document

Two capability fields enumerate relationships a counterparty asserts: media_buy.portfolio.publisher_domains and signals.data_provider_domains are both populated from those counterparties’ /.well-known/adagents.json, which any domain owner publishes unilaterally and without the named agent’s consent. An agent that mirrored every publisher claiming it had handed an unauthenticated stranger a write primitive into its own discovery document — and since the RFC 9421 signing-key path fetches that document unnarrowed under MAX_CAPABILITIES_BYTES, pushing it past 64 KiB cost a victim that signed under that profile signature verification, arriving a cache cycle later with no visible connection to its cause. 3.3 adds a normative byte budget — 8,192 bytes for any single counterparty-asserted field, 16,384 bytes for both together — and declares structural bounds (100 unique entries, 253 characters each) that the conformance storyboard grades in 3.x and the schema enforces in 4.0. No previously-valid document becomes schema-invalid; what changes is what counts as conformant. Because a bounded list would otherwise make a large legitimate network look unauthorized for most of its own inventory, the bound ships with publisher_domains_complete and data_provider_domains_complete — default true, set false when you truncate. Both lists are explicitly non-exhaustive, so a buyer must resolve the publisher named on a product through that publisher’s own adagents.json and must never read absence from the list as a denial.

Account change feed: recognize your own changes

The experimental account change feed (account.change_feed) gains two changes ahead of graduation. A record whose origin.kind is adcp can echo the originating request’s idempotency_key, so a buyer recognizes its own changes on a shared account; the seller includes it only on records served to the principal that sent the request, and every other reader sees the same record without it. And changed_paths is now required when origin.kind is adcp or seller_operator, staying best-effort for seller_system and connected_platform. See list_account_changes.

Reporting subscriptions on the principal (experimental, beta.1 to beta.4)

Reliable Reporting was configured one account at a time, so a new account reported nothing until someone configured it. sync_principal now takes reporting_subscriptions: one registration per feed purpose, scoped to all_authorized_accounts: true or to named account_ids, with a selector that works across sellers (feed_purpose, period_duration, required_finality, optional dimensions, and match). The buyer can work out coverage without asking: a confirmed buy is owed every complete period that starts on or after the later of the subscription version’s accepted_at and the account’s authorization.authorized_at, from the period in which the buy is confirmed through its final period. get_reporting_status reports only exceptions under subscription_coverage. Exceptions remove periods from what is owed and never add any, so a missing report still means an owed period with nothing delivered. Revoked accounts appear in the subscription readback on get_principal, not as silent gaps. A caller’s own sync_accounts delivery config still wins for that account and feed purpose. Sellers list accepted registration tasks in reporting_delivery.configuration_tasks[]. configuration_task stays "sync_accounts" for older clients and is deprecated. In beta.2, offerings publish standard_dimensions so a buyer resolves the selector from the wire, and the readback carries inactive_intervals, per-version configuration in prior_versions, and per-offering gaps and timezone cutovers. Period arithmetic (civil days, elapsed hours), cutovers across different offerings, and authorization chains on re-grant are now pinned. Feature id media_buy.reporting_subscriptions. See Reporting subscriptions and Subscription coverage. Coverage fixes after beta.3 (in beta.4). Two coverage rules change, and both SDKs adopt them:
  • Packages added later. A package added to a confirmed buy carries added_at on get_media_buys, and it acts as that package’s own confirmed_at: the package is owed from the period containing added_at, and resolves its offerings then. Absent, the package was part of the buy at confirmation. Before, a buyer couldn’t tell when a later package started owing, and an SDK that resolved it with the buy over-owed.
  • Reduced grants without get_reporting_status. A grant reduced to tasks that omit get_reporting_status is a loss of reporting authority, exactly like a revocation: the account is listed in accounts_unauthorized[] from the reduction, its owed periods are withheld, and adding get_reporting_status back is a re-grant. A reduced grant that keeps it is still the wind-down grant.
Three changes need no new rule. Schema validation now refuses a period_duration that mixes date and time components (P1DT12H) under a local alignment, as the period rule already did. destination_overrides[] items declare their fields where code generators see them, so generated types are no longer empty objects. Managed-delivery offerings without account_id in primary_keys get their own seller SDK error, SUBSCRIPTIONS_REQUIRE_ACCOUNT_ID_KEY. The reference model now carries the whole IANA tzdata 2026f database, so the vectors can use any zone; new vectors cover Pacific/Auckland, Pacific/Chatham, Asia/Kolkata, and Mexico City across the 2022 end of DST.

Experimental in 3.3

New feature ids are media_buy.spot_lifecycle, media_buy.daypart_granularity, creative.broadcast_loudness, media_buy.hold_policy, media_buy.hold_ranking, media_buy.installment_holds, media_buy.hold_extension, media_buy.delegated_composition, media_buy.collection_cards, media_buy.collection_catalog, brand.collection_links, media_buy.open_opportunities, media_buy.lineage, media_buy.delivery_projection, media_buy.installment_lifecycle, media_buy.collection_lists, media_buy.offline_delivery_metrics, signals.signal_lifecycle, signing.web_bot_auth, account.agent_onboarding, account.requests, media_buy.reporting_subscriptions, creative.live_updates, media_buy.seller_offers, media_buy.execution_readiness, media_buy.gender_targeting, media_buy.measurement_provenance, account.invoice_lines, signals.pricing_groups, signals.delivery_methods, security.profiles, and identity.trust_json. media_buy.purchase_rights and media_buy.installment_selection shipped in beta.1 and are withdrawn, so they are not registered, and media_buy.price_adjustments and media_buy.audience_evidence_targets shipped in the betas and are withdrawn at rc.0. media_buy.offline_delivery_metrics registers the new print_metrics block together with the 3.2 ooh_metrics block. identity.trust_json publishes the trust.json v1 schemas, identifying agents by origin with no keys in the record; the Web Bot Auth profile reads it, and publishers declare nothing (trust.json). Governance budget periods extend the existing governance.campaign cluster, get_principal relationship status extends protocol.principal, and rights channel restrictions extend brand.rights_lifecycle. The creative.evaluator surface on build_creative drops its account-arranged evaluator_id source form and withdraws the list_evaluators follow-on: sources are now inline exemplars or an allowlisted agent_url, and a seller’s house evaluator is an agent it lists in creative_policy.accepted_verifiers[] (migration). Reliable Reporting carries a new breaking-change notice: older superseded snapshots may be compacted no earlier than the first minor after November 20, 2026. The per-surface status table is in the release notes. rc.0 adds media_buy.installment_refinement and media_buy.installment_creative_assignment (New in rc.0). Beta.5 adds media_buy.match_keys (above), which stays experimental at 3.3 GA and extends the experimental Product.identity declaration and TMP provider registration with match keys.

Clarifications and conformance

  • Broadcast TV certification. sales-broadcast-tv now certifies one authorized TV transaction on a guaranteed or a non-guaranteed fixed-price path. Existing claimants should expect new checks; 1.0.x claims have a grace window.
  • Signing buyers serve get_adcp_capabilities at their agent URL, because request-signature discovery starts there. See request signing.
  • Fixed-rate certification. The sales_fixed_rate storyboard grades the new sales-fixed-rate specialism; its optional hold phases run only when the seller advertises the force_media_buy_confirmation controller scenario. The specialism is stable from beta.5, and a passing claim counts toward the AAO Verified media-buy badge.
  • Hold-failure testing. The experimental force_hold_unavailable controller scenario lets a runner reach the all-or-none hold-failure path; the beta.4 hold storyboards use it (New in beta.4).
  • Storyboard and schema fixes. Storyboards that seed a sandbox fixture account send sandbox: true explicitly, and validate_input warning items now declare field as a string, so a warning whose field is not a string fails validation.
  • New storyboards. media_buy_seller/unprovisioned_account_reference (advisory until runner capability 14.1.0), and capability-gated media_buy_seller/stable_account_id, media_buy_seller/definition_pin_drift, governance/budget_periods, media_buy_seller/property_delivery_reporting, media_buy_seller/installment_property_delivery_reporting, media_buy_seller/outcome_target_vendor_metric, and media_buy_seller/outcome_target_event_cost.
The storyboard changes affect grading, not the wire.

Already shipped in 3.2.2, 3.2.3, and 3.2.4

These merged on main during the 3.3 cycle and were also released on the 3.2 line. They appear again in the 3.3.0 changelog but are not new to 3.2.4 adopters.
  • 3.2.2: the account-reference clarification and the trust-docs consistency fixes (v3.2.2).
  • 3.2.3: the A2A operation-resolution security errata (GHSA-2pm6-6mc8-8xcm) with hardening at SHOULD, the adagents.json agent-URL clarification, the evaluator feature-membership fix, storyboard capability gates for wholesale discovery and finalize replay, the polling-based sales-guaranteed path, the validate_input gates, and the acceptance-policy sandbox account (v3.2.3).
  • 3.2.4: the experimental REVISION_UNREADABLE reporting issue, requires: [controller] on controller-seeded storyboards and five storyboard fixes, request-signing step-1 vectors with the negative/026 re-code, complete profile-3.2 mirrors and step-5 canonicalization vectors, envelope composition and the bundled provenance hoist, the product channel-declaration guidance, and the principal-layer buyer walkthrough (v3.2.4).

What requires adopter attention

Withdrawn from 3.3, planned for 4.0

Three features are not part of 3.3. All three add terms to commercial_terms, which is held closed until 4.0. A buyer must not be bound by terms it cannot read: terms_digest covers every member of commercial_terms, including members under the open schemas inside it, and a party that cannot interpret every member must not accept the terms (Verify terms independently). 4.0 gives commercial_terms a declared extension point with must-understand and brings them back (adcp#8501). The designs are kept for 4.0: see Planned for 4.0. The closed-schema triage adds four more fields to the 4.0 list at rc.0, because each would extend the commercial terms held closed until 4.0: metric_id on performance standards, price_adjustments, counting_mechanisms, and target_audiences on purchases (New in rc.0). The metric_id withdrawal (#8854) is in review, not in rc.0.

In review for 3.3

Open 3.3 proposals are not part of any prerelease until they merge. Six working-group decisions are ratified or accepted, and their normative text has merged:
  • Agent identity is an origin (DR-0023). Merged: the Web Bot Auth profile #7894, Web Bot Auth identities and the deprecation of the RFC 9421 brand.json profile #8162, first-contact binding #8168, the buyer walkthrough and migration guide #8172, the experimental production security profile #8155, seller onboarding posture #8170, and the R7/R8 erratum #8219. request_account #8293, then the single account write and reporting subscriptions (#8543: #8551, #8552).
  • Responses conform to the served release (DR-0024, #8117). Merged. The rule is in Serving an older pin; advisory grading of undefined properties merged in #8156 (beta.4).
  • Demand-side grants (DR-0025). Merged: #8157, #8169.
  • JWS artifacts use the Web Bot Auth key directory (DR-0026, #8299). Merged. It amends DR-0023: governance contexts, designated-task response signatures, and rights attestations from a listed origin verify against its key directory in 3.3.
  • Seller revisions advance on every committed change (DR-0031, #8159). Merged; recorded in #8389. See Tightened rules.
  • Verifiers bundle the Public Suffix List (DR-0037, #8702). Ratified 2026-11-02 and merged for beta.5. Verifiers compute eTLD+1 with a bundled list, never fetched at runtime.
Records DR-0027 to DR-0030 (mutation outcome, sales-fixed-rate, delivery projection, and lineage) describe surfaces merged for beta.0 and are accepted. DR-0028’s sales-fixed-rate is stable from beta.5. DR-0034 (major-only requests) is accepted, and DR-0036 (schemas open by default) was decided at the 2026-11-09 working-group session. The open proposals are listed in the 3.3 beta program.

Start here

  1. Read the 3.3 prerelease program.
  2. Follow Migrating from 3.2 to 3.3.
  3. Choose the exact package and support level in Choose your SDK.
  4. Use the Release Notes for the cumulative record.