{"id":103314,"plugin_id":"plugin_asdk_app_6aedf6ea2fac819180910f8b98663c77","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-18T06:19:20.264Z","digest":"901b979d6f1924c834725c5c742fc428b64e7a8101331f7f6a1c3b3d67406b6d","against":null,"payload":{"description":"Clay ad syncs — push an audience segment to ad platforms (LinkedIn, Meta, Google, Bing, Reddit, Vibe) as a custom audience. Use to create, edit, start, pause, or map the fields of an ad sync, or to check its status, match rate, or run history.","included_files":[{"relative_path":"field-mapping.md","size_in_bytes":3560}],"name":"ad-syncs","skill_md_contents":"---\nname: ad-syncs\ndescription: Clay ad syncs — push an audience segment to ad platforms (LinkedIn, Meta, Google, Bing, Reddit, Vibe) as a custom audience. Use to create, edit, start, pause, or map the fields of an ad sync, or to check its status, match rate, or run history.\n---\n\n# Ad syncs\n\nBefore using this skill, read the `clay` entry skill if you haven’t already this session, and follow its access guidance.\n\nAn ad sync pushes an audience segment to ad accounts on ad platforms, called its destinations. Each\nplatform matches the records and builds an audience to advertise to.\n\n## Supported commands\n\n- `clay ad-syncs list [--limit <n>] [--cursor <cursor>]`\n- `clay ad-syncs get <adSyncId>`\n- `clay ad-syncs get-by-source --source-id <segmentId> --entity-type <people|companies>`\n- `clay audiences get <segmentId>`\n- `clay ad-syncs create --name <name> --source-id <segmentId> --entity-type <people|companies> --schedule-type <ONE_TIME|RECURRING>`\n- `clay ad-syncs update <adSyncId> [--name <name>] [--schedule <ONE_TIME|RECURRING>] [--tier <PREMIUM|STANDARD>]`\n- `clay app-accounts list --filter type=<provider>-ad-audience`\n- `clay ad-syncs ad-accounts list <appAccountId> --provider <provider>`\n- `clay ad-syncs destinations create <adSyncId> --provider <provider> --app-account-id <appAccountId> --ad-account-id <accountId> [--ad-user-data-consent <status> --ad-personalization-consent <status>]`\n- `clay ad-syncs destinations update <adSyncId> --destination-id <destinationId> [--app-account-id <appAccountId>] [--ad-account-id <accountId>] [--ad-user-data-consent <status>] [--ad-personalization-consent <status>]`\n- `clay ad-syncs destinations delete <adSyncId> --destination-id <destinationId>`\n- `clay ad-syncs field-mapping update <adSyncId> --input '<json>'`\n- `clay ad-syncs pause <adSyncId>`\n- `clay ad-syncs trigger <adSyncId>`\n- `clay ad-syncs runs list <adSyncId> [--limit <n>]`\n\nUse only the subcommands `clay ad-syncs --help` lists; some ship to only some channels. When one is\nmissing, the user does that step in the Clay app, from the sync's `url`. Run\n`clay ad-syncs <subcommand> --help` before a subcommand's first use. It has the exact output\nshape, value sets, and error codes. `<provider>` is `LinkedIn`, `Meta`, `Google`, `Bing`, `Reddit`,\nor `Vibe`, written in lowercase inside `type=<provider>-ad-audience` (e.g.\n`type=linkedin-ad-audience`). An `<accountId>` is an `accountId` from `ad-accounts list`, and a\n`<destinationId>` is a `providerSyncConfigs[].id` from `get`.\n\n## Limits\n\n- You can always create an ad sync, and edit it while it is a draft or paused.\n- You cannot delete an ad sync: the user deletes it in the Clay app. A segment can have only one ad\n  sync, so create one only for a segment the user confirmed.\n- Pause a running sync only when the user asks. Before running `pause`, tell them what pausing does\n  (see Statuses) and ask them to confirm, even when they asked for it.\n- Start or resume a sync with `trigger` only when the user explicitly asks; follow Start.\n\n## Schedules\n\n- `ONE_TIME`: it exports once, when the user starts it.\n- `RECURRING`: it syncs continuously to its destinations, so they stay up to date with the people\n  or companies the user wants to target.\n\n## Statuses\n\nTell the user the label in parentheses, not the raw value.\n\n- `DRAFT` (Draft): not started yet.\n- `PROCESSING` (Processing): an export is running, including enrichment when the sync has a tier.\n- `ACTIVE` (Active): a recurring sync whose latest export reached every destination. It exports\n  again on its schedule.\n- `DONE` (Exported): a one-time sync that reached every destination.\n- `WARNING` (Warning): some destinations failed. A one-time sync reached only some of them, or a\n  later export of a recurring sync failed on at least one, and the sync stays live. `runs list`\n  shows which destinations failed.\n- `FAILED` (Failed): a one-time sync that failed on every destination, or a recurring sync whose\n  first export failed on any destination.\n- `BULK_ENRICHMENT_FAILED` (Enrichment failed): the enrichment step failed.\n- `PAUSED` (Paused): the user paused it. Clay stops enriching new records in the segment, so it\n  stops spending credits, and stops pushing new records to the ad platforms. The audiences already\n  on the platforms stay as they are until the user resumes the sync in the Clay app.\n\n## Create\n\nConfirm each choice with the user before running the command that makes it.\n\n1. **Draft.** Read the segment's `entityType` with `clay audiences get <segmentId>`, then run\n   `clay ad-syncs get-by-source --source-id <segmentId> --entity-type <entityType>`. If it returns a\n   sync, use that one. If it returns `not_found`, ask whether the sync should run once or on a\n   recurring schedule, and create it:\n\n   ```bash\n   clay ad-syncs create --name \"<name>\" --source-id <segmentId> --entity-type <entityType> --schedule-type <ONE_TIME|RECURRING>\n   ```\n\n2. **Accounts.** For each platform, run `clay app-accounts list --filter type=<provider>-ad-audience`.\n   If it returns one connection, pick it. If it returns more than one, list them by name and ask the\n   user which to use. Don't check any connection's ad accounts before the user picks one, even if\n   you expect only one to work.\n\n   You MUST check the picked connection before using it, every time, including when it is the only\n   one: run `clay ad-syncs ad-accounts list <appAccountId> --provider <provider>`. Never pass an\n   `--app-account-id` to any command until that check has succeeded for it in this conversation. If\n   the check errors, don't use the connection: tell the user it couldn't load its ad accounts and\n   ask them to pick another one.\n\n   An ad account is usable when `canManageAudiences` is true, `restrictions` is empty, and it has\n   not already been added to this ad sync: compare its `accountId` with the\n   `providerSyncConfigs[].providerAdAccount.id` values from `clay ad-syncs get <adSyncId>`. If there\n   are none, the user sets them up in the Clay app from the sync's `url`. Continue once they're done.\n\n3. **Destinations.** Ask which ad accounts to advertise to, then add each one:\n\n   ```bash\n   clay ad-syncs destinations create <adSyncId> --provider <provider> --app-account-id <appAccountId> --ad-account-id <accountId>\n   ```\n\n   Company syncs go to LinkedIn only. For Google, ask the user for both consent values and add\n   `--ad-user-data-consent <status> --ad-personalization-consent <status>`. Send `UNSPECIFIED` if\n   they don't track consent.\n\n4. **Enrichment tier** (people syncs only). Best match rates is\n   `clay ad-syncs update <adSyncId> --tier PREMIUM`, Good match rates is\n   `clay ad-syncs update <adSyncId> --tier STANDARD`, and none means skipping this step. A tier\n   costs credits and can't be changed once set. To see what each tier costs, the user opens the\n   sync's `url` in the Clay app.\n\n5. **Field mapping.** Read `field-mapping.md` and follow it.\n\nThen give the user the sync's `url` so they can review it. If they want to start it now, follow\nStart; otherwise they start it in the Clay app.\n\n## Start\n\n`trigger` starts a draft's first export, runs a one-time sync again, or resumes a paused sync.\n\n**Before confirming**, run `clay ad-syncs get <adSyncId>`. Tell the user:\n\n- each destination's platform and ad account;\n- what the schedule does: `ONE_TIME` exports once, `RECURRING` keeps syncing;\n- for a sync with a tier, that Enhanced Matching charges credits for each record it matches.\n\n**Always confirm with the question tool before running `trigger`.** You can't tell in advance\nwhether a trigger will be held for approval, so an approval request, if one follows, is a second\ncheck, not a replacement. After the user confirms, run `get` again; if anything you described\nchanged, tell the user and confirm again.\n\n**After the command:**\n\n- On `approval_required`, nothing has started yet: present the request as the `cli` skill describes\n  and don't run the command again.\n- On `validation_error`, report the reason in product terms (no destinations, a missing field\n  mapping, an empty segment, or an export already running) and offer to fix what you can.\n- On success, give the sync's `url` and say that `clay ad-syncs runs list <adSyncId>` shows each\n  destination's progress. Never retry automatically.\n\n## Edit\n\nCheck `adSync.status` with `clay ad-syncs get <adSyncId>` first. `DRAFT` and `PAUSED` syncs can be\nedited. A running sync (`PROCESSING`, `ACTIVE`, or `WARNING`) has to be paused first. Tell the\nuser it has to be paused and what pausing does, and ask them to confirm before running\n`clay ad-syncs pause <adSyncId>`. `DONE`, `FAILED`, and `BULK_ENRICHMENT_FAILED` syncs\ncan't be edited.\n\n- Rename: `clay ad-syncs update <adSyncId> --name \"<name>\"`\n- Change the schedule: `clay ad-syncs update <adSyncId> --schedule <ONE_TIME|RECURRING>`\n- Set a tier, only if it has none: `clay ad-syncs update <adSyncId> --tier <PREMIUM|STANDARD>`\n- Add a destination: follow steps 2 and 3 of Create.\n- Change the ad account for a destination: `clay ad-syncs destinations update <adSyncId> --destination-id <destinationId> --ad-account-id <accountId>`,\n  adding `--app-account-id <appAccountId>` if that ad account is under another connection. The\n  synced audience will then exist in a different ad account, so confirm the change with the user\n  first. A Google destination needs both consent flags again when its ad account changes.\n- Switch the connection a destination syncs through, keeping its ad account: `clay ad-syncs destinations update <adSyncId> --destination-id <destinationId> --app-account-id <appAccountId>`\n- Remove a destination, on drafts only: `clay ad-syncs destinations delete <adSyncId> --destination-id <destinationId>`\n- Change the field mapping: follow `field-mapping.md`.\n\nA paused sync stays paused. The edit takes effect once the user resumes it in the Clay app.\n\n## Read\n\n1. Find the sync with `clay ad-syncs list`, paging with `--cursor <cursor>`, or with\n   `clay ad-syncs get-by-source --source-id <segmentId> --entity-type <people|companies>` when the\n   user names the segment.\n2. Read its setup with `clay ad-syncs get <adSyncId>`.\n3. Read its results with `clay ad-syncs runs list <adSyncId> --limit 100`. The default returns only\n   the 20 newest runs across all destinations, so a destination's latest run can be missing without\n   the higher limit. If a destination has no run in the result, say so rather than guessing. Report\n   each destination's latest run in plain words (status, match rate, and audience size), and link\n   the sync's `url`. Google and Bing have no single audience size: report the size for each\n   network in the run's `google` or `bing` object. For a failed run, relay its `errorMessage`, which says what went wrong\n   and what the user can do about it.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}