How to tell whether sharing or recommendation carried a viral spike

"Viral" is an analogy worth taking seriously, because it says something precise. An infection spreads when each case produces, on average, more than one further case. Below that line, it dies out however dramatic the individual cases are.

Spread on a platform obeys the same arithmetic. Each view has to produce, on average, more than one further view, and it must do so before the item's window closes.

That single ratio is the whole subject. Planning raises it before publishing. Execution times the window. Measurement estimates it from your own numbers rather than from how it felt.

What to take away

Two engines: sharing and recommendation

The two engines feed each other. Sharing produces the early response recommendation looks for. Recommendation produces the audience sharing draws from.

Knowing which engine carried a spike is the first measurement job. It tells you which of your choices mattered. The plain mechanics of how a recommender picks what to push are in what a recommender can and cannot infer.

Planning what can be planned

Participation cost. The trends that spread furthest are cheapest to join. A shape someone can copy in a minute, with their own material, beats one that requires skill. Strip out everything that makes copying hard.

A copyable core. Separate what must stay the same for the thing to be recognizable from what each participant changes. A small fixed core and a large variable part run longest, because each copy is new enough to be worth seeing and familiar enough to be understood.

Hooks for both engines. A reason to pass it on, and a reason to keep watching. Different reasons, and the plan names both.

A ready follow-up. If the ratio does go above one, the window is short. The most common execution failure is having nothing ready when attention arrives. Prepare the second and third item before publishing the first.

What cannot be planned is the spark: why this one, out of a thousand similar attempts, catches. Sparks look inevitable in hindsight and are invisible in advance. The honest plan raises the ratio for every attempt and accepts that most will still sit below one.

Executing on timing

Every trend has a life. A small group starts it, a larger group joins once it is recognizable, volume peaks, then copies outnumber the audience's patience.

Joining early means being seen as part of the thing. Joining at the peak means competing with the most copies for the least remaining attention. Joining after means being seen as late.

Your own feed shows where a trend sits in its life, but your feed is a biased sample. Better: note when you first saw it and how many copies you saw a week later.

Doubling weekly is early. Ten copies a day is the peak. Copies that comment on the trend instead of doing it mean it is over.

Trends at the product layer move more slowly and are easier to time. Content trends, the kind this page is about, are the fastest and least forgiving.

Measuring the ratio from views per hour

You cannot see the ratio directly, but you can estimate it.

Platform fingerprints, as they usually show up. TikTok's For You feed is recommendation-led: a smooth early rise, decided in the first hours. Facebook group and Messenger sharing is sharing-led: clustered arrivals, quiet gaps, a slow start that steps up as groups pass the item on.

Instagram mixes the two, with Reels fed by recommendation and direct messages carrying the clustered tail. X leans on reposts inside a fast algorithm, so a step and a smooth rise often arrive together.

Typical thresholds for organic posts, as working bands rather than measured constants. Below 1.0 the item decays. From 1.0 to 1.2 it buys a few hours. From 1.2 to 1.5 it can hold for a day or two. Above 1.5 it is still climbing when you check.

What sets the bands is how many further views one share, or one recommendation, actually brings.

A worked example. A post takes 34,400 views and 1,000 shares in its first nine hours. That is about 0.03 shares per view. The hourly figures below come from the same post.

If one share brings 40 further views on average, the ratio is about 1.2. The item survives, but only just, and it stops once the groups and the feed slots behind those views are used up.

Plotting template. Record cumulative views at the end of each hour for the first day, then subtract each row from the one below to get views per hour. Use your own numbers. The rows here are illustrative.

Reading the half-life. The peak is 6,000 views an hour, at hours 2 and 3. Half of that is 3,000, which the table reaches at hour 6, so the half-life is about three hours. Hourly views cross 1,500 at hour 9, two half-lives from the peak.

The tool for thinking about this exists in another field: the basic reproduction number. It transfers because the arithmetic of chains does not care what is passed along.

Step 1 is the measurement step that uses it: shares per view times views per share is the same chain arithmetic, and 1.0 is the line between growth and decay.

The related information cascade shows people acting on what others appear to have chosen, not their own judgment. That explains why spread can be large and still say little about the item's quality.

Step 3 is the measurement that uses it: early response is people copying what they see others doing, so compare your first hours against your own baseline before you credit the item.

What a spike does not tell you about your account

A big number is one observation, not a property of your account. A single item that cleared the ratio says the audience was there that week, not that the next item will find it.

The distribution is what you manage. Most attempts sit below one; a few clear it by a wide margin. A plan that assumes the average attempt fails is the only plan that survives contact with the numbers.

Common questions

Something of mine went viral once. Why can I not repeat it?

Because the spark was not yours to control and the ratio was probably only just above one. Repeat what you can plan, and expect the same distribution of outcomes: mostly nothing, occasionally a lot.

Should I join every trend I can?

No. Each one costs production and dilutes what you are known for. Join the ones with low participation cost that fit what you already make, and only while they are early.

Is a paid push the same as a viral spread?

It raises views without raising the ratio. When the push stops, the spread stops, which is the test that tells the two apart.

How do I tell if a spike came from recommendation or sharing?

The hourly shape, and where the viewers came from if your analytics report it. Smooth and early is recommendation. Stepped and clustered is sharing. Both together is the rare case that goes furthest.