Instagram Story navigation counts how viewers move through Stories: Forward advances to your next Story, Next Story moves to another account, Back returns to the previous Story, and Exits records leaving the Stories viewer. Each count records an action; it does not measure unique people or their opinion of your content.
A viewer who taps Forward may still be watching your account. Keep it separate from Next Story when you review where people leave a sequence.
What each navigation metric means
Meta's media insights reference groups these actions under navigation and provides a separate count for each type.
| Metric | Action counted | What to check before interpreting it |
|---|---|---|
| Forward or Taps Forward | A tap to advance to the next Story in your sequence | Was this a quick announcement or a frame with several paragraphs to read? |
| Next Story | A swipe to the next account's Stories | Where was this frame in your sequence, and had you delivered the promised information yet? |
| Back or Taps Back | A tap to return to the previous Story | Inspect both the frame the viewer left and the preceding frame. |
| Exits or Exited | Leaving the Stories viewer | Was this the final frame, and what action were you asking the viewer to take? |
Navigation records the action taken from a Story. A Back count on frame three therefore needs to be read alongside frame two; it is not proof that viewers replayed frame three. The counts alone cannot tell you whether someone understood a point, got distracted or disliked the content.
For access to the native numbers, use Instagram's guide to viewing Story insights. Record the metric names exactly as they appear in the tool you use.
Are forwards and exits bad?
Not automatically. A short opening frame might take a second to read. Tapping Forward could be a reasonable way to reach the demonstration that follows. On a dense instructional frame, the same action raises a different question: did viewers skip the explanation before they could use it?
Someone might tap Back to inspect an earlier detail or to reread instructions they could not follow. If viewers repeatedly move back from a result to the instructions, test a clearer image or fewer steps.
An exit on the final frame also needs different interpretation from an exit before the promised answer. Navigation does not record the reason. Treat each explanation as a hypothesis and check it against replies or the outcome you wanted from the Story.
Compare Stories with the same job
Group Stories by their job: an opening frame, a demonstration and an offer need separate comparisons. Match their position in the sequence and the time since publication. Record those details along with views and navigation counts; a larger audience can otherwise make the raw number of exits look worse.
These invented numbers illustrate a comparison between two versions of the second frame in a product tutorial. Each has 1,000 views when measured at the same age after publication.
| Metric | Version A | Version B |
|---|---|---|
| Views | 1,000 | 1,000 |
| Forward | 630 | 620 |
| Next Story | 150 | 80 |
| Back | 24 | 55 |
| Exits | 70 | 45 |
| Replies | 3 | 12 |
Version B has fewer Next Story actions and exits, while Back taps and replies increased. Read the replies and inspect the preceding frame before deciding that B explains the product better. Questions about an unclear step would lead to a different edit from requests to buy.
The counts do not prove that B caused the change. The audience and the surrounding Stories may differ. If B used a shorter explanation, repeat that change in another comparable tutorial before adopting it for every Story.
Avoid turning navigation totals into a completion rate. These are action counts, and subtracting exits from views does not identify who finished the sequence. Keep reach and views separate when you choose a denominator for any rate you report.
Turn the review into one content test
SmartMetrics Story cards display Taps Back, Taps Forward, Exits and Replies. Review the individual fields alongside the actual Story. If a field is unavailable in your report, mark it as missing; do not enter zero to make the table complete.
For your next monthly Instagram report, record one finding and one edit to test. For example: "Viewers moved to the next account most often on our text-heavy setup frame. Next time, show the finished result first and shorten the setup."
Choose the outcome before publishing the test. For a tutorial, inspect whether replies still ask about the missing step. For a Story meant to send people to a website, measure those visits with tagged links and GA4 alongside navigation. Record the result after the same observation window as the original Story.