Skip to main content
Autonomy settings let a buyer control how independently the agent operates on a campaign. The preference persists across sessions, so the buyer does not have to repeat it each time they start a conversation.

Two dimensions

Each campaign has two independent autonomy dimensions:

Three modes

Each dimension accepts one of three mode values:

Setting autonomy via the API

Pass the autonomy field to the campaign create or update operation. Each dimension is optional — omitting a dimension leaves its current value unchanged.
At least one dimension must be present when the autonomy object is supplied.

Reading the stored preference

The response shape differs between the V2 REST API and the V3 MCP agent surface.

V2 REST API

The V2 REST campaign response includes autonomy only when at least one dimension has been explicitly set. Each present dimension is returned as a plain enum string:
An absent dimension means no preference has been saved and the effective mode is manual. The autonomy object itself is absent from the response when neither dimension is set.

V3 MCP agent surface

The V3 campaign workspace always returns both dimensions, each as an object: A source of inherited means no preference has been saved and the dimension is using its default (manual). A source of overridden means the buyer explicitly set the mode.

Scope and persistence

Autonomy is a per-campaign setting. Changing it on one campaign does not affect other campaigns for the same advertiser or account. The preference survives session restarts and is included in every campaign read response.