> ## Documentation Index
> Fetch the complete documentation index at: https://docs.erdo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Audience observation and targeting

> Let Erdo configure how an existing Google Ads campaign uses its audiences.

Erdo can set and verify how a campaign or ad group uses audience lists. Ask it to
review retargeting for the development. It checks the connected account, proposes
the required setup through your approval policy, and reads the result back.

**Observation** keeps the campaign able to reach new people while adding audience
reporting and bidding signals. **Targeting** restricts ads to members of the linked
audiences. Adding a list without explicitly checking this setting can narrow an
existing prospecting campaign.

The mode action changes only the audience dimension. It preserves other targeting
dimensions, budgets, bids and campaign statuses. Google permits targeting settings
at either the campaign or ad group level; Erdo refuses an ad group update when its
parent campaign already holds those settings. It never moves settings between
levels automatically.

## API and MCP

`POST /v1/paid-media/campaigns/{campaign_id}/audience-mode` takes:

```json theme={null}
{
  "provider": "google_ads",
  "customer_id": "1234567890",
  "mode": "observation",
  "reason": "Preserve prospecting reach before linking visitor audiences"
}
```

Include `adgroup_id` to change one ad group. The MCP equivalent is
`erdo_set_paid_media_audience_mode`, with `campaign_id` in its input.

The response is `pending_approval` with an approval ID unless your standing policy
allows execution. A completed action verifies the setting through a fresh provider
read. If verification fails after the write, Erdo reports that uncertainty; re-read
the account before submitting another change.

## CLI

```bash theme={null}
erdo paid-media audience-mode 23456789012 \
  --customer-id 1234567890 --mode observation
```

Use `--adgroup-id` for an ad group and `--reason` to explain the change on its
approval card. These commands use the same approval policy as the agent.

A configured audience and a verified mode establish configuration. Audience-level
delivery needs separate provider evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.