Skip to main content
The analytics commands return account-level metrics for a connected platform and performance metrics for an individual post. Output is JSON by default — pass --table for a human-readable view, or pipe the JSON into jq for scripting.

​
analytics:platform

Get analytics for a platform section or social account.
​
string
required
Account UUID, or a platform name (facebook, instagram, linkedin, linkedin_page, youtube, x, twitter, whatsapp). When you pass a platform name, the CLI resolves it to the first connected account for that platform in your workspace.
​
string
The analytics section to fetch (for example page, posts, videos, account, media, stories, channel, content). Sections are platform-specific — see the table below. Omit it to see the available sections for a platform name, or to fetch the combined platform summary when the identifier is an account UUID.

​
Available sections

Platform aliases are normalized automatically before the request is sent: twitter is treated as x, and linkedin_page is treated as linkedin.

​
How resolution works

1

Platform name + no section

The CLI prints the available sections for that platform and exits without making a request.
2

Account UUID + no section

The CLI fetches the combined platform summary from the legacy /v1/analytics/platform/:id endpoint.
3

Identifier + section

The CLI fetches that specific section. If the platform is known, the section is validated against the table above before the request is made.

​
Examples

Passing an invalid section for a known platform (for example so-me analytics:platform facebook stories) fails and prints the list of valid sections for that platform. If you pass an account UUID that isn’t connected in the current workspace together with a section, the command also fails — run so-me accounts:list to find a valid account.

​
analytics:post

Get performance metrics for a specific post by its ID.
​
string
required
The post UUID.

​
Examples