Plan before write
Every write command starts as a JSON plan that Claude Code, Codex, CI, or a human can review before execution.
Open source · Platform API 1.0 supported
Apple Ads CLI by Lily
Lily 0.2.0 supports Apple Ads Platform API 1.0 for campaign workflows and authenticated live reporting. Plan campaigns, review JSON dry-runs, and connect spend to keyword-level revenue and ROAS.
brew install crevas/tap/lilyadslily --provider platform ads plan create
lily --provider platform ads plan create \
--country US \
--daily-budget 300 \
--bid 3.00 \
--cpa-goal 2.00 \
--exact-keywords "photo editor,ai photo" \
--negative-exact "wallpaper,jobs" \
--creative product-page:pp_123Business first
Real-world workflows
Revenue first
Support keyword-level revenue
API 1.0
alongside classic v5
MIT License
Free Apple Ads operations
Different by focus
Not another endpoint wrapper.
Apple Ads managers think in launches, countries, budgets, CPA goals, creative routes, and payback. The CLI should speak that language.
Revenue-aware by design
Reports can call Lily Ads Revenue Analytics so campaign decisions are tied to paid users, profit, and ROAS.
Business workflows
Create the campaign package you mean, not a pile of raw endpoint calls stitched together by an agent.
Platform API 1.0 supported
Lily 0.2.0 added campaign workflows and authenticated live reporting; Lily 0.2.2 adds SDK-aligned keyword, phrase, category, target CPA, budget, popularity, impression-share, and change-history queries. v5 remains available.
Lily advantage
Spend is only useful when it can explain revenue.
A free Apple Ads CLI gets developers into the workflow. Lily Ads Revenue Analytics turns those same commands into paid-user, profit, and ROAS decisions.
1
Ask an agent to launch a US Apple Ads plan.
2
Review the JSON dry-run with campaign, ad group, keywords, negatives, CPA, and creative.
3
Approve execution only when the plan matches the business intent.
4
Pull spend plus Lily revenue to understand ROAS and paid-user quality.
ROAS enrichment
lily ads reports campaigns --app-id 999999999
{
"appleAds": { "spend": "$12,856" },
"revenue": { "source": "Lily Ads Revenue Analytics" },
"roas": "6.12x"
}Lily versus asc
Use asc for App Store Connect breadth. Use Lily when Apple Ads is the job.
The point is not to replace asc. The point is to own the Apple Ads workflow where revenue, creative, bids, and Platform API migration all meet.
Decisionasccli.shApple Ads CLI by Lily
Scope
Broad App Store Connect automation across releases, TestFlight, metadata, signing, analytics, and Apple Ads.
Apple Ads only, with deeper campaign planning, revenue enrichment, creative routing, and migration logic.
Command model
Endpoint-rich command tree for many App Store Connect jobs.
Business-first commands that create a campaign, ad group, keywords, negatives, CPA goal, and creative in one plan.
AI agent fit
Great general-purpose automation surface for coding agents.
JSON dry-runs by default, explicit confirmation for writes, and prompts that map to growth decisions.
Growth loop
Manages Apple Ads objects and reports.
Connects Apple Ads spend to Lily Ads Revenue Analytics so agents can explain paid users, profit, and ROAS.
Platform API
Useful for current Apple Ads API access inside a larger toolkit.
Supports Apple Ads Platform API 1.0 today, with v5 retained for migration compatibility and SDK-aligned opportunity commands in Lily 0.2.2.
Lily CLI is an independent Apple Ads-focused CLI and analytics tool for Apple Ads. It is not affiliated with Apple Inc. “Apple” and “Apple Ads” are trademarks of Apple Inc.
Platform API 1.0 — supported now
Run live Apple Ads workflows on API 1.0.
Authenticated reporting and SDK-aligned opportunity queries are available through Apple's v1 endpoint. Use the platform provider today; v5 stays available until migration, ahead of its January 26, 2027 retirement.
See what Platform API 1.0 unlocks for advertiserslily ads platform readinesslily --provider platform ads reports campaigns --app-id 999999999lily --provider platform ads suggestions keywords --app-id 999999999 --countries USlily --provider platform ads suggestions phrases --app-id 999999999lily --provider platform ads insights search-term-popularity --country US --genre Travelbrew install crevas/tap/lilyads
# or
curl -fsSL https://www.chatlily.ai/apple-ads-cli/install | bashFrequently asked questions
Security, open source, agents, and installation.
The short version: local keys stay local, the CLI stays open, and revenue analytics is the commercial layer.
- Is Lily CLI safe?
- Yes. Your Apple Ads private keys and certificates stay on your machine and do not need to be uploaded. If you want keyword-level revenue analytics, you can authorize Lily API access for Apple Ads reporting, but that revenue workflow does not require uploading your private key.
- Is Lily CLI free and open source?
- Yes. The CLI is free and open source for Apple Ads operations. Keyword-level revenue analytics through Lily is paid because Apple does not provide that capability as an official Apple Ads feature.
- How is Lily CLI different from asc?
- asccli.sh is a broad App Store Connect automation CLI. Lily CLI is narrower and deeper for Apple Ads: campaign planning, ad groups, keywords, negative keywords, CPA goals, creative routing, revenue enrichment, and Platform API migration.
- Does Lily support AI agents and coding assistants?
- Yes. Lily is designed for Claude Code, Codex, CI, and other coding assistants. Write operations default to JSON plans, so agents can show the proposed campaign package before anything is executed.
- Does Lily support Platform API 1.0?
- Yes. Lily 0.2.0 supports Apple Ads Platform API 1.0 for campaign workflows and authenticated live campaign reporting. Lily 0.2.2 aligns read-only opportunity queries with Apple's official SDK contract. Select it with --provider platform or APPLE_ADS_PROVIDER=platform; v5 remains available during migration.
- How is Lily CLI different from other Apple Ads CLI tools?
- Lily starts from business and revenue decisions instead of raw endpoint calls. The core workflow is to plan a campaign package, review it as JSON, execute safely, then connect spend to paid users, profit, and ROAS.
- Does Lily support RevenueCat or AppsFlyer?
- Yes. Lily can connect RevenueCat or AppsFlyer so Apple Ads spend can be attributed to keyword-level paid users, revenue, profit, and ROAS.
- How do I install Lily, the Apple Ads CLI?
- Install with Homebrew: brew install crevas/tap/lilyads. You can also use the hosted install script: curl -fsSL https://www.chatlily.ai/apple-ads-cli/install | bash.
Free core CLI, Lily revenue layer when you need ROAS