audience_id | string | Yes | - | Custom audience ID, e.g. from meta_list_custom_audiences |
action | string or SelectableOption | No | update | ’update’ changes the provided fields; ‘delete’ permanently deletes the audience (it is removed from any ad sets still using it) and ignores all other fields. |
name | string | No | - | New audience name |
description | string | No | - | New audience description |
rule | object or string | No | - | Replacement website-audience rule, sent to Meta as-is. Same Audience Rules shape as meta_create_custom_audience: {‘inclusions’: {‘operator’: ‘or’, ‘rules’: [{‘event_sources’: [{‘type’: ‘pixel’, ‘id’: ‘<PIXEL_ID>’}], ‘retention_seconds’: 2592000, ‘filter’: {…}}]}}. Only valid for website custom audiences. |
retention_days | integer | No | - | New lookback window in days (Meta caps this per audience type, e.g. 180 for website, 365 for engagement) |
opt_out_link | string | No | - | URL where people can opt out of the audience |
customer_file_source | string or SelectableOption | No | - | Source of customer data, for customer-list audiences |
allowed_domains | array of string | No | - | Domains allowed as traffic sources for the audience |
tags | array of string | No | - | Tags to organize the audience |
use_in_campaigns | boolean | No | - | |
product_set_id | string | No | - | Product set ID, for product audiences |
lookalike_spec | object or string | No | - | Lookalike spec JSON, for lookalike audiences, e.g. {“type”: “similarity”, “origin_audience_id”: “<ID>”, “country”: “US”} |