Meta Retargeting Audience Builder

# Meta Retargeting Audience Builder

Design and create one reviewed Meta custom audience for retargeting.

## Required Aident Actions

- <action-tag>composio:metaads_tools:metaads_create_custom_audience</action-tag> (required inputs: account_id, name, subtype): Create a new custom audience using the Meta Marketing API. Supports various types of custom audiences including customer lists, website visitors, and app users.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

## Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply the source-derived guidance below to create a concrete plan. Resolve ambiguity before invoking an Action.
3. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

## Source-Derived Guidance

- Collect the Meta account, audience purpose, subtype, source population, inclusion window, exclusions, name, and privacy basis.
- Confirm that the supplied audience data and intended use comply with consent, platform, and regional requirements.
- Present the complete audience definition and target account for explicit confirmation.
- Use composio:metaads_tools:metaads_create_custom_audience once with the approved inputs.
- Verify the returned audience ID and status without claiming that campaigns, ads, or other platforms were configured.

## Execution Boundaries

- Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
- Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
- Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
- Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

## Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

## Attribution

This Skill adapts the reviewed upstream workflow. See [UPSTREAM.md](UPSTREAM.md) for the pinned source and [LICENSE.txt](LICENSE.txt) for the preserved license.