Lens 02 / Interactions and denominators
Give every rate a denominator
A percentage without a calculation rule is an unfinished sentence. Decide which behavior you are counting, which opportunity you are comparing it with, and why.
Choose the behavior before the formula
A creator publishing an illustrated guide may care about saves because the content is intended for later reference. A community team asking for feedback may care about substantive replies. Combining these actions into a single engagement total can help summarize activity, but it can also hide the difference between attention, conversation and utility.
Start by naming the interaction set. Are you adding likes, comments, shares and saves? Are clicks included? Are your own replies counted? Does the export expose the same actions for every format? Record those choices before calculating. A mathematically correct percentage can still answer the wrong question if its numerator combines unrelated or inconsistently available behaviors.
Definition: an interaction rate
An explicitly defined interaction count divided by an explicitly defined denominator, multiplied by 100. The resulting percentage is meaningful only within those definitions.
Example: saves per reached account
Illustratively, 18 saves divided by 900 reached accounts, multiplied by 100, is 2%. This describes save events relative to reach. It does not establish that 2% of unique people saved unless the platform’s counting rules support that interpretation.
Choose the opportunity you mean
A reach-based rate relates interactions to distinct reached accounts within the platform’s definition. An impression-based rate relates them to exposure events. A follower-based rate relates them to the size of the account’s follower base, including people who may never have seen the content. Each denominator asks a different question.
Follower-based calculations can be convenient when exposure data is unavailable, but do not call them audience response among viewers. Some interactions may come from non-followers, and many followers may not have received the post. Similarly, views can be useful for a video-specific question only when the view definition and interaction scope are understood.
| Calculation | Denominator | Rate |
|---|---|---|
| Interactions / reach × 100 | 800 reached accounts | 5% |
| Interactions / impressions × 100 | 2,000 impressions | 2% |
| Interactions / followers × 100 | 4,000 followers | 1% |
These are three descriptions of the same hypothetical numerator, not three competing grades. Do not select the largest percentage because it looks most impressive. Select the calculation that supports the stated decision, then keep that rule stable across the comparison.

Do not confuse events with people
One account can like, comment on and share the same post. If you add those events, the numerator does not represent distinct engaged accounts. Depending on the counting rules, a combined event rate can even exceed 100%. That is not necessarily an arithmetic error; it may reveal that the numerator and denominator describe different kinds of units.
When a platform offers a distinct “accounts engaged” metric, do not silently substitute it for a sum of interaction events. Label the difference. A report should let another reader reconstruct the calculation without asking which dashboard tile you copied.
The denominator is not a footnote. It is the question your percentage answers.
Aggregate without hiding the choice
Suppose one post receives 10 interactions from 100 reached accounts and another receives 10 from 1,000. Their individual rates are 10% and 1%. The simple average is 5.5%. Dividing the combined 20 interactions by the combined 1,100 post-level reach counts gives approximately 1.82%. Neither figure is interchangeable with the other.
The simple average gives each post equal weight. The pooled calculation weights posts by the denominator. Also, summed post-level reach is not necessarily distinct audience reach across the whole period: the same account may appear in several posts. Describe the pooled result as interactions relative to summed post reach, not as a unique monthly audience response rate.
Handle missing and unstable data honestly
A zero denominator does not produce a valid rate. Report it as not available, investigate whether the export is incomplete, and do not replace it with zero percent. Very small denominators produce volatile percentages: one extra action can make a result look dramatically different without providing much new evidence.
Keep the counts visible beside the rate. Round consistently and avoid presenting tiny differences with excessive decimal precision. If a platform estimates reach or later revises counts, a precise-looking percentage remains based on uncertain inputs. The formula does not remove that uncertainty.
Write a calculation note you can reuse
A compact note should include the objective, interaction list, denominator definition, time window, paid or organic scope and aggregation method. State any excluded actions or unavailable fields. If comparing Instagram, TikTok, LinkedIn, Facebook or Pinterest, first verify that the available definitions support the comparison; identical labels do not guarantee equivalent measurements.
Next, align the reporting conditions. A well-labeled rate is necessary for comparison, but differences in content age, format and distribution can still make the conclusion misleading.
Check the comparison