StoriesFly logo
Tool — Analytics

Instagram analytics: an engagement reading built from public profile data.

StoriesFly's Instagram analytics tool reads the three public counters on a profile (followers, following and posts), adds up to 30 events its own tracker has recorded for that account, and has a language model write an engagement reading from exactly those fields. It does not read reach, impressions or saves, because Instagram serves those to the account owner alone. A run needs a signed-in paid plan, since each one costs a model call.

What you enter@handle

public fields onlyplus tracker recordsaccount required

Fig. 01How deep an outside reading can go
0publicprivatethe three countersthe public post gridtracker events, if the account is watched
what a run actually readsowner only: reach, impressions, saves

The public floorInstagram serves reach, impressions, saves and audience demographics to the signed-in owner of an account and to nobody else. This is the platform's own wall, and it applies to every outside tool equally. Any analytics page that claims those numbers for an account it does not own is guessing.

01Two kinds of report

The owner's insights and an outside reading

The two reports answer different questions. This one says what the public numbers support; the owner's says what happened inside the account. A tool that sells the second while running the first is describing its own guesswork.

Fig. 02Which fields feed which report
Instagram's own insights
their loginreachsavesdemographics

Served to the account that posted, behind its own login. None of it leaves that login.

This analysis
public fieldstracker eventsmodelreading

Built from what anyone can see, plus events our tracker recorded itself while watching the account.

the report this page produces
02Numbers and text

What is read, and what the model writes

The numbers are read, not written: the three counters from the public header, plus up to 30 recent events from the log our tracker keeps while an account is being watched. Nothing in that layer is generated.

The sentences are written by a language model that receives exactly the fields shown on the diagram and nothing else. That limit works in both directions. The model cannot leak data it was never given, and when the input is thin, such as a private header or an account nobody tracks, the reading has to say less rather than invent more.

03Fields on the wire

What goes into a run and what never does

The chips are Instagram's own field names. The third group is the floor spelled out: those keys exist in the owner's responses and never in anything served to us.

The field accepts
@handle
Read on every run
followersfollowingpostsis_private
Never in the input
reachimpressionssaves
04One run, in numbers

Inputs and daily limits

Every run costs a model call, which is what the daily limit is for. The inputs are not padded to look bigger: three counters and up to 30 recorded events are what an outside reading has to work with.

Fig. 03Counters, events and the daily meter
Counters read from the profile
3
Tracker events fed to the model
≤ 30
Runs a day on Basic
10
Runs a day on Pro
no cap
05The run, in order

From a handle to a reading in four steps

What happens after you press analyze.

  1. 01The handle is checkedIt is normalized, validated and looked up on the public surface through one of our sessions, the same fetch every viewer page here uses.
  2. 02The profile header is readFollowers, following, posts and the privacy flag. That is the whole numeric input Instagram gives an outsider.
  3. 03Tracker events join, if there are anyIf the account is being watched, up to 30 recent recorded events (follows, unfollows, gaps between posts) are added to the input. If it is not watched, the model is told it is working from the header alone.
  4. 04The model writes the readingEngagement level, posting rhythm, and what the numbers do and do not support, written only from the input above.
06Out of reach

What a public-data reading cannot show

The first three are Instagram's boundaries. The fourth is our daily meter.

  • 01Reach and impressions for accounts you do not ownInstagram serves these to the account owner only. No outside tool reads them, whatever its landing page says, and the floor on the diagram is that fact drawn.
  • 02Private accountsThe public header still arrives, so you get the counters and the privacy flag, and the reading says openly that it worked from the header alone.
  • 03History nobody recordedTracker events begin when tracking begins. There is no archive of past activity to import, so an account watched since yesterday has one day of context.
  • 04Runs without a paid planEach run costs a model call, so runs are metered per account: 10 a day on Basic, uncapped on Pro. Free accounts get no analysis runs.
07Questions about the report

Before you run an analysis

Is this the account's real reach?

No. Reach and impressions are served only to the account owner, so no outside tool has them. What you get here is what public data supports: an engagement reading from public counts and a posting rhythm from recorded events.

Do I need an account to run it?

Yes. Each run costs a model call, so it is tied to a signed-in paid plan: 10 runs a day on Basic, uncapped on Pro. Free accounts cannot run an analysis.

Will the analyzed account know?

No. The report is built from public-surface fetches made by our sessions, which is the same kind of request as opening the profile page. Instagram sends no notification for that.

Why does the page keep mentioning the tracker?

Because the tracker is where the extra depth comes from. Without it the input is the public header alone; with it, up to 30 recorded events join the input, and those are events our own sweeps observed rather than data Instagram hands over.

Can it analyze a private account?

It analyzes what a private account shows, which is the header: followers, following, posts and the privacy flag. The reading states that limit instead of presenting thin input as insight.

How current are the numbers?

The counters are fetched when you press analyze. The recorded events are as fresh as the last sweep for that handle, and sweeps run on the tracker's own schedule, every 180 minutes on Pro and every 240 on Basic, not on your click.

Is the text written by AI?

Yes, and the model receives only the fields listed on this page. It cannot use hidden data because it is never given any, and thin input produces a shorter reading rather than an invented one.

How is this different from the account analyzer?

This page reads one account's surface as it stands today and writes an engagement summary from it. The account analyzer compares dated snapshots to show what changed over time. Both stop at the same public floor.

Run a report on an account you actually care about.

The reading uses the public surface exactly as it stands today.

Run the analysis