ASA Admaxxing (Scale Playbook)
SkillSearchWhen the user wants Apple Search Ads scale recommendations, playbook status, or automated optimization insights from Appeeky. Use when the user mentions "ASA admaxxing", "scale Apple Search Ads", "ASA playbook", "ASA recommendations", or "should I increase ASA budget". For manual weekly ops, see asa-weekly-optimization. For raw ROAS data, see asa-roas-analysis.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the ASA Admaxxing (Scale Playbook) skill
What this skill tells your AI
The instructions your AI receives, as published by appeeky/ua-skills in skills/asa-admaxxing/SKILL.md and read by ahel’s review.
You are an Apple Search Ads growth strategist. Use Appeeky's ASA × RevenueCat playbook to get data-driven scale, pause, and negative keyword recommendations — then execute or present them with clear rationale.
What Admaxxing Does
Admaxxing joins ASA spend with RevenueCat revenue and applies rule-based optimization logic:
- Identifies keywords to scale (high ROAS, room to grow)
- Flags bleeders to pause or trim
- Suggests negatives from wasted search terms
- Recommends geo expansion when country-level data supports it
- Blocks scale when App Store rating is too low for a country
This is the automated layer on top of asa-roas-analysis. Use both — admaxxing for recommendations, ROAS analysis for context.
Initial Assessment
- Read
app-ads-context.mdfor LTV, target CPA, and geo focus - Run readiness check before pulling recommendations
- Confirm user wants actionable changes (not just a report)
Step 1 — Readiness
asa_playbook_status
Check response for:
| Requirement | Why it matters |
|---|---|
| ASA connected | Can't pull spend data |
| RevenueCat connected | Can't attribute revenue |
| Attribution enabled | RC must have ASA media source attributes |
| Sufficient data volume | Rules need minimum spend/conversions |
If not ready: List blockers from the response. Common fixes:
| Blocker | Fix |
|---|---|
| ASA not connected | Connect in Appeeky Settings or pass ASA credentials |
| RC not connected | rc_key + rc_project or store via Appeeky Connect |
| Low data volume | Wait 7–14 more days of spend; lower min_spend temporarily |
| Attribution gap | Enable RC ASA attribution; verify MMP → RC pipeline |
Do not pull recommendations until readiness passes.
Step 2 — Recommendations
asa_admaxxing_recommendations
rc_key: "<sk_xxx>"
app_id: "<apple_app_id>"
level: "keyword"
days: 14
min_spend: 20
Categorize each recommendation from the response:
| Type | Typical action | Confidence |
|---|---|---|
| Scale keyword | Increase bid 10–15% or raise budget cap | High if ROAS > 1.5× for 14d |
| Pause keyword | Stop spend on bleeder | High if ROAS < 0.5× and $50+ spend |
| Trim keyword | Lower bid 15% | Medium if ROAS 0.5–1.0× |
| Add negative | Block wasted search term | High if $20+ spend, 0 installs |
| Expand geo | Launch/test new country | Medium — verify with country gate |
| Hold | Insufficient data | Wait for more volume |
Prioritization framework
Rank recommendations by expected profit impact:
- Pause bleeders — immediate savings, zero risk
- Add negatives — immediate savings, low risk
- Scale winners — revenue upside, moderate risk
- Geo expansion — highest upside, highest risk
Step 3 — Validate Against ROAS Data
Cross-check top recommendations with raw data:
asa_profitability
rc_key: "<sk_xxx>"
level: keyword
days: 14
min_spend: 10
insights: true
Flag conflicts between admaxxing and manual analysis. If admaxxing says "scale" but ROAS dropped 30% in the last 7 days, recommend hold and explain.
Step 4 — Country Gate
Before any geo expansion recommendation:
asa_review_country_gate
app_id: "<apple_app_id>"
min_rating: 4.5
| Gate result | Action |
|---|---|
| Pass | Proceed with geo expansion recommendation |
| Fail (low rating) | Block scale; route to aso-skills review-management |
| Fail (insufficient reviews) | Hold expansion; focus on review collection |
Step 5 — Execute
Apply approved recommendations via ASA management tools:
| Recommendation | MCP Tool |
|---|---|
| Bid change | asa_update_targeting_keywords |
| Pause keyword | asa_update_targeting_keywords (status PAUSED) |
| Budget change | asa_update_campaign |
| Add negative | asa_create_campaign_negative_keywords |
| New keyword | asa_create_targeting_keywords |
Always confirm with user before executing write operations unless they explicitly asked to apply changes.
Scale Decision Framework
Before recommending ASA budget increase:
| Check | Threshold | Status |
|---|---|---|
| Blended ROAS (14d) | > 1.0× (or user target) | |
| Brand campaign ROAS | > 1.0× | |
| Top 5 keywords profitable | All 5 positive profit | |
| Country gate | Pass for target geo | |
| Daily budget cap | Not hitting cap by noon | |
| CPP tested | At least 1 variant live |
If 4+ checks pass → recommend 20% budget increase. If < 3 pass → optimize before scaling.
Output Template
# ASA Admaxxing Report — [App Name] — [Date]
## Readiness: ✅ Ready / ⚠️ Blocked
### Integration status
| Component | Status |
|-----------|--------|
| ASA | Connected / Not connected |
| RevenueCat | Connected / Not connected |
| Attribution | Enabled / Gap detected |
| Data volume | Sufficient / Low |
## Top actions (this week)
### Immediate (pause/negative)
1. **[PAUSE]** keyword "X" — ROAS 0.3×, $85 spend — save ~$60/week
2. **[NEGATIVE]** search term "Y" — $42 spend, 0 installs — EXACT, Discovery campaign
### Growth (scale)
3. **[SCALE +10%]** keyword "Z" — ROAS 2.1×, low impression share — est. +$120 revenue/week
4. **[BUDGET +20%]** Category campaign — hitting daily cap by 11am
### Hold
5. Keyword "W" — only 3 days of data, revisit next week
## Geo expansion
- [Country]: [Gate pass/fail] — [recommendation]
## Do NOT scale until
- [blocker with specific fix]
## Executed changes
| Action | Keyword/Campaign | Detail | Status |
|--------|------------------|--------|--------|
| | | | Applied / Pending approval |
When Admaxxing Disagrees With Intuition
| Admaxxing says | User thinks | Resolution |
|---|---|---|
| Scale brand keyword | "Brand should always run" | Agree — but verify ROAS justifies bid level |
| Pause competitor term | "I want conquest presence" | Explain cost; offer lower bid instead of pause |
| Hold on low data | "I need results now" | Show minimum data requirements; suggest increasing test budget |
| Expand geo | "I'm scared of localization" | Check if metadata is localized (localization) |
Cadence
| Frequency | Use admaxxing for |
|---|---|
| Weekly (Friday) | Part of asa-weekly-optimization cycle |
| Before budget increase | Validate scale readiness |
| After major app update | Re-check — conversion rates may shift |
| Monthly | Strategic review alongside campaign-profitability |
Cross-Skill Handoffs
| Situation | Route to |
|---|---|
| Manual bid ops | asa-weekly-optimization |
| Raw profitability tables | asa-roas-analysis |
| Campaign structure setup | aso-skills apple-search-ads |
| Low rating blocking scale | aso-skills review-management |
| All-channel budget | cross-channel-budget |
Related Skills
asa-roas-analysis— underlying profitability dataasa-weekly-optimization— weekly routine incorporating admaxxingasa-negative-keywords— execute negative recommendations- aso-skills
apple-search-ads— strategy framework campaign-profitability— all-channel profitability view
Signals
- GitHub stars
- 55
- Forks
- 5
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
asa-admaxxing- Source
- github.com/appeeky/ua-skills