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
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
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
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
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
Use available demographic breakdowns to inform content and channel choices. The network may not supply every breakdown for every account.
Save a report snapshot
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 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.