Analytics
What you published and how it performed, every channel in one view.
How are we doing? One page, every channel.
Each network has its own dashboard, its own numbers and its own idea of what counts. Analytics puts them on one page: what was published, what happened to it, and what your site and search results did in the same weeks.
It combines two sources: FinalPost's own publishing records, and live numbers from the platforms you have connected.
Three views, one date range
| View | What you see |
|---|---|
| Overview | An insight line from Jarvis, social totals where available, publishing KPIs, a channel breakdown, daily volume and your most recent posts |
| Social posts | Recent social posts with per-post engagement |
| Website & search | Google Analytics and Search Console reporting, once you connect them |
The date range you choose applies to all three.
The four numbers at the top
- Published — posts that went live in the window, with a trend against the previous window.
- Awaiting approval — drafts from the window that still need you.
- Failed — publish attempts that did not go through.
- Failure rate — failed out of everything sent, so you notice a broken connection early.
Honest about what it knows
- Per-post engagement (views, likes, comments) is shown for channels on the one-click connection. It includes posts you published outside FinalPost on the same accounts, so you see the whole account.
- Queue outcomes (posted, failed, awaiting, queued) work for every channel, including a blog.
- An empty view offers Check connections. It does not show invented zeros.
Connect your site, read-only
Google Search Console adds clicks, impressions, position and top queries. Google Analytics 4 adds sessions, users, engagement and top landing pages. Both are read-only and neither uses a social-account slot.
A five-minute weekly review is enough: what went out, what earned replies, what failed and why. Then let that shape next week's drafts. Use A/B tests when you want to compare two versions on purpose. The page is explained in Analytics.