# Methodology: profile readings and calculations

Ganicly methodology explains public profile readings, calculation methods and data refresh timing so you can interpret each metric. Learn more.

## Every number, and where it comes from.

Ganicly makes every number checkable: each one is either a reading of your public profile or arithmetic on a published range, and this page shows which is which.

## Where each number comes from

If a figure is not in this table, it is not on the site.

## The arithmetic, written out

#### Engagement rate

(average likes + average comments) ÷ followers × 100, across up to 24 recent public posts. Saves, shares and sends are not public, so they are not in it. A carousel counts once.

#### Follower ratio

followers ÷ following, rounded to one decimal. Nothing is inferred from it beyond what the page says: it is a signal a visitor reads in one second, not a quality score.

#### Consistency

100 − (standard deviation of likes ÷ average likes × 50), clamped between 10 and 100, over the sample. High means posts land in a tight band around your own average, not that they are good.

#### Account score

engagement × 0.35 + audience × 0.20 + growth potential × 0.20 + content × 0.25. Each part is bounded 0 to 100 and each is shown separately, because a single number hides which part is weak.

#### Projection

The midpoint of the plan's published monthly range, spread evenly over 30 days, then held to the daily ceiling for an account that size. No compounding is assumed and no virality is modelled.

#### Daily cap

60 a day under 1,000 followers, 100 to 10,000, 150 to 50,000, 200 above. The cap beats the plan: a small account on a big plan receives up to its daily cap, and the plan's guaranteed minimum is held to what that cap allows.

## The bands we judge a rate against

Engagement falls as an account grows, so a rate without a band is meaningless. These are the numbers the scan and the free tools use, per network.

## Private numbers, and what we show instead

Some numbers live only inside your own app insights. Rather than estimate them, the dashboard shows the closest public reading and says which one it is.

## Every number stays checkable

Your dashboard is always measured against the app itself, so you have a second opinion built in: open your profile and the two should agree. If they ever do not, the app wins and we want to hear about it. You will get a straight answer about what happened, from a person, rather than a figure that quietly changes overnight.

Two limits we publish rather than paper over: a scan waits its turn when the platform is busy, and a private profile stays private, exactly as it should. In both cases the screen tells you precisely that, so what you see is always a real reading or an honest explanation, never a zero dressed up as a measurement.