API Reference › Google Ads › update_pmax_audience_signal

update_pmax_audience_signal

Google Ads Write

🚨 **IF THIS TOOL RETURNS A QUOTA ERROR:** - The error message will include a clickable upgrade link - Show the FULL error message to the user (it contains the upgrade link) - DO NOT attempt to work ar

Endpoint

POST https://api.adspirer.ai/api/v1/tools/update_pmax_audience_signal/execute

Headers

Description

🚨 **IF THIS TOOL RETURNS A QUOTA ERROR:** - The error message will include a clickable upgrade link - Show the FULL error message to the user (it contains the upgrade link) - DO NOT attempt to work around the error or use alternative data - DO NOT create campaigns or perform actions without valid tool data - STOP and direct the user to upgrade via the provided link Update the segment composition of an existing PMax audience IN PLACE (#325). USE THIS INSTEAD OF REMOVE + ADD when you want to change which audiences are in a signal — for example, to merge in a new Customer Match list while keeping existing in-market interests. Updating in place avoids the "audience with this name already exists" error that comes from removing a signal and re-adding under the same name. **Workflow:** 1. Call get_pmax_audience_signals → returns signals with their `audience` resource names AND current `composition` 2. Build a new audience_config dict with the FULL desired composition (this REPLACES, not merges — copy the current composition then add or remove segments as needed) 3. Call this tool with the audience_resource_name + new audience_config **Parameters:** - audience_resource_name: from get_pmax_audience_signals (the `audience` field on each signal — NOT the signal's own resource_name) - audience_config: same shape as add_pmax_audience_signal **Execution time:** 2-5 seconds

Request body

All tool arguments are wrapped in an arguments object.

FieldTypeDescription
audience_resource_namestring requiredThe audience resource name to update. Get from get_pmax_audience_signals — it's the `audience` field on each signal (NOT the signal's own resource_name). Example: 'customers/1234567890/audiences/12345'
audience_configobject optionalREPLACES the audience's segment composition. Same shape as add_pmax_audience_signal: keys 'in_market_audience_ids' (List[int]), 'affinity_audience_ids' (List[int]), 'custom_audience_ids' (List[str]), 'user_list_ids' (List[str]). Shape-tolerant (#559): synonym keys, flat, and nested 'segments' shapes are normalized for you. To MERGE rather than replace, fetch the current composition from get_pmax_audience_signals first and combine with the new segments. Example: {'in_market_audience_ids': [80432, 80210], 'user_list_ids': ['customers/123/userLists/456']}
customer_idstring optionalGoogle Ads customer ID. Required for multi-account users. Get from get_connections_status.

Example request

{
  "arguments": {
    "audience_resource_name": "string",
    "audience_config": {},
    "customer_id": "string"
  }
}

Example responses

200 — Success

{
  "success": true,
  "data": {
    "text": "(tool-specific textual output for update_pmax_audience_signal)",
    "quota": {
      "used": 42,
      "limit": 150,
      "tier": "plus",
      "period_end": "2026-05-01"
    }
  },
  "tool": "update_pmax_audience_signal"
}

400 — Tool-level error (bad arguments / multi-account selection)

{
  "success": false,
  "error": "You have 25 meta_ads accounts connected. Please specify which account to use by passing the ad_account_id parameter:\n  - Acme Holdings (ad_account_id=\"act_123456789\")\n  - Acme EU (ad_account_id=\"act_987654321\")",
  "is_error": true,
  "tool": "update_pmax_audience_signal"
}

402 — Quota exhausted

{
  "success": false,
  "error": "\ud83d\udea8 Monthly limit reached (150/150 tool calls on Plus tier).\nUpgrade to Pro at https://adspirer.ai to keep building.",
  "is_error": true,
  "tool": "update_pmax_audience_signal",
  "quota": {
    "used": 150,
    "limit": 150,
    "tier": "plus",
    "period_end": "2026-05-01",
    "upgrade_url": "https://adspirer.ai"
  }
}

Try it live

Interactive: Swagger UI

Machine-readable: OpenAPI 3.1 spec · llms-full.txt

More tools: Google Ads · All tools

Adspirer REST API — get an API key at adspirer.ai/keys · adspirer.ai