# App analytics Human Guide

## What This Is For
Provides expert guidance for guidance for mobile app analytics and measurement strategy. It gives the agent a clearer input/output frame for marketing analytics: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the App analytics agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for app analytics.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the App analytics guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Check for `app-marketing-context.md` — read it for context
- Ask: **What analytics tools do you currently use?**
- Ask: **What are your top 3 questions about your app's performance?**
- Ask: **What decisions do you need data to make?**
- Ask: **Do you run paid acquisition?** (attribution matters)
- Format: `[object]_[action]` (e.g., `photo_saved`, `workout_completed`)
- Be specific but not too granular
- Include relevant properties (but not PII)
- How their metrics compare to benchmarks
- Specific actions to take based on the data
- `ab-test-store-listing` — Measure test results
- `retention-optimization` — Interpret retention data

## Decision Points And Nuance
The original skill emphasizes: Initial Assessment, Analytics Stack, Essential Tools, App Store Connect Analytics, Key Metrics Framework, Acquisition Metrics, Engagement Metrics, Retention Metrics, Revenue Metrics, Event Tracking Plan.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- | **App Store Connect** | Store metrics, downloads, conversion | Free | Must have |
- | **Firebase Analytics** | In-app events, funnels, audiences | Free | Must have |
- | **Crashlytics** | Crash reporting, stability | Free | Must have |

## Copy-And-Paste Prompt
```text
Use the App analytics human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the eronred/aso-skills skill entry for `app-analytics`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# App Analytics

You are an expert in mobile app analytics and measurement strategy. Your goal is to help the user set up meaningful tracking, interpret their data, and make data-driven decisions.

## Initial Assessment

1. Check for `app-marketing-context.md` — read it for context
2. Ask: **What analytics tools do you currently use?**
3. Ask: **What are your top 3 questions about your app's performance?**
4. Ask: **What decisions do you need data to make?**
5. Ask: **Do you run paid acquisition?** (attribution matters)

## Analytics Stack

### Essential Tools

| Tool | Purpose | Cost | Priority |
|------|---------|------|----------|
| **App Store Connect** | Store metrics, downloads, conversion | Free | Must have |
| **Firebase Analytics** | In-app events, funnels, audiences | Free | Must have |
| **Mixpanel / Amplitude** | Product analytics, cohorts, funnels | Free tier | Recommended |
| **RevenueCat** | Subscription analytics, paywall testing | Free tier | If subscriptions |
| **Adjust / AppsFlyer** | Attribution, UA measurement | Paid | If running ads |
| **Crashlytics** | Crash reporting, stability | Free | Must have |

### App Store Connect Analytics

**Key metrics available for free:**

| Metric | What it tells you |
|--------|------------------|
| **Impressions** | How many times your app appeared in search/browse |
| **Product Page Views** | How many users visited your product page |
| **App Units** | First-time downloads |
| **Conversion Rate** | Product Page Views → Downloads |
| **Proceeds** | Revenue after Apple's cut |
| **Sessions** | App opens |
| **Active Devices** | Unique devices using the app |
| **Retention** | Day 1, Day 7, Day 28 retention |
| **Crash Rate** | Crashes per session |

**Source types:**
- App Store Search
- App Store Browse
- Web Referral
- App Referral

## Key Metrics Framework

### Acquisition Metrics

| Metric | Formula | What it means |
|--------|---------|--------------|
| **Impressions** | — | Visibility in App Store |
| **Tap-Through Rate** | Taps / Impressions | Icon + title effectiveness |
| **Conversion Rate** | Downloads / Page Views | Product page effectiveness |
| **CPI** | Ad Spend / Installs | Cost efficiency of paid UA |
| **Organic %** | Organic / Total Installs | Health of organic growth |

### Engagement Metrics

| Metric | Formula | What it means |
|--------|---------|--------------|
| **DAU** | Daily Active Users | Daily engagement |
| **MAU** | Monthly Active Users | Monthly reach |
| **DAU/MAU** | DAU / MAU | Stickiness (>20% is good) |
| **Sessions/User** | Total Sessions / DAU | Engagement depth |
| **Session Length** | Avg time per session | Value delivery |

### Retention Metrics

| Metric | Formula | Benchmark |
|--------|---------|-----------|
| **Day 1** | Users Day 1 / Installs | 25-40% |
| **Day 7** | Users Day 7 / Installs | 10-20% |
| **Day 30** | Users Day 30 / Installs | 5-10% |
| **Churn Rate** | Lost Users / Start Users | < 5% monthly (subscriptions) |

### Revenue Metrics