Start with your own shape

Before any demo, write down 4 numbers. They determine the answer more than any feature.

How many accounts will you run in 12 months? Not today. Model the bill at your target size, because per-profile pricing looks reasonable at 10 and rearranges your margin at 200.

How many people need access? If the answer is three or more, seat-based pricing is charging you for a department you do not have.

Which networks do your clients actually use? Write the list. One unusual network on it eliminates more tools than price does.

How much of the work is replying versus publishing? Agencies consistently underestimate this, and a tool chosen for its calendar can be poor at the thing you do most.

Pricing questions

What exactly is metered? Accounts, seats, posts, AI credits, analytics history, or several at once. A tool metering 4 things is a tool whose bill you cannot predict.

What does this cost at twice my size? Ask them to quote it. The pause tells you what the growth curve looks like.

What happens when I add a person? If the answer is a per-seat charge, hiring becomes a software decision.

Are there costs outside the subscription? X charges per post through its API. A tool that passes that through at cost is being straight with you; one that hides it in the plan price is averaging your light usage against someone else’s heavy usage.

The 4 questions most tools dislike

Which networks return no analytics, and what do you show there? The correct answer names X, Discord and Slack, and says it shows a gap. If every cell in the dashboard has a number, some of those numbers are estimated. Ask which.

Does analytics history start when I connect, or does it roll? Platforms expire their numbers after about 30 days. If nobody stored a snapshot, a year-on-year comparison will not exist next year. This is the single most important analytics question and almost nobody asks it.

Which moderation actions work on which networks? Every platform exposes a different set: YouTube allows banning an author, Instagram allows hiding, Threads allows nothing. A tool showing the same 5 buttons everywhere is showing you buttons that will fail.

What do you do with my content when I use an AI feature? The answer should be one sentence and should name the provider. Anything vaguer is worth following up in writing.

Practical questions about the work

Can I set per-platform fields? Alt text per carousel slide, cover frame, collaborators, subreddit flair, reply controls, content warnings. If not, you will open the app anyway, which defeats the calendar.

What happens when a post fails? The useful answer is the platform’s own error message and a one-click requeue. A generic failure means guessing.

How do clients approve content? If they need to log in, most of them will not, and the process will collapse into WhatsApp within a month.

How do I get my data out? Scheduled content, past posts, analytics history. Ask before you start, not when you are leaving.

Things that matter less than they seem

The number of integrations. You will use two.

Best time to post. Every tool has it, all of them derive it from the same thin data, and consistency beats optimal timing on every network except Mastodon.

AI features in general. Every tool has an AI button now. The question is not whether it exists but whether it knows the platform’s rules before it writes, which is a different and much shorter list.

Follower growth features. If a tool offers them, treat that as information about the tool.

The trial that tells you something

Do not test with a fresh account and sample content. Connect one real client, run one real week, and pay attention to 3 things.

How long did the first connection take, including whatever was broken on the client’s side. How many times did you open a native app anyway. And how did it handle the first thing that went wrong, because something will.

A fortnight of that tells you more than a feature table ever will.

Our own side-by-side comparisons name the cases where the other tool is the better buy: vs Buffer, vs Later, vs Hootsuite, vs Publer.

No social listening

Brand and competitor monitoring across social and the wider web. Hootsuite does it, Later does a version of it, and we are not going to.

The reason is honest rather than principled: doing it properly means ingesting and indexing a large share of public social data continuously, which is a different product with a different cost base. A cheap version produces a keyword alert feed that misses most of what matters and looks like a feature on a pricing page.

If listening is central to your work, buy a tool built for it. We would rather say that than sell you a box that ticks.

No paid advertising management

Campaign creation, budgets, audiences, ad reporting. Out of scope entirely.

Organic publishing and paid media are different disciplines with different approval chains and different risk. Tools that do both tend to do one well, and the combined interface is heavier for everyone who only wanted the other half.

We are building the organic half, for people who run a lot of accounts with a small team.

No engagement automation

Auto-liking, auto-following, auto-commenting, auto-DM sequences.

This one is a position rather than a scoping decision. These features exist, they sell, and they are against the terms of service of every network that matters. They get accounts restricted, and it is usually the client’s account, not the agency’s.

There is also a quieter cost. An automated reply that lands on a complaint reads exactly as what it is, in public, under your client’s name.

AI-drafted replies are a different thing, and we do build those: a draft a person reads and sends. The difference is whether a human is in the loop, and we are not going to blur it.

No follower growth features

No follow-unfollow cycles, no engagement pods, no “grow your audience” mechanics of any kind.

They work briefly, they damage the account’s standing, and the audience they produce does not buy anything. If a tool offers them, that tells you what it thinks of your account.

No fabricated metrics

This is the one that costs us most in demos.

X, Discord and Slack return no analytics to any tool. Where a platform gives us nothing we show a dash and a note explaining why, rather than an estimate that fills the space.

A competitor dashboard with a number in every cell looks more complete. It is also, in three of 15 cases, an invention. Our version looks worse and can be defended line by line in front of a client, which is the version we would want if we were the one presenting.

No enterprise tier

No SSO, no procurement process, no custom contracts, no account manager. Business at $99 is the top of the list and it has no seat limit.

Enterprise sales is a company shape, not a feature set: security questionnaires, legal review, an implementation team. Building that changes who the product is designed for, and we would rather stay pointed at the small team with a lot of accounts.

If you need SSO and procurement sign-off, Hootsuite is genuinely the right answer and we will say so on a call.

What this list is for

2 things.

It saves you the month where you evaluate a tool, buy it, and discover in week three that the one thing you assumed was there is not. That month is expensive for you and produces a refund and a bad review for us.

And it is a commitment we can be held to. A roadmap is easy to publish because it is all upside. A list of refusals is only worth reading if it stays true, which is why it is dated and lives here rather than in a sales deck.

If any of it changes, it changes in the changelog, with the reason.

What we are building sits in the changelog, dated, including the entries where something took longer than we said. Start free.

Every network has a different ceiling

These are the real per-account daily limits, and they vary by more than an order of magnitude.

• Threads: 200 a day. The highest in the set by a wide margin.
• Discord and Slack: 100 a day.
• Instagram: around 50.
• Bluesky and Mastodon: around 50.
• Reddit and Pinterest: 24.
• Snapchat and Google Business: 20.
• LinkedIn: around 18.
• TikTok: 10. The tightest, and the one people hit.

A single calendar frequency applied across all of these is either far below what some networks want, or over the limit on others, and usually both at once.

The ceiling is not the target

The limit tells you what is permitted. What the platform rewards is a separate question, and the two rarely match.

Pinterest rewards volume. A pin has a shelf life measured in months, so publishing is closer to building a library than filling a feed. 24 a day is allowed and even a fraction of that compounds. Most accounts do two a week and wonder why the channel is quiet.

Reddit punishes volume. One post a month per community is often right, and the account that posts weekly reads as a brand running a campaign. Here the useful number is comments, not posts.

TikTok rewards consistency inside a hard cap. 10 a day is plenty for anyone, but the cap means a bulk upload of a month’s content in one afternoon will fail. Spread it.

LinkedIn rewards restraint. Three or four a week from a Page is usually the ceiling of what an audience tolerates, well under the technical limit of 18.

Google Business rewards recency. Posts expire visually after about a week, so one a week keeps the listing looking alive. More than that is wasted.

Format limits shape the plan too

Not just how many, but what.

One file per post on Pinterest and Snapchat. No carousels, which means covering a topic requires several pins rather than one post with 10 slides.

Up to 10 files on Instagram, Threads and Reddit galleries. One idea can be one post.

60 seconds on Snapchat, against 15 minutes on Pinterest and 3 minutes for a YouTube Short. The same video cannot simply go everywhere.

300 characters on Bluesky against 50,000 on Facebook. A caption written for one is either truncated or lost in the other.

Planning the format first and the frequency second produces a calendar that survives contact with the platforms.

The cost that exists on exactly one network

X charges per post through its API: around $0.015 for a standard post and $0.20 for one containing a link. Deleting through the API also costs.

Nowhere else in the set does the calendar have a direct unit cost. It changes the planning question from “how often” to “how often is this worth”, and it makes link-heavy scheduling on X materially more expensive than text.

Worth knowing before you promise a client daily posting there.

A calendar built from the ceilings

Instead of a frequency, set a shape per network, then fill it.

Daily or near-daily: Instagram, TikTok, Threads. High-tolerance feeds where absence is noticed.

Two or three a week: LinkedIn, Facebook, Bluesky, Mastodon, YouTube Shorts.

Weekly: Google Business, Discord announcements, Slack updates. Surfaces where each post is an event rather than a stream.

Volume, when there is material: Pinterest. Treat it as a library that grows.

Monthly at most: Reddit posts, with comments in between.

That is five different rhythms, which is why a single frequency never fitted.

Fail in the editor, not at the platform

The practical failure mode is silent. A scheduled post that exceeds a daily cap does not warn you in advance; it fails at the moment of publishing, when nobody is watching.

The fix is to enforce the platform’s own limits at the point of scheduling, so the eleventh TikTok of the day is refused while you can still move it to tomorrow. It is the same principle as validating a Reel’s aspect ratio before upload: catch it where it costs 30 seconds.

EngageDigital enforces each platform’s real daily caps and format constraints when you schedule, not when you publish. See how publishing works or check the limits network by network.

What each one actually is

Bluesky looks and behaves like early Twitter. 300 characters, quote posts as a first-class format, chronological and algorithmic feeds you can choose between, and content labels you apply yourself. It is centralised enough to be simple.

Mastodon is federated, which is the thing that confuses people. There is no single Mastodon. There are thousands of servers that talk to each other, and your account lives on one of them. Around 500 characters depending on which server, four privacy levels per post, content warnings as standard etiquette, and editing after publishing.

The practical difference: on Bluesky you sign up. On Mastodon you choose a neighbourhood first, and the choice matters, because your server’s culture and moderation are what you inherit.

The case for bothering

Reach per follower is unusually good. Both networks have chronological options and far less advertising competition, so a post to 2,000 followers reaches a meaningful share of them. That has not been true on the large networks for years.

The audiences are concentrated. Technology, journalism, open source, science, design, policy. If you sell to any of those, the density is higher than the follower count suggests.

It is cheap to be early. Building two thousand engaged followers now costs a fraction of what the equivalent took on Instagram in 2018, and the accounts that established themselves early keep the advantage.

Almost nobody is scheduling to them. Which means consistency alone is a differentiator.

The case against

The numbers are small. If you need volume this quarter, these are not where you find it.

Analytics are thin and always will be. Bluesky gives follower counts and basic engagement; impressions are derived rather than reported. Mastodon deliberately collects very little, because that is the point of it. If your client judges channels by dashboard numbers, you will struggle to make the case.

Marketing register is punished, hard. Both communities formed partly in reaction to advertising-driven platforms. A corporate voice that passes unnoticed on LinkedIn stands out badly here.

Mastodon has a real learning curve. Servers, federation, content warnings. An hour to understand properly, and the mistakes are visible.

Who should be on them

Yes, clearly: software and developer tools, open source projects, science and research, journalism and publishing, policy and advocacy, privacy-focused products, anyone whose audience left X on principle.

Probably not: local services, most retail, hospitality, anything where the audience is on Instagram and Facebook and has no reason to be anywhere else. A hair salon does not need a Mastodon presence, and saying so is more useful than selling one.

Worth a cheap test: B2B services, consultancies, agencies. Low cost to find out, and the test is 3 months of posting rather than a strategy document.

Getting the etiquette right

Alt text is expected, not optional. Both communities care about it visibly, and people will tell you. This is also simply good practice everywhere.

Content warnings on Mastodon are normal. Politics, food, long threads, anything heavy. Using them well is the difference between welcome and blocked.

Quote posts on Bluesky are conversation, not commentary. Adding your take above someone’s post is the native format; screenshotting instead reads as avoidance.

Post at human times. Mastodon’s chronological timelines mean posting time matters more here than anywhere else in the set. A three in the morning scheduled post is seen by nobody.

A realistic commitment

Do not build a strategy. Build a habit and measure it in 3 months.

Cross-post what already works elsewhere, rewritten for 300 characters rather than truncated. Reply to things in your field, because replies are where both networks actually form relationships. Once a week is enough on each.

Judge it on referral traffic and on conversations started, not on impressions, because impressions are the one number neither network reports honestly.

If after 3 months nothing has come of it, stop. That is a legitimate outcome and it cost you an hour a week.

EngageDigital publishes to Bluesky and Mastodon alongside 13 other networks, with quote posts, content warnings and per-instance limits handled natively. See Bluesky, see Mastodon, or start free.

Who the reply is really for

Not the reviewer. They have made their decision and moved on, and the odds of changing their mind in a public text box are low.

The reply is for the next 50 people who read that review while deciding whether to call you. They are looking for one thing: evidence that if something goes wrong, a person will deal with it reasonably.

Once you accept that, the writing gets much easier. You are not arguing. You are demonstrating, to an audience that is not in the conversation.

The four-part structure

It works for almost every negative review and takes about 3 minutes.

Thank them, briefly and without irony. One line. “Thank you for telling us” is enough. Skip “we appreciate all feedback”, which is what every template says.

Name the specific thing. This is the part that proves a human read it. “A 40-minute wait on a Saturday with a booking is not what we promise” beats any amount of general regret. If you dispute the facts, this is where you say so once, plainly, without heat.

Say what changed. The concrete thing. An extra person on Saturdays, a new check, a conversation with the team. If nothing has changed yet, say what you are looking into. Never promise something vague.

Offer a way to continue, off the listing. A name, an email, a phone number. This moves the conversation somewhere it can actually be resolved, and it shows the next reader that the door is open.

The 5 mistakes

Arguing the facts at length. Even when you are right. A long rebuttal reads as defensive to everyone who was not there, and the reviewer will reply, and now there is a thread.

The identical template. Readers see your replies in a column. Five identical responses signal that nobody is reading.

Blaming the customer. “As we explained at the time” is the most expensive phrase in this genre.

Waiting a month. A reply within a couple of days reads as attentive. A reply in March to a review from January reads as someone doing an annual clean-up.

Overwriting the existing reply without reading it. Google allows exactly one owner reply per review, editable afterwards. If a colleague already answered, replacing it silently can delete something better than what you are writing.

Positive reviews deserve a reply too

Most businesses answer complaints and ignore praise, which is backwards in one specific way: the positive replies are what make the negative ones credible.

A listing where only the angry reviews have responses looks like damage control. A listing where everything has a short, human reply looks like a business that pays attention.

3 sentences is plenty. Thank them, mention the specific thing they liked, give a reason to come back. 30 seconds each.

What to do about a fake one

It happens: a competitor, a mistaken identity, someone who has never been.

Report it through the listing, and then reply anyway while it is under review, because removal is slow and frequently refused. The reply for these is shorter and more careful:

“We have no record of a visit matching this and we would like to understand what happened. Please contact us at [email] so we can look into it.”

No accusation. The next reader draws their own conclusion, and a calm reply to an unfair review is unusually persuasive.

Making it a habit

The only version of this that survives is a routine, not a resolution.

Reviews get checked with the comment queue, every working day. Anything under 3 stars gets answered the same day. Everything else within 48 hours. One person owns it.

At 20 clients this is where a single queue stops being a convenience and starts being the only way it happens at all, because 20 listings means 20 logins to a console built for one business owner.

EngageDigital brings Google reviews and Facebook recommendations into the same inbox as comments, with the existing owner reply shown before you replace it. See the local module or start free.

Why approval processes collapse

4 reasons, in order of how often they kill one.

The client has to log in. This is the big one. A busy owner will not create an account, remember a password and learn an interface to approve 4 captions. They will reply to whatever arrives on their phone.

Nothing happens when nobody replies. A draft sitting in “awaiting approval” forever is a queue with no exit. Silence has to mean something.

Feedback arrives in 3 places. Comments in the tool, a WhatsApp voice note, a correction on the call. Now nobody knows which version is current.

Everything needs approving. If a reply to a comment has to go through the same process as a campaign launch, the process becomes the bottleneck for work that is time-sensitive by nature.

Rule one: approval goes to them

The client should never log in to anything. They receive a link, they see the posts as they will appear, they tap approve or write a note. That is the entire interaction, on a phone, in 90 seconds.

Every hour of friction you add here comes back as a week of delay. The agency logs in. The client taps.

Rule two: silence has a meaning, agreed in advance

Write it into the engagement, not into a policy document nobody reads.

The version that works: “Content goes out for approval by Thursday for the following week. If we have not heard back by Monday morning, we publish as drafted.”

Clients almost never object to this, because the alternative is that their account goes quiet and they know it. What it removes is the week where nothing ships and nobody can say why.

The one exception worth carving out: anything involving price, legal claims or a named third party waits for an explicit yes.

Rule three: one place for feedback

Not because tidiness matters, but because scattered feedback produces published mistakes.

If a client sends a voice note, the person who hears it writes the change into the draft as a comment before doing anything else. The voice note is not the record. The draft is.

This sounds like bureaucracy until the week someone acts on a verbal instruction that was later reversed, on a post that is now live, and nobody can reconstruct who said what.

Rule four: 3 tiers, not one

The most common mistake is treating all content as equally risky.

No approval. Replies to comments, review responses, community management. These are time-sensitive and low-risk, and a reply that needs sign-off arrives too late to be worth sending. Agree the tone once and trust the person doing it.

Batch approval. The standard calendar, approved a week at a time in one sitting. This is 90 percent of the output.

Explicit approval. Campaign launches, anything with a price or a legal claim, anything sensitive, anything naming another company. Individually, in writing, no exceptions.

Getting this split right is what makes the whole thing survive a busy month.

What to do about the client who never replies

Every agency has one. 2 approaches work and one does not.

Works: the deadline rule above, applied consistently from week one. They adapt or they accept what ships.

Works: a standing 15-minute slot. Same time every week, screen shared, approved live. For a certain kind of client this is the only thing that ever works, and it is cheaper than chasing.

Does not work: chasing. Three follow-ups a week trains them that the deadline is soft, costs you the time you were trying to save, and makes you feel like a supplier rather than an adviser.

The record you will be glad of

Keep who approved what and when. Not to win an argument, though it does that.

Keep it because 6 months into an account, the question is rarely “who approved this” and usually “how long does approval actually take here”. If the answer is 4 days, your Thursday deadline is wrong and the calendar should be built a week further ahead.

That is a process fix you can only see if someone recorded the timestamps.

EngageDigital is building approval workflows with client-side review by link, so the person approving never needs an account. It sits on the Business plan. See where it is in the queue or start free.

What actually blocks you

3 things, every time, and all three are predictable.

The Instagram account is personal, not business. No API access at all until it is converted and linked to a Facebook Page. 5 minutes for the client, a week if nobody tells them.

Nobody knows who owns the Facebook Page. A former employee, a cousin, an agency from 2019. Until someone with admin rights grants access, nothing can be connected.

The Google listing is unverified or claimed by someone else. Verification can take days and sometimes involves a postcard. Start it on day one or it blocks the entire local programme.

None of this is difficult. It is all slow, and it only becomes slow if you discover it in week two.

The pre-flight message

Send this before the kickoff call, not after. It converts a week of back-and-forth into one reply.

Ask them to confirm, in writing:

• Which accounts exist, with the exact handle for each
• Whether Instagram is a Business or Creator account, and which Facebook Page it is linked to
• Who has admin on the Facebook Page and the Business Manager, by name
• Whether the Google Business Profile is verified, and who holds it
• Whether a Snapchat Public Profile exists, if that is in scope
• Which accounts they want us to touch, and which are off limits

That last line saves an argument later. There is always one account someone in the family runs.

Connect by permission, never by password

Do not accept a password. Not for convenience, not because the client offers.

Every platform has a proper permission model: Business Manager roles on Meta, page admin on LinkedIn, channel permissions on YouTube, manager access on Google Business. Use them. The client keeps ownership, you get access, and when the relationship ends they revoke it in one click without changing a single password.

A shared password is also a straightforward security problem, and if you handle EU clients it is one you would have to explain in a breach notification.

Every serious tool connects through the platform’s own login screen and stores a revocable token. If something asks you to type a client’s password into it, that tells you what you need to know about it.

The audit before you post anything

2 hours, before the first piece of content. It is also the best first deliverable you will ever send.

The Google listing, field by field. Hours including holidays, categories, services with prices, attributes, action links, photos from this year. Most listings are half empty and this is the highest-return hour in the whole onboarding.

Unanswered comments and reviews. There will be months of them. Clearing the backlog in week one is visible, cheap, and occasionally recovers a customer.

What actually worked before you arrived. Their best posts from the last year, before you overwrite the approach with your own. Sometimes the thing that works is the owner’s phone camera, and replacing it with polished graphics makes performance worse.

Bios, links and handles. Consistent name, working link, current description. 10 minutes, always wrong somewhere.

The first week, in order

Day one. Send the pre-flight list. Start Google verification if it is needed, because it is the only thing with a queue you cannot control.

Day two. Connect everything that can be connected. Note what is blocked and who has to unblock it, by name.

Day three. Run the audit. Send it as a short document. This is when the client decides you were worth hiring.

Day four. Clear the comment and review backlog. Agree tone for replies while you are in there.

Day five. Build 2 weeks of calendar and get it approved. 2 weeks, not a month: you do not know enough yet, and a month of content built on a wrong assumption is a month wasted.

What to write down while it is fresh

The things you will otherwise ask twice.

Who approves content and how fast they actually reply. Which topics are off limits. The one competitor they do not want mentioned. Whether the owner wants to be in photos. Which of their own past posts they liked.

Keep it in one page per client, somewhere the whole team can see. In a year it is the difference between an account anyone can cover and an account that only one person understands.

EngageDigital connects every account through the platform’s own login, never a password, and imports past posts on day one so the reporting does not start from empty. See how it works for agencies or start free.

Who this actually affects

Start with the number, because it changes how seriously people take the rest. Somewhere around one in 20 people has a vision impairment significant enough to affect how they use a phone. On an account with 10,000 followers that is several hundred people for whom your post is a blank.

Screen readers announce alt text where it exists. Where it does not, Instagram and Facebook substitute an automatic guess, which produces things like “may be an image of one person and text”. Technically a description. Useless as one.

And it is not only permanent impairment. It is a cracked screen, bright sun, a slow connection that never loads the image, and anyone who has turned images off to save data.

What each platform gives you

Instagram. Alt text per image, including every slide of a carousel up to 10. This is the one most often missed, because it is per slide rather than per post.

Threads. Per image, on up to 10 files.

Bluesky. Per image and, unusually, on video too. Still rare across the industry.

Pinterest. Alt text up to 500 characters, and it does double duty: Pinterest is a search engine wearing a feed, so the description does ranking work as well as accessibility work.

LinkedIn and Mastodon. Per image.

X. Per image, though it is easy to skip in most tools.

Video captions are a separate problem with a bigger audience. Most video on social is watched with sound off, which means captions are not an accessibility extra; they are the only way most people consume it at all.

How to write one that works

Alt text is not a caption and it is not a place for keywords.

Describe what matters, not everything. “A barista pouring a flat white, seen from above” beats a full inventory of the counter.

Read the text in the image. If a slide says “3 ways to cut your reply time”, the alt text says that. An image of text with no alt text is completely lost.

Keep it to a sentence. Around 125 characters is the practical limit before a screen reader gets tedious.

Skip “image of”. The screen reader already said it is an image.

Decorative means empty. A background texture with nothing to communicate should have empty alt text rather than a description of the texture.

The carousel problem, specifically

A carousel is usually a sequence: a hook, then steps, then a conclusion. Each slide is a separate image with separate alt text, and treating them as 10 independent descriptions loses the thread.

Write them as a sequence too. Slide one sets up what the carousel is. Slides two to nine each carry their own point. The last one carries the call to action, because a listener who reaches the end should know what to do next, the same as everyone else.

It takes about 4 minutes for 10 slides. That is the entire cost.

Where AI genuinely helps

This is the one part of social media work where generated text is unambiguously better than the alternative, because the alternative is nothing.

A model reads the image and produces a usable description in a second. It will miss context it cannot see, so skim it and fix the one in 10 that is wrong. But the comparison is not “AI alt text versus excellent hand-written alt text”. It is “AI alt text versus a blank field”, and the blank field is what almost everyone ships.

If your tool can generate it per slide, the 4 minutes becomes 20 seconds and the excuse disappears.

The reach argument, for the sceptics

If accessibility on its own does not move the decision, there is a second reason.

Alt text is text the platform can read. On Pinterest it directly affects whether a pin surfaces for a search. Across the others, it is one more signal about what the post is, in a system that mostly guesses from engagement.

It will not transform your reach. It costs 4 minutes and helps several hundred people per 10,000 followers actually see what you published, which is a better return than most things on the calendar.

EngageDigital exposes alt text per carousel slide rather than one field per post, and can draft it from the image itself. See how publishing works or start free.

Why the usual report fails

The standard version is a dashboard export with a follower count at the top. It fails for 3 reasons.

It answers a question nobody asked. The client does not want to know their impressions. They want to know whether this is working and what happens next.

It cannot be checked. Blended scores and invented indices sound authoritative and mean nothing. A client who asks how a figure was calculated should get an answer in one sentence.

It has no opinion. A page of numbers with no interpretation transfers the analysis back to the person paying you to do it.

The five-page structure

Long enough to be substantial, short enough to be read. This shape works for almost any client.

Page one: what we did. Posts published, by network, against what was planned. Boring and essential. A client paying a retainer is buying consistency first.

Page two: what happened. The real platform metrics, named in each platform’s own terms. Reach on Instagram, impressions on LinkedIn, views on TikTok. Never blended, never summed into a total that means nothing.

Page three: what worked. The three best posts and the three worst, with a sentence each on why. This is the page clients actually read, and the one that is impossible to automate.

Page four: what we learned. Comments and reviews, response time, the questions people kept asking. 20 comments about delivery is a product page problem, and telling them that is worth more than any impression count.

Page five: what next. Three specific things you will do differently, and anything you need from them. A report that ends without a decision is a newsletter.

Metrics to include

Publishing consistency. Planned versus published. If it slipped, say so on page one rather than hoping nobody notices.

Reach or impressions, per network, unblended. Label whether each is reported or derived.

Engagement rate with its denominator stated. Per impression and per follower are different numbers with the same name. Pick one and keep it for a year.

Response time on comments and reviews. Almost nobody reports this and it is the metric a client can feel.

Referral traffic. From the website analytics, not the platform. It survives every API change and it is closest to money.

Search terms, for local clients. The monthly search terms from the Google listing, next to calls and direction requests, beat every social metric for a business with a shopfront.

Metrics to leave out

Follower count as a headline. It moves slowly, it is easily bought, and it tells you nothing about the month.

Any invented composite score. If you cannot explain the formula in one sentence, it does not belong in a document with your name on it.

Cross-network totals. A TikTok view and a LinkedIn impression are not the same event. Adding them produces a bigger number and a smaller truth.

Anything from a network that reports nothing. X, Discord and Slack give no analytics to any tool. Report activity there, and put a dash where the number would be.

The page that keeps clients

Page three. 3 posts that worked, three that did not, and a sentence of judgement on each.

It is the only part of the report that proves a person was involved. Everything else could have been generated. This is where the client sees that someone looked at their account and formed a view, and it is the reason they renew.

The sentences do not need to be clever. “This one worked because it answered a question 3 people had already asked in the comments” is enough, and it is more than most agencies write all year.

Cadence and format

Monthly for most retainers. Quarterly for a strategic review with year-on-year comparisons, which only exists if someone has been storing history since day one.

Send it as a document, not a dashboard login. Clients do not log in. They forward a PDF to someone who was not on the call, and that person needs it to make sense alone.

Send it on the same date every month. A report that arrives on the third Tuesday is a system. One that arrives when someone remembers is a favour.

EngageDigital keeps full analytics history from the day an account connects and exports per client, so a quarterly review can look back further than a month. See how reporting works or start free.

Why the gaps exist

Social analytics do not come from measurement. They come from an API returning numbers the platform chose to expose, under rules the platform changes without consulting anyone.

3 things follow from that, and all three surprise people.

The metrics differ by network. Reach on Instagram, impressions on LinkedIn, views on TikTok. They are not the same measurement, and stacking them into one total is arithmetic that means nothing.

The history is short. Most platforms expire their numbers after about 30 days. If nobody stored a snapshot, last March is gone for everyone.

Some networks return nothing. Not less than you want. Nothing.

The three with no analytics at all

X. Reading engagement data now sits behind enterprise pricing. You can publish and you cannot measure. Anyone showing you X engagement numbers has derived them from something else.

Discord. No analytics API exists, for anyone. What you can report is that the post went out, to which channel, when.

Slack. Same. No message analytics are offered to third-party tools at all.

For these three the honest report line is a dash and a footnote, not a zero. A zero implies nothing happened. A dash says nobody can see.

The ones with partial data

Reddit gives post-level metrics — score, comments, upvote ratio — and almost nothing at profile level. No follower analytics worth the name.

Threads covers only content published after April 2024, when its API opened. Older posts return nothing, for everyone.

Bluesky returns follower counts and basic engagement. Impressions are derived rather than reported, which is a calculation, not a measurement, and should be labelled that way.

Mastodon collects very little by design. That is the point of the network, and no tool can give you more than the instance holds.

Google Business Profile has no per-post analytics. Instead it gives location impressions and the monthly search-terms report, which is more useful than post data for a local client but arrives in a different shape.

What a client actually needs to be told

Not at the end of the quarter. At the start of the engagement, in the proposal.

The sentence that works: “11 of the 15 networks we publish to report performance data. Three report none, because their platforms do not offer it to any tool. For those we report activity and outcomes instead.”

2 things happen when you say this early. The client stops asking for a number that does not exist, and they start trusting the numbers that do — because you were the one who told them where the edges are.

Reporting the unmeasurable networks

A dash in a table is honest but unhelpful on its own. 3 things can be reported for Discord, Slack and X without inventing anything.

Activity. Posts published, on schedule, to which surface. A client paying for consistency can see consistency.

Downstream effect. Referral traffic in the website analytics, which the platform does not control. This is the one number that survives every API change.

Qualitative. Screenshots of the thread, the reply, the reaction. Unfashionable, and frequently the most persuasive page in the report.

The history problem, and why it compounds

The 30-day window is the gap people notice last and regret most.

Everything looks fine for the first month. Then a client asks how this September compares with last September, and the answer is that nobody kept it. Not the tool, not the platform, not you.

The fix is unglamorous: a daily snapshot, stored, from the day an account is connected. It is the most expensive thing to promise because the storage never stops growing, and it is the only way a year-on-year comparison exists at all.

If you are choosing a tool, ask exactly one question about analytics: does the history start when I connect the account, or does it roll? The answer tells you whether you can write a proper annual review 12 months from now.

What good looks like

A report that can be defended line by line. Metrics named by their platform’s own term rather than blended into a single invented score. Gaps shown as gaps. Derived numbers labelled as derived.

It is less impressive than a dashboard with a big number on it, and it is the only version that survives a client who reads carefully.

EngageDigital snapshots analytics daily and keeps the full record, and shows a dash where a platform gives nothing rather than filling the space. See how reporting works or start free.