
Asc Apple Ads
- 1.5k installs
- 948 repo stars
- Updated July 31, 2026
- rorkai/app-store-connect-cli-skills
asc-apple-ads is a Claude Code skill that operates Apple Search Ads through App Store Connect CLI workflows to bid on keywords, manage campaigns, and measure paid install lift for developers launching iOS apps.
About
asc-apple-ads is an agent skill from rorkai/app-store-connect-cli-skills for managing Apple Ads via the asc CLI, covering separate Apple Ads authentication, org lookup, campaigns, ad groups, ads, keywords, reports, and raw API calls with safe live testing. Ground rules require running asc ads --help before scripting, using --output json for automation, supplying org ID via --org or ASC_ADS_ORG_ID, and never guessing payload fields—Apple Ads request JSON must come from documented files. Apple Ads auth is distinct from App Store Connect auth; asc auth login does not configure asc ads. Developers reach for asc-apple-ads when automating keyword bids, campaign creation, or install performance reports during iOS launch windows without hand-crafting unsigned API requests.
- CLI-driven Apple Search Ads management
- Keyword campaign setup and budget tuning
- Pairs with App Store Connect automation stack
- Supports launch acquisition experiments
- Reports ad metrics alongside store performance
Asc Apple Ads by the numbers
- 1,518 all-time installs (skills.sh)
- +99 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #385 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-apple-adsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.5k |
|---|---|
| repo stars | ★ 948 |
| Last updated | July 31, 2026 |
| Repository | rorkai/app-store-connect-cli-skills ↗ |
How do you manage Apple Search Ads from CLI?
Operate Apple Search Ads through App Store Connect CLI workflows to bid on keywords, manage campaigns, and measure paid install lift during iOS app store launch windows.
Who is it for?
iOS developers automating Apple Search Ads campaigns and keyword reports via the asc CLI during app store launch windows.
Skip if: Android Google Ads campaigns or teams without asc CLI installed and Apple Ads org credentials configured separately from App Store Connect.
When should I use this skill?
A task involves asc ads commands, Apple Search Ads campaigns, keyword bidding, org lookup, or JSON report automation for iOS apps.
What you get
asc ads campaign configs, keyword bid scripts, JSON performance reports, and validated Apple Ads API request payloads.
- Campaign and keyword configs
- JSON performance reports
- Validated Apple Ads API payloads
Files
asc Apple Ads
Use this skill when a task involves Apple Ads or asc ads.
Ground Rules
- Run
asc ads --helpor the specific subgroup help before scripting a command. - Apple Ads auth is separate from App Store Connect auth.
asc auth logindoes not configureasc ads. - Use JSON output for automation:
--output json. - Most commands need an org ID. Prefer
--orgfor one-off commands andASC_ADS_ORG_IDfor a scoped session. - Never guess payload fields. Use Apple Ads request JSON in a file and pass it with
--file. - Do not mutate a live account until the user has named the org and approved the resource type. Prefer read-only checks first.
Auth
Stored profile:
asc ads auth login \
--name "Marketing" \
--client-id "$ASC_ADS_CLIENT_ID" \
--team-id "$ASC_ADS_TEAM_ID" \
--key-id "$ASC_ADS_KEY_ID" \
--private-key "$ASC_ADS_PRIVATE_KEY_PATH" \
--org "$ASC_ADS_ORG_ID" \
--networkEnvironment auth:
export ASC_ADS_CLIENT_ID="SEARCHADS_CLIENT_ID"
export ASC_ADS_TEAM_ID="SEARCHADS_TEAM_ID"
export ASC_ADS_KEY_ID="KEY_ID"
export ASC_ADS_PRIVATE_KEY_PATH="$HOME/.asc/apple-ads-private-key.pem"
export ASC_ADS_ORG_ID="123456"Short-lived token auth:
export ASC_ADS_ACCESS_TOKEN="ACCESS_TOKEN"
export ASC_ADS_ORG_ID="123456"Useful checks:
asc ads auth status --validate --output json
asc ads auth doctor --output json
asc ads me view --output json
asc ads acls --output jsonOrg Resolution
When the org ID is unknown:
asc ads acls --output jsonUse the returned org ID:
asc ads campaigns --org "123456" --limit 10 --output jsonOrg precedence is --org, ASC_ADS_ORG_ID, stored profile org_id, then config ads.org_id.
Read Workflows
Campaigns and ad groups:
asc ads campaigns --org "123456" --limit 100 --output json
asc ads campaigns --org "123456" --paginate --output json
asc ads campaigns view --org "123456" --campaign 987654321 --output json
asc ads ad-groups list --org "123456" --campaign 987654321 --output jsonDiscovery:
asc ads apps search --org "123456" --query "My App" --limit 10 --output json
asc ads product-pages list --org "123456" --adam-id 1234567890 --states VISIBLE --output json
asc ads creatives list --org "123456" --limit 100 --output json
asc ads geo search --org "123456" --query "San Francisco" --country-code US --limit 10 --output jsonReports:
asc ads reports campaigns --org "123456" --file reporting-request.json --output json
asc ads reports keywords --org "123456" --campaign 987654321 --file reporting-request.json --output jsonReporting and find endpoints keep pagination in the JSON body.
Mutating Workflows
Create and update commands take Apple Ads JSON files:
asc ads campaigns create --org "123456" --file campaign.json --output json
asc ads campaigns update --org "123456" --campaign 987654321 --file campaign-update.json --output json
asc ads ad-groups create --org "123456" --campaign 987654321 --file ad-group.json --output jsonBulk endpoints often require arrays:
asc ads targeting-keywords create-bulk \
--org "123456" \
--campaign 987654321 \
--ad-group 123456789 \
--file keywords.json \
--output jsonDelete commands require --confirm:
asc ads targeting-keywords delete-bulk \
--org "123456" \
--campaign 987654321 \
--ad-group 123456789 \
--file keyword-ids.json \
--confirm \
--output json
asc ads campaigns delete --org "123456" --campaign 987654321 --confirmFor live tests, create paused resources with names such as ASC CLI Live Test <timestamp>. Clean up only the parent campaign or ad group created for that test. Apple may reject direct deletion for default product page creative ads, but deleting the test parent campaign or ad group can clean up the test resource.
Raw API
Use raw requests when Apple adds a field before the first-class command surface changes:
asc ads api request \
--method POST \
--path v5/campaigns/find \
--org "123456" \
--file selector.json \
--output jsonRaw requests accept only Apple Ads v5 paths or https://api.searchads.apple.com/api/v5/... URLs. DELETE still requires --confirm.
Live Test Checklist
- Start with
asc ads me view --output jsonandasc ads acls --output json. - Print the target org ID before mutations.
- Create paused or future-dated resources.
- Use a unique test name.
- Save created IDs from JSON output.
- Delete only the test parent campaign or ad group created during the run.
- Run a final campaigns find/list query to confirm cleanup.
Related skills
How it compares
Pick asc-apple-ads over manual App Store Connect UI work when repeatable asc ads CLI scripts with JSON reports are needed at iOS launch scale.
FAQ
Does asc auth login configure Apple Ads?
asc-apple-ads documents that Apple Ads auth is separate from App Store Connect auth. asc auth login does not configure asc ads; developers must authenticate Apple Ads independently before campaign commands.
How does asc-apple-ads automate Apple Ads commands?
asc-apple-ads uses asc ads with --output json and org ID via --org or ASC_ADS_ORG_ID. The skill requires running subgroup help and supplying Apple Ads request JSON from files rather than guessing fields.