---
title: "Add an audience signal to an asset group"
method: POST
path: "/api/v1/tools/google_add_audience_signal/execute"
tags: ["Google Ads"]
---

# Add an audience signal to an asset group

`POST /api/v1/tools/google_add_audience_signal/execute`

## Request

- Base URL: `https://adako.ai`
- URL: `https://adako.ai/api/v1/tools/google_add_audience_signal/execute`
- Auth: HTTP bearer

Adds an audience as a signal on a Performance Max asset group. A signal tells Google who to start with; it is not targeting and Google will serve well outside it.
Use when: the account has a genuinely useful audience — a customer list, a converter list, a close in-market segment — and the user picked it from google_search_audiences.
Do not use when: the user expects the campaign to stay inside that audience. It will not. If they want strict targeting, Performance Max is the wrong campaign type and a Search or Display campaign is the honest answer.
Pass an audience id from google_search_audiences. Adding a second identical signal is refused.
If you are unsure which account, campaign or period the user means, ask them — do not guess ids or dates.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object, required
    - `customer_id` string: Google Ads customer id (10 digits, dashes optional). Omit to use the primary account; list_connected_accounts shows the valid ids.
    - `asset_group_id` string, required: Asset group id as a string of digits.
    - `audience_id` string, required: Audience id from google_search_audiences — only an entry from its `audiences` list. The `interest_segments` and `user_lists` it also returns are different kinds of id and Google refuses them here with INVALID_COMBINED_AUDIENCE_ID (seen live 2026-09-18). An account with an empty `audiences` list has no audience to signal with; say so rather than passing an interest id.
    - `idempotency_key` string: Optional caller-supplied key; identical keys never execute twice.

## Response `200`

The tool ran. A write returns proposal_id and approve_url while the change waits for approval.

- SuccessEnvelope
  - `success` unknown, required
  - `tool` string, required
  - `data` object, required: Machine-readable result.
  - `markdown` string, required: The same result written for a person or a model.
  - `quota` Quota: Task usage for the current billing period.
    - `plan` string
    - `used` integer
    - `limit` integer
    - `period_end` string
    - `upgrade_url` string
  - `proposal_id` string: Present for writes. Nothing changes on the ad platform until it is approved.
  - `approve_url` string: Where a person approves the proposal.
  - `request_id` string, required

## Other responses

- `400`: Invalid arguments, or the ad account could not be resolved.
- `401`: Missing, invalid, revoked or expired API key.
- `402`: Monthly task quota used up, or the plan does not include this tool.
- `403`: The connected ad account lacks the access level this tool needs.
- `404`: Unknown tool name.
- `409`: Not connected, reconnect needed, confirmation required, a proposal already pending or no longer pending, an identical create that failed earlier today (proposal_failed_before), a create that duplicates an approved one (duplicate_create), the ad-account limit of the plan reached (account_limit), or an Idempotency-Key reused with different arguments.
- `429`: Rate limited by Adako or by the ad platform. See Retry-After.
- `500`: Unexpected error inside Adako.
- `502`: The ad platform returned an error.

---

[API](https://skmtc.dev/adako/apis/adako-rest-api.md) · [All operations](https://skmtc.dev/adako/apis/adako-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/adako/apis/adako-rest-api/revisions/59ee60d48a56?raw)