Per-post metrics

Post-level statistics from Home and the calendar — date windows, connect missing releases, and API access.

2 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Per-post metrics

Performance for one published release — not workspace-wide totals.

Where: Open a post from Home or the calendar, then choose Statistics in Post actions. Step-by-step for the modal menu is in Actions and stats.

Account-level charts on the Analytics sidebar page do not list individual posts. Use Workspace analytics for channel-wide trends.

Warning

Which channels support per-post insights depends on the channel key and the platform API. See the per-post table in Platforms → Analytics.

Statistics controls

Control	Purpose
7 days · 30 days · 90 days	Same lookback windows as workspace Analytics and the public API
Metric rows	Views, engagement, and other fields the provider returns for that release

While data loads you see Loading analytics…. When the platform has nothing for that post yet, the dialog shows No statistics available for this post.

Statistics need a published release id from the network. If OpenQuok never stored one — or the provider changed ids — you may need Connect first.

Connect a missing release

Inside Statistics, when analytics cannot match the post to provider content, OpenQuok shows:

Select the content that matches this post:

Pick the correct thumbnail from the grid and click Connect post. Success toast: Post connected.

If the provider does not expose searchable content, you may see No content found from this provider. The provider may not support this feature.

The CLI equivalent is posts:connect — list candidates with posts:missing, then pass the post row id and provider release id. See Managing posts → Connect a post and Update Release ID.