A slideshow can get views without creating product interest, or create strong intent without a large reach number. The useful question is not “did it go viral?” It is “which part of the path did this post improve?”
Organize the dashboard into four layers: reach, attention, intent, and product outcome.
Reach tells you who received the post
Views, unique viewers, traffic source, and audience characteristics help you understand distribution. They are useful for finding out whether the topic reached the intended group.
Reach is not a quality score. A broad hook can attract curiosity from people who do not have the problem, while a narrow tutorial can reach fewer people who are much more qualified.
Attention tells you whether the sequence worked
Look for completion, average watch or view behavior where available, swipe-through patterns, and the slide where people stop. A slideshow earns attention one beat at a time, so a weak third slide can matter more than a strong first slide.
When you see an early drop, ask whether the post made a promise and then delayed the payoff. When you see a late drop, ask whether the CTA arrived before the useful idea was complete.
Intent tells you what viewers wanted to do
Saves, shares, comments, profile visits, and link clicks are different forms of intent. A save often means reference value. A share can mean relevance to someone else. A comment can reveal a question or objection. A profile visit indicates interest beyond the post.
Read the comments, not just the counts. The exact wording can become the next hook, FAQ, or product improvement.
Product outcomes tell you whether the funnel matched
Where attribution is available, connect profile visits or link clicks to store views, installs, activation, and meaningful first actions. The definition of activation should match your app’s real value moment; opening the app is not always the same as reaching the first win.
If you cannot measure installs reliably, do not invent a result. Use qualified comments, link clicks, and user interviews as directional evidence while you improve tracking. A tracked store link in your bio is the cheapest place to start; the install tracking guide shows how to set one up for each store.
Build a simple review table
For each post, record:
- topic and audience,
- hook pattern,
- visual format,
- CTA,
- reach,
- attention signal,
- intent signal,
- product signal,
- and the next hypothesis.
This makes comparisons fairer. You can see whether a hook works only with a listicle, whether a scrapbook style earns more saves, or whether a product demo converts better than a broad category post.
Avoid metric traps
Do not optimize for comments by asking empty questions. Do not judge every post by installs when the goal was awareness. Do not compare a launch post with a customer-support answer without recording the different intent.
Use a primary metric and a guardrail. For a saveable guide, the primary metric might be saves and the guardrail might be qualified clicks. For a product demo, the primary metric might be activation and the guardrail might be completion.
The hook testing guide explains how to turn the dashboard into experiments. ViralSlides makes it easier to produce variants, but measurement is what tells you which variants deserve another week.