Does Bluesky have analytics?

Bluesky has basic visible numbers, but I would not treat the app as a full analytics dashboard.

You can see public signals like likes, replies, reposts, quotes, follower count, following count, and post count. Basic checks stop there. For follower history, post-by-post comparisons, best posting times, weekly growth reports, and account workflow, you need more than the app view.

Use TheBlue.social Bluesky Analytics when you want the account-workflow version.

What Bluesky shows by default

Bluesky gives you the numbers most people expect to see on the post and profile.

  • Likes
  • Replies
  • Reposts
  • Quotes
  • Followers
  • Following
  • Total posts

The numbers help with a quick read. A post with replies is worth opening. A reposted post should make me check whether it reached the right people. Follower movement after a thread tells me whether the attention became an audience.

But the app view is still mostly a current-state view. It lets me inspect a post or profile. It does not give me a proper history of follower gains and losses, a heatmap of when posts get liked, or a weekly report that tells me what changed.

Analytics tools fill that gap.

What Bluesky data can tools read?

Bluesky is built on AT Protocol, so a lot of public Bluesky data can be read through documented APIs.

Bluesky's own developer docs describe feeds as paginated lists of posts. The Viewing feeds docs show author feeds, timeline feeds, and feed generator views. The API reference also documents public app.bsky.* endpoints that can be called through the public Bluesky AppView API.

For analytics, the useful starting points are post records, profile views, feed views, and public engagement counts.

The important boundary is public data versus your own analytics history. A tool can read current public counts, but it needs to check and store snapshots over time if you want trends.

History is the useful part. A post with 20 likes today is only one fact. A post that got 20 likes, 6 replies, 4 reposts, and 3 new followers in a quiet week tells me more.

What a Bluesky analytics dashboard should add

A useful Bluesky analytics dashboard should do more than repeat the numbers already visible in the app.

The minimum I want:

  • Follower growth over time
  • Follower losses, not just the current total
  • Post engagement by likes, replies, reposts, and quotes
  • A way to compare recent posts
  • A heatmap or pattern view for when posts get liked
  • Weekly summaries I can read without opening the dashboard every day
  • Links from the numbers to the next action

The last point is easy to miss. Analytics by itself can become a report you ignore.

Follower jumps send me to new followers so I can follow back the relevant ones. Replies send me into the conversation. A topic that keeps working goes into the next scheduled post. Too many stale follows means I clean up the following list before adding more.

I prefer analytics close to the account workflow instead of a separate report page.

I would also separate public popularity from useful growth. A post can get likes because it landed in a broad feed. Nice, but it may not help the account. For a product or creator account, I care more about whether the post brought relevant followers, useful replies, or a topic I can keep building around. Bluesky's visible numbers start the check. The history decides whether I repeat the move.

How TheBlue.social handles Bluesky analytics

TheBlue.social Analytics is built around the Bluesky account work I check:

  • follower growth and follower changes
  • post likes, replies, reposts, and quotes
  • account growth snapshots
  • when posts tend to get liked
  • weekly growth reports
  • nearby tools for follow-back, cleanup, starter packs, and scheduling

The setup is also tied to the account you connect. For a creator or product account, I want the account I own, the account history, and the next action.

The normal setup flow is:

  1. Create a Bluesky app password.
  2. Connect the Bluesky account to TheBlue.social.
  3. Let the dashboard start collecting snapshots.
  4. Review recent posts and follower movement.
  5. Use the results to decide what to post, who to follow back, and what to clean up.

If you have not created one before, use the Bluesky app-password guide. Bluesky's own User FAQ tells users to generate an app password for third-party apps, and the Bluesky developer docs include the official com.atproto.server.createAppPassword endpoint.

I create one named password per tool. If I stop using the tool, I revoke that password from Bluesky settings.

I also give the first sync a little time. Current post counts are easy to fetch. History needs snapshots. The sooner you connect the account, the sooner you start building the record you wish you had later.

Handle the app password setup carefully. Use a clear label like "TheBlue.social Analytics" so you can recognize it later in Bluesky settings. Save it only long enough to paste it into the tool. If the connection fails, create a fresh app password instead of guessing which old one belongs to which service.

When basic Bluesky numbers are enough

You do not need a full analytics dashboard for every account.

Basic Bluesky numbers are enough when:

  • you post casually
  • you only care whether one post got replies
  • you do not need historical follower changes
  • you are not testing posting times
  • you are not using Bluesky for a product, newsletter, client, or creator workflow

In that case, open the post and read the numbers. Done.

When you should use an analytics tool

Use a connected analytics tool when Bluesky is part of your actual growth workflow.

That usually means you care about questions like:

  • Which posts brought replies from people I want to know?
  • Which topics got reposts without getting useful replies?
  • Did a post bring followers, or only short-term attention?
  • Am I losing followers after certain topics?
  • What time of day tends to get likes for my account?
  • Which new followers should I follow back?
  • What should I schedule next week?

These questions decide what you do next.

When the answer is "post more like this", schedule the next post. When it is "reply more", spend time in the replies. A wrong-audience signal means changing the topic mix. A noisy feed means using cleanup before following more accounts.

For me, the strongest signal is usually replies plus follower movement. Likes are fine, but replies show whether people want to talk. Reposts show reach. Follower movement tells me whether the account is attracting people who may come back.

I also watch for mismatches. A post can get a lot of likes from outside the audience I am trying to build. Another post can get fewer likes but bring three good replies and a few relevant followers. I would rather repeat the second one. The analytics view should help me make that call without opening every old post by hand.

That is the workflow I built TheBlue.social around.

A simple first check

If you are trying Bluesky analytics for the first time, do not overbuild it.

Start with one week:

  • Check your top posts by replies, reposts, and likes.
  • Check whether follower count moved after those posts.
  • Check when those posts were published.
  • Follow back relevant new followers.
  • Clean up obvious low-fit follows.
  • Schedule one or two posts based on the pattern.

Then wait another week and compare.

Keep the comparison small at first. I usually start with three posts that did better than normal and three posts that did worse than normal. I check topic, format, time, and whether I replied after publishing.

The next week's plan gets less random. After a month, the account has enough history for better timing and topic decisions. Keep the notes simple. Track one change. That small loop is the whole habit.

Use the dashboard long enough to make the next decision, then go do the work.

Last updated: July 2, 2026