Asc Apple Ads

This handles the full Apple Search Ads workflow through the asc CLI, from auth setup and org resolution to campaigns, ad groups, keywords, and reporting. The source gives you the ground rules up front: Apple Ads auth is separate from App Store Connect, never guess payload fields, and don't touch live accounts until the user confirms the org and resource type. It covers both stored profiles and environment variable auth, includes read-only discovery commands for apps and geo targeting, and shows you how to use raw API requests when Apple ships features faster than the CLI updates. The live test checklist is practical: create paused resources with timestamped names, save the IDs, and clean up only what you created.

skills.sh installs: 3.2K
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add rorkai/app-store-connect-cli-skills --skill asc-apple-ads --agent claude-code

Installs into .claude/skills of the current project.

Files

asc Apple Ads

Run Apple Ads work through asc ads. Apple Ads credentials are separate from App Store Connect credentials; asc auth login does not configure Ads.

Pick the API first

Direct asc ads <resource> ... commands use Apple Ads Platform API v1 and an ad account ID.
Deprecated Campaign Management API v5 commands live under asc ads v5 ... and use an organization ID. Apple retires v5 on January 26, 2027.
Never substitute an org ID for an ad account ID. The CLI keeps them separate.
Run the exact leaf command with --help before building a request file. Platform v1 payloads and response envelopes differ from v5; the CLI does not translate them.
For non-interactive pipelines, pass --file - to read a JSON request body from stdin; the CLI rejects it when stdin is a terminal.
Resource, report, upload, and raw commands emit lossless JSON. Use jq for projections instead of asking for table or markdown output.