Amazon’s sponsored-ads tools have three different release schedules

What changed

Keep those dates separate when planning adoption. Review data permissions and proposed campaign actions; beta performance comparisons are vendor claims, not a forecast for your account.

Create a readiness list for Data Manager with the data owner, permissions and intended reporting use. Keep campaign intelligence and automated optimization as separate milestones, with access checks when each becomes available. Do not remove existing controls or reporting simply because a future system is expected to replace part of the workflow.

The source describes Data Manager as the near-term data-connection opportunity, campaign intelligence as an October milestone and automated optimization as a January 2027 milestone. These are dependencies in an operating plan, not three switches that can necessarily be enabled together. Teams should avoid writing an implementation brief that assumes future functionality is already handling data quality or campaign decisions.

Separate the preparation work by owner: data access and reconciliation belong with the relevant data team, diagnostic use cases with campaign managers, and automated actions with whoever approves operational changes. Define the reporting or decision each tool is intended to improve. When access arrives, compare the actual product with the announced scope and update the plan. This keeps a useful roadmap from turning into an unsupported commitment about when manual work, reporting or approval steps can be removed.

Why it matters for advertisers

The three schedules affect planning differently. Teams can investigate available data connections now, while features announced for later periods need to remain explicit dependencies rather than assumptions inside the current operating process.