CLI analytics commands
Pull post-level and account-level analytics, workspace overviews, and recommended
posting times. All analytics commands require the analytics:read scope on your
API key.
Commands
| Command | Description |
|---|---|
analytics:post <post-id> | Per-post analytics aggregated across platforms: impressions, engagements, likes, comments, shares, plus per-platform breakdowns |
analytics:posts <id,id,...> | Bulk analytics for up to 100 posts in one call (comma- or space-separated ids) |
analytics:overview | Workspace-level overview: totals, average engagement rate, top platform. Flags: --period <7d|30d|90d>, --start-date <YYYY-MM-DD>, --end-date <YYYY-MM-DD> |
analytics:accounts | Account-level analytics such as followers and subscribers. Flags: --platform, --date <YYYY-MM-DD> |
analytics:best-times | Recommended posting slots (top 3 plus per-day scores) computed from your own posting history. Flags: --platform (required), --timezone <IANA tz> |
analytics:best-times needs history to work with: below 15 analyzed posts it falls
back to labeled industry defaults instead of your own data.
Metric semantics
Account-level metrics from analytics:accounts are daily snapshots, and a
metric's scope varies by platform; read the note field on each row. The big
one: LinkedIn profile rows keep a lifetime total in impressions_lifetime,
across all of the account's content, including posts published outside
OmniSocials. When LinkedIn serves a daily breakdown, impressions is that day's
value and the row says period: "daily"; otherwise the row says
period: "lifetime". LinkedIn page rows always hold day values. Never compare a
lifetime total to a windowed export like LinkedIn's native 90-day analytics: a
multi-year account's lifetime total can easily be 10x a 90-day window. To
measure a window, diff two snapshots (--date 2026-08-01 vs --date 2026-07-01). Some platforms (e.g. Instagram) report no account-level
impressions at all; a missing field means "not collected", not zero.
Engagement is normalized the same way on every OmniSocials surface: the sum of the platform's real interaction fields: for LinkedIn that includes link clicks (matching LinkedIn's own definition), for X it includes quotes and bookmarks. Engagement rate is engagement / impressions.
Examples
How did last week go?
Terminal
Check a specific post across every platform it went to:
Terminal
Bulk-check a campaign:
Terminal
When should we post on TikTok?
Terminal
Combine with --json and jq for reporting pipelines:
Terminal