Analytics — the three altitudes
Inklate measures at three altitudes — the operations dashboard, the analytics overview, and per-post metrics — over one shared, null-aware metric contract.
Inklate answers two different questions with two different surfaces: “is the machine running?” (the operations dashboard) and “what’s working?” (the analytics overview), with per-post metrics sitting underneath both. All three read the same synced numbers, so they never disagree.
The operations dashboard
The dashboard is the org-wide operations view — the review of how your posting pipeline is running right now, not how any single post performed. It aggregates in SQL and shows:
- Pipeline — how many posts sit in each lifecycle status (draft, scheduled, published, failed, and the rest) this moment.
- Cadence — published placements per day, split by provider, over the selected range.
- Forward horizon — posts scheduled to fire over the next 7 days.
- What needs you now — posts awaiting approval and how long the oldest has waited.
- Throughput — posts published in range and the average draft-to-live wait.
It also surfaces channel token health so an expiring connection is caught before it silently stops publishing. See Channel health.
The analytics overview
The analytics overview is the org’s outcome surface — the review-mode counterpart to the dashboard. One engagement report drives it: period-over-period headline tiles (impressions, engagement, engagement rate), a daily trend with the previous period drawn as a ghost line, per-provider and per-format splits, a when-to-post heatmap, and a top-posts leaderboard. Every total is null-aware — an unmeasured metric shows as an em-dash, never a fake zero.
The whole report can be scoped to a single channel, so one channel gets the same rich treatment as the whole organization.
Per-post metrics
Every published post carries its own metrics panel: per-placement totals across each channel it went to, its engagement and engagement rate, a comparison against your organization’s average engagement rate, and a per-day gained-engagement trend. A Sync now control refreshes a post’s numbers on demand between background syncs.
One contract underneath
All three altitudes share a five-metric contract — impressions, reactions, comments, shares, and clicks — where a metric a platform doesn’t report is null (unknown), never 0. Engagement is the sum of the three interactions every platform reports, so it stays comparable across networks. Numbers are refreshed by a background sync you can nudge on demand.
Labels
Labels are shared, color-coded tags that classify posts for filtering and reporting. Manage them in settings, apply them in the composer, and see them as chips on the calendar.
Metrics and coverage
Inklate tracks five metrics on a contract where null ≠ 0 — a metric a platform doesn't report is unknown, not zero. Coverage varies by network and scope.