gplay-reports-download
Financial and statistics report listing and downloading from Google Play Console via GCS. Use when asked to view, list, or download financial earnings, sales, payouts, or app statistics (installs, ratings, crashes).
What this skill does
# Google Play Reports Download
Use this skill when you need to list or download financial reports (earnings, sales, payouts) or statistics reports (installs, ratings, crashes, store performance, subscriptions) from Google Play Console.
## How reports work
Google Play Console reports are **not available via the REST API**. They are stored as CSV/ZIP files in Google Cloud Storage (GCS) buckets:
- **Bucket name**: varies by account — either `pubsite_prod_rev_<id>` or `pubsite_prod_<id>`. Always copy the exact URI from Play Console.
- **Financial reports**: `earnings/`, `sales/`, `payouts/`, `play_balance_krw/`, `wht_statements/` prefixes
- **Statistics reports**: `stats/installs/`, `stats/ratings/`, `stats/crashes/`, `stats/store_performance/`, `financial-stats/subscriptions/` prefixes
The service account must have access to the GCS bucket (this access is granted automatically when the service account is added to Play Console with appropriate permissions).
## Prerequisites
- A service account configured via `gplay auth login`
- The GCS bucket ID (see below — this is **not** the same as the Play Console URL developer ID)
- For financial reports: `VIEW_FINANCIAL_DATA` permission (service account must be added to Play Console with "View financial data" access)
- For stats reports: `VIEW_APP_INFORMATION` permission (service account must be added to Play Console with "View app information" access)
## Finding your bucket ID
> **Important:** The bucket ID for reports is **not** the numeric ID in your Play Console URL. The URL ID and the GCS bucket ID are different.
To find the correct bucket ID:
1. Go to **Google Play Console** > **Download reports** (in the left sidebar under "Download reports")
2. Look for the **Cloud Storage URI** shown on that page, e.g.:
```
gs://pubsite_prod_rev_12110000881713004121/
```
3. You can pass either the full URI or just the numeric ID: `12110000881713004121`
Alternatively, use the Google Cloud Console to find the bucket name associated with your Play Console account.
**Common mistake:** Using the developer ID from the Play Console URL (`https://play.google.com/console/developers/<this_id>/...`) will result in a `404 Not Found` error because the GCS bucket uses a different internal ID.
## Financial reports
### List available financial reports
```bash
# List all financial reports
gplay reports financial list --bucket-id <id>
# You can also pass the full GCS URI
gplay reports financial list --bucket-id "gs://pubsite_prod_rev_12345/"
# Filter by type
gplay reports financial list --bucket-id <id> --type earnings
gplay reports financial list --bucket-id <id> --type sales
gplay reports financial list --bucket-id <id> --type payouts
# Filter by date range
gplay reports financial list --bucket-id <id> --from 2026-01 --to 2026-06
# Combine filters
gplay reports financial list --bucket-id <id> --type earnings --from 2026-01 --to 2026-03
```
### Download financial reports
```bash
# Download earnings for a specific month
gplay reports financial download --bucket-id <id> --from 2026-01 --type earnings
# Download to a specific directory
gplay reports financial download --bucket-id <id> --from 2026-01 --type earnings --dir ./reports
# Download a range of months
gplay reports financial download --bucket-id <id> --from 2026-01 --to 2026-06 --type sales
```
### Financial report types
| Type | Description | Filename pattern |
|------|-------------|-----------------|
| `earnings` | Revenue and earnings data | `earnings/earnings_YYYYMM_<id>.zip` |
| `sales` | Sales transaction reports | `sales/salesreport_YYYYMM.zip` |
| `payouts` | Payment disbursement reports | `payouts/payout_YYYYMM.csv` |
| `play_balance` | Play balance reports (KRW) | `play_balance_krw/...` |
| `wht_statements` | Withholding tax statements | `wht_statements/...` |
## Statistics reports
### List available statistics reports
```bash
# List all stats reports
gplay reports stats list --bucket-id <id>
# Filter by package name
gplay reports stats list --bucket-id <id> --package com.example.app
# Filter by type
gplay reports stats list --bucket-id <id> --type installs
# Filter by date range and package
gplay reports stats list --bucket-id <id> --package com.example.app --type installs --from 2026-01 --to 2026-06
```
### Download statistics reports
```bash
# Download installs report
gplay reports stats download --bucket-id <id> --package com.example.app --from 2026-01 --type installs
# Download to a specific directory
gplay reports stats download --bucket-id <id> --package com.example.app --from 2026-01 --type crashes --dir ./reports
# Download a range of months
gplay reports stats download --bucket-id <id> --package com.example.app --from 2026-01 --to 2026-06 --type ratings
```
### Statistics report types
| Type | Description | Filename pattern |
|------|-------------|-----------------|
| `installs` | Install/uninstall data | `stats/installs/installs_<pkg>_YYYYMM_overview.csv` |
| `ratings` | Rating distribution | `stats/ratings/ratings_<pkg>_YYYYMM_overview.csv` |
| `crashes` | Crash occurrence data | `stats/crashes/crashes_<pkg>_YYYYMM_overview.csv` |
| `store_performance` | Store listing performance | `stats/store_performance/...` |
| `subscriptions` | Subscription metrics | `financial-stats/subscriptions/...` |
## Flags reference
### Financial commands
| Flag | Required | Description |
|------|----------|-------------|
| `--bucket-id` | Yes | GCS bucket ID or full URI |
| `--type` | No (list: default `all`) / Yes (download) | Report type: `earnings`, `sales`, `payouts`, `play_balance`, `wht_statements`, `all` |
| `--from` | No (list) / Yes (download) | Start month `YYYY-MM` |
| `--to` | No | End month `YYYY-MM` (defaults to `--from`) |
| `--dir` | No | Output directory (default `.`) |
| `--output` | No | Output format: `json`, `table`, `markdown` |
| `--pretty` | No | Pretty-print JSON output |
### Stats commands
| Flag | Required | Description |
|------|----------|-------------|
| `--bucket-id` | Yes | GCS bucket ID or full URI |
| `--package` | No (list) / Yes (download) | Package name filter |
| `--type` | No (list: default `all`) / Yes (download) | Stats type: `installs`, `ratings`, `crashes`, `store_performance`, `subscriptions`, `all` |
| `--from` | No (list) / Yes (download) | Start month `YYYY-MM` |
| `--to` | No | End month `YYYY-MM` (defaults to `--from`) |
| `--dir` | No | Output directory (default `.`) |
| `--output` | No | Output format: `json`, `table`, `markdown` |
| `--pretty` | No | Pretty-print JSON output |
## Output format
### List output
```json
{
"bucket": "pubsite_prod_rev_12345",
"reports": [
{"name": "earnings/earnings_202601_12345.zip", "size": 1234, "updated": "2026-02-01T00:00:00Z"}
]
}
```
### Download output
```json
{
"bucket": "pubsite_prod_rev_12345",
"type": "earnings",
"from": "2026-01",
"to": "2026-01",
"dir": "./reports",
"files": [
{"name": "earnings/earnings_202601_12345.zip", "path": "reports/earnings_202601_12345.zip", "size": 1234}
]
}
```
## Common workflows
### Monthly financial review
```bash
# List last month's earnings
gplay reports financial list --bucket-id <id> --type earnings --from 2026-01 --output table
# Download all financial reports for Q1
gplay reports financial download --bucket-id <id> --from 2026-01 --to 2026-03 --type earnings --dir ./q1-reports
```
### App performance monitoring
```bash
# Check install trends
gplay reports stats list --bucket-id <id> --package com.example.app --type installs --from 2026-01
# Download crash data for analysis
gplay reports stats download --bucket-id <id> --package com.example.app --from 2026-01 --type crashes --dir ./crash-data
```
### CI/CD automated report collection
```bash
# Download all report types for archival
for type in earnings sales payouts; do
gplay reports financial download --bucket-id $BUCKET_ID --from $(date -d "last month" +%Y-%m) --type $type --dir ./monthly-reports
done
``Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.