Freeze the candidate set
Select channels, dates, or posts from a preceding result so the denominator applies to a known and reproducible comparison set.
Feature · Normalized reactions
Compare Telegram reactions per view on comparable data
Compare reaction-to-view rates for eligible Telegram posts at one shared post-age horizon, with explicit denominators, readiness, exclusions, and citations.
Direct answer. The Ocean can divide a post's captured reaction total by its captured views and rank eligible posts only at one observation horizon reached by every candidate. The analysis shows numerator, denominator, formula, horizon, coverage, and missing reasons. If the youngest post has not reached the shared checkpoint, the ranking is withheld instead of mixing ages.
Research fit
Who this workflow is for
Researchers comparing response intensity across posts of different reach who need an inspectable ratio and refuse rankings built from mismatched post ages, missing views, or zero-filled snapshots.
Choose reactions over views
Define the numerator as reactions_total and denominator as views; do not substitute subscribers or a blended engagement score.
Wait for one horizon
Use a scheduled post-age checkpoint that every candidate has reached and withhold ordering while the youngest post is still maturing.
Read coverage reasons
Distinguish missing views, unavailable metrics, disabled observation, late ingestion, missed snapshots, and data still collecting.
Interpret the rate
Treat the percentage as measured reactions relative to displayed views, not unique people, positive sentiment, or causal impact.
Practical module
Comparable reaction-rate worksheet
The worksheet makes the formula and readiness visible before any post is described as unusually reaction-heavy.
NumeratorCaptured reactions_total at the chosen fixed horizon for each eligible post.
DenominatorCaptured views from the same post and same snapshot; null or non-positive values are unavailable.
Shared horizonOne configured post age reached by every candidate before the ordering is released.
Coverage stateComplete, partial, collecting, or insufficient data with typed reasons for every excluded post.
Result rowsSource, post, numerator, denominator, computed rate, timestamp, and evidence permalink.
InterpretationA bounded comparison of measured response, not proof of agreement, audience quality, or influence.
Analysis contract
What the calculation actually does
For one mature shared target_age_seconds, Chat divides reactions_total by views from the same captured snapshot, orders the resulting values, and attaches coverage state to every candidate.
Scope
Logical posts in selected sources and an optional publication period, or the exact posts inherited from the previous analytical result.
Measured fields
- Reaction numerator
- View denominator
- Reaction-per-view rate
- Fixed horizon
- Coverage status
- Next readiness time
Coverage rules
- Every candidate must first reach the shared horizon
- Missing numerator or denominator is never zero-filled
- Collecting results are withheld until age comparability exists
- Partial results cover only the measured subset
- Typed exclusion reasons remain visible per post
Questions to ask
- Rank these posts by reactions per 1,000 views at one shared horizon.
- Among the same posts, which has the highest reaction-to-view rate on comparable data?
- When will the youngest post be ready for this normalized comparison?
Reactions-per-view comparison recipe
A fixed-horizon formula and coverage checklist for comparing measured reaction intensity without mixing post ages.
For [selected or previously listed posts], compare reactions_total divided by views at one shared post-age horizon. Show numerator, denominator, rate, horizon, eligible/measured/missing counts, every exclusion reason, next readiness time when known, and citations. Withhold a global winner when coverage is partial or collecting.
normalized engagement ranking
reactions_total / views from the same captured snapshot at one shared target_age_seconds horizon.
Inputs to set
- Candidate posts
- A fixed selected-source/date set or exact references inherited from a prior result.
- Numerator
- Telegram reactions_total captured at the shared horizon.
- Denominator
- Telegram views captured in the same snapshot.
- Readiness rule
- All candidates must have reached the chosen scheduled post age.
Expected output
- Ordered reaction/view rates
- Numerators and denominators
- Shared observation horizon
- Coverage state and exclusion details
- Cited post references
Coverage rules
- Never mix different post-age horizons
- Never replace missing views with zero
- Do not name a global winner for partial coverage
- Do not interpret reactions as positive sentiment
- Preserve the exact candidate set in follow-ups
Read the complete resource
# Reactions-per-view comparison recipe A fixed-horizon formula and coverage checklist for comparing measured reaction intensity without mixing post ages. ## Calculation - Mode: normalized_engagement_ranking - Formula: reactions_total / views from the same captured snapshot at one shared target_age_seconds horizon. ## Query For [selected or previously listed posts], compare reactions_total divided by views at one shared post-age horizon. Show numerator, denominator, rate, horizon, eligible/measured/missing counts, every exclusion reason, next readiness time when known, and citations. Withhold a global winner when coverage is partial or collecting. ## Inputs - **Candidate posts:** A fixed selected-source/date set or exact references inherited from a prior result. - **Numerator:** Telegram reactions_total captured at the shared horizon. - **Denominator:** Telegram views captured in the same snapshot. - **Readiness rule:** All candidates must have reached the chosen scheduled post age. ## Expected output - Ordered reaction/view rates - Numerators and denominators - Shared observation horizon - Coverage state and exclusion details - Cited post references ## Coverage checks - [ ] Never mix different post-age horizons - [ ] Never replace missing views with zero - [ ] Do not name a global winner for partial coverage - [ ] Do not interpret reactions as positive sentiment - [ ] Preserve the exact candidate set in follow-ups
Boundaries
What this does not establish
- Views are aggregate counters rather than verified unique people
- Posts without both values at the horizon are excluded
- Partial coverage cannot support a global winner
- Reaction rates do not identify sentiment or authenticity
- The comparison remains limited to selected indexed sources
Founding research pilot
Apply with a reaction-rate comparison
Bring one recurring research job and a small set of public sources. We will assess fit personally before offering a pilot.
Apply for a 14-day research pilot
30 founding researcher places · rolling admission · personal reply within 2 business days
Analytics cluster
More ways to investigate this result
Continue researching
Related guides
Publication notes. This page was reviewed before publication and is scheduled for review by 2026-12-19. Facts used: product-chat-fixed-horizon-ranking · product-chat-coverage-reasons · product-chat-reaction-breakdown · product-citations