Skip to main content

​
AdCP 3.2 prerelease history

AdCP 3.2 is generally available as release 3.2.1 (published 2026-09-30), wire pin "3.2". The number 3.2.0 was never released. Move integrations pinned to a 3.2 beta or RC to "3.2" and to the stable SDKs: TypeScript @adcp/sdk@14.0.0 and Python adcp==8.0.0. Start with What’s new in AdCP 3.2 and Migrating from 3.1 to 3.2.
This page is the record of the 3.2 prerelease cycle. Every prerelease remains an immutable, signed checkpoint, so adopters who pinned one can still reproduce and debug their results.

​
Changes between RC.7 and 3.2.1

Adopters moving from 3.2.0-rc.7 to 3.2.1 should check these changes, which landed during the GA freeze:
  • Seller-optimized budgets. media_buy.features.seller_optimized_budget now covers only the core shared-budget contract and media-buy pacing. Package budget caps, minimum-spend targets, and package pacing need seller_optimized_package_budgets, seller_optimized_min_spend_targets, and seller_optimized_package_pacing. An RC seller that declared the parent and honors those controls must add the matching sub-capabilities, or buyers’ requests carrying them are rejected with UNSUPPORTED_FEATURE. Core sellers must accept omitted or even pacing and may reject asap or front_loaded.
  • Delivery reporting timezone. get_media_buy_delivery dates and daily_breakdown[].date are calendar dates in the products’ reporting_capabilities.timezone, with the optional reporting_period.timezone echo. RC wording required exact UTC day boundaries. A dated or windowed (time_granularity) request spanning more than one reporting timezone is rejected with VALIDATION_ERROR.
  • Account change feed. list_account_changes is now experimental (account.change_feed). Sellers implementing it list account.change_feed in experimental_features.
  • views goal definition. The optimization-goal views metric now matches delivery metrics (content views toward the billable view threshold), not viewable impressions. Use viewable_rate for viewability.
  • Conformance. 27 new content-digest-covered request-signing vectors under test-vectors/request-signing/profile-3.2/, a restructured seller_optimized_budget storyboard (1.1.0) with two new scenarios, and storyboard fixes for reporting_core, get_creative_features_idempotency, non-guaranteed sellers, and cross-phase generated IDs.

​
Checkpoints

TypeScript “RC.N” means @adcp/sdk@14.0.0-rc.N. Go module versions are not AdCP versions: adcp/v3@v3.2.1 embeds 3.2.0-rc.1 schemas and is not AdCP 3.2.1.

​
Version strings

The artifact version, wire pin, and documentation selector are related but not interchangeable: Prerelease pins are exact. A buyer pinned to "3.2-rc.7" never silently negotiates to another prerelease, and a stable "3.2" pin never resolves onto a prerelease. A peer that still advertises only a prerelease pin must move to "3.2" before stable 3.2 buyers can reach it. If you keep running a pinned prerelease compliance bundle for regression evidence, run it against a staging endpoint. Do not weaken production authentication to accommodate a prerelease runner.

​
Artifact retention

Release-candidate and stable artifacts are never retired. Superseded 3.x beta artifacts were retired from the repository and runtime image on 2026-09-14; only the 3.2.0-beta.11 schema bundle stays hosted, backing the frozen 3.2-beta documentation snapshot. Earlier beta URLs resolve from the artifact CDN on a best-effort basis. The prerelease documentation snapshots stay reachable by URL after their selectors leave the version picker.