> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.simplified.com/cli/analytics-and-reporting/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.simplified.com/_mcp/server. # Analytics and reporting The CLI provides four views of social performance: summary KPIs, metrics over time, individual posts, and audience demographics. Use them together to answer what changed and which content contributed. ## 1. Choose an account and reporting period ```bash simplified accounts:list ``` Copy the account's numeric `id`. Analytics commands use singular `--account` (or `-a`), unlike the comma-separated `--accounts` option used by post commands. Use `YYYY-MM-DD` dates, with `--to` set to today or an earlier date. The examples below use a completed month. Replace both dates with your reporting window. Available metrics and demographic fields vary by network and account. ## 2. Read the account summary ```bash simplified analytics:aggregated \ --account 12345 --from 2026-08-01 --to 2026-08-31 ``` Use the returned engagement, publishing, reach/impression, and follower metrics as the starting point for a report. Compare the same account over comparable periods; do not assume that similarly named metrics have identical definitions across networks. ## 3. Look at the trend over time ```bash simplified analytics:range \ --account 12345 --metrics "views,reach,follower_count" \ --from 2026-08-01 --to 2026-08-31 ``` Request metrics supported by that network. Inspect the returned time series for spikes, drops, or sustained changes, then compare those dates with your posting activity. Missing data is not automatically a zero result. ## 4. Inspect individual posts ```bash simplified analytics:posts \ --account 12345 --from 2026-08-01 --to 2026-08-31 \ --page 1 --per-page 25 ``` Review the response before deciding how to rank posts. A reach objective and an engagement objective may identify different winners. Continue through pages when building a complete report; `--per-page` supports up to 100 posts. ## 5. Understand the audience ```bash simplified analytics:audience \ --account 12345 --from 2026-08-01 --to 2026-08-31 ``` Use available demographic breakdowns to inform content and channel choices. The network may not supply every breakdown for every account. ## Save a report snapshot ```bash simplified analytics:aggregated \ --account 12345 --from 2026-08-01 --to 2026-08-31 > account-summary.txt ``` In CLI 1.8.0, analytics output includes a heading before the JSON response. Save it as text for inspection, or use the [output extraction example](/cli/use-from-an-ai-agent#read-command-output) before processing it as JSON. Run reports with an explicit teamspace in automated jobs so their scope does not depend on a saved interactive selection. > Move from account-level results to the posts and audiences behind them.