Facebook page insights template

Page reach moves in spikes, and a spike is only useful if you can say what caused it. This template keeps a row per post with its type and its shares, a row per day of page-level reach and views, and a row per audience snapshot, so the chart and the explanation live in the same workspace. It also makes the slow story visible: whether page likes are actually growing, or being replaced faster than they arrive.

The fast layer is Posts: one row per post on the page, with the message, the date it went out, the type (Video, Link, Photo), the reach it travelled to, the reactions it collected and the number of shares. The middle layer is Daily page insights, one row per day: page reach, page views, engagements, new likes. The slow layer is Audience, one row per snapshot: page likes, the net change since the last one, the top city and the top age band. Together they cover the three timescales a page actually moves on: the post, the day, and the slow drift of who follows you.

The line jumps on the twelfth. Why? Because a row per post sits next to a row per day, the answer is already on the chart: the post published on the twelfth appears right beside the peak, not in a different tab or in an app that has since stopped showing it. Page reach moves in spikes, and a spike you can explain is a spike you can try to repeat.

A decline of twelve in a week hides perfectly inside a running total and is unmissable as a series. That's the case for snapshots: page likes with a net change on every one, so a genuinely growing audience looks different from one being replaced faster than it arrives. Left unnoticed for two quarters, that kind of leak gets expensive. The sample rows include a week where likes went backwards: you'll recognize the shape before it belongs to your page.

Some posts collect reactions and never leave the feed. Others travel. Only the ratio between reactions and shares separates the two, and that ratio only exists once reach, reactions and shares are split by post type. What each post type earns does the splitting: all three numbers side by side with the ratios between them, so you're not working the difference out by eye from a list of posts.

Type "what drove the spike in reach on the twelfth" and the answer reads the daily row alongside the posts published against it. "Which post type gets shared most often" ranks by the ratio rather than the raw count. "Are page likes growing or leaking, month by month" reads the audience snapshots as a series. And "which posts got reactions but no clicks" is the question that separates a popular post from a useful one.

Most pages run paid and organic at the same time, and comparing them from two different reports is exactly how the wrong conclusion gets drawn. Add an Ads table and put paid reach beside organic reach on the same chart. The week that looked strong organically becomes visible for what it was: the week that got boosted. A campaign column, a creative, or a landing page can be added the same way.

Small businesses and nonprofits running their own pages get the most out of it. An agency reporting on a client's page fits too, and so does any marketer who needs a Facebook number that outlives the app's own window. If Facebook is one channel among several, the cross-platform social media analytics template holds them together instead.

One import a month covers it. Facebook arrives through Ferra's social import where your workspace has it enabled, a job you re-run, not a connection that stays open, and everywhere else, Facebook's own export or a Google Sheet you already keep loads the same tables today. One boundary: Meta Ads has no Ferra connector, so campaign cost stays out of this template. A monthly refresh keeps the daily and audience rows current, and current rows are all the two dashboards run on.