spotuify analytics
When to use it
Section titled “When to use it”Inspect local analytics data
Examples
Section titled “Examples”spotuify analytics events --limit 20spotuify analytics top --kind artistsInspect local analytics data
Usage: spotuify analytics [OPTIONS] <COMMAND>
Commands: events Print recent analytics events top Top-N most-played tracks / artists / albums / playlists habits Habit metrics bucketed by `day` / `week` / `month` search Search history (raw or normalized mode) rediscovery Tracks worth re-discovering rebuild Recompute derived listen facts from analytics_events prune Apply retention prune (default: dry-run) export Export qualified listens to ListenBrainz / Last.fm import Import historical scrobbles help Print this message or the help of the given subcommand(s)
Options: --log-format <LOG_FORMAT> Phase 13 (P13-A) - pick the daemon log format for this run. Also honoured via `SPOTUIFY_LOG_FORMAT` [possible values: text, json] --no-daemon-start Phase 13 (P13-H) - if set, the CLI never auto-starts the daemon. Errors with a clear hint when the daemon socket is missing -o, --set <key.path=value> Phase 13 (P13-H) - one-shot TOML override (e.g. `-o player.bitrate=160`). Repeatable. Applies for this invocation only; the config file on disk is unchanged -h, --help Print help