Select comparable posts
Use one source/date scope or inherit the exact posts from a previous result before changing the requested metric.
Feature · Normalized forwards
Compare Telegram forwards per view at one post age
Compare captured forwards relative to views at a shared post-age horizon, with transparent formula, collection readiness, missing reasons, and evidence.
Direct answer. The Ocean can calculate forwards divided by views for each eligible post at a single observation horizon shared across the candidate set. It exposes both values, the rate, horizon, collection status, and exclusions. A post still waiting for its checkpoint prevents a premature comparable ranking, and missing counters are not silently replaced with zero.
Research fit
Who this workflow is for
Analysts studying redistribution propensity across posts with different exposure who need one denominator and one post age rather than a raw forward leaderboard or an inferred propagation map.
Define the ratio
Choose forwards as numerator and views from the same snapshot as denominator; keep reactions outside the calculation.
Enforce one age
Wait until every candidate has reached the shared scheduled horizon so a newer post is not penalized for having less observation time.
Audit missing coverage
Read whether a horizon is pending, missed, unavailable, late, disabled, or missing a usable views value.
Avoid propagation overclaiming
Use the rate to compare measured forwarding relative to exposure, not to identify destinations, origin, or coordination.
Practical module
Forward-rate comparison sheet
A complete rate record makes both counters, their shared checkpoint, and excluded posts inspectable.
Forward numeratorCaptured forwards at the selected fixed post-age horizon.
View denominatorCaptured views from precisely the same snapshot and post.
Comparable horizonThe mature scheduled age common to all candidate observation policies.
Coverage detailMeasured and missing candidates plus typed reasons and any predictable next-ready time.
Ordered resultPost, source, numerator, denominator, computed rate, timing, and citation.
Meaning limitA relative redistribution measure, not a map of where content traveled or who shared it.
Analysis contract
What the calculation actually does
At one mature target_age_seconds checkpoint, Chat divides captured forwards by captured views from the same metric row, sorts the rate, and reports the state of every candidate.
Scope
A defined set of logical posts in selected Telegram sources, optionally inherited exactly from the previous analytical answer and its period.
Measured fields
- Forward numerator
- View denominator
- Forwards-per-view rate
- Fixed horizon
- Measured coverage
- Readiness time
Coverage rules
- A shared horizon must be reached by all candidates
- Null forwards or views remain missing
- Collecting data produces no premature ranking
- Partial coverage restricts claims to measured posts
- Each excluded item has a typed reason
Questions to ask
- Rank these posts by forwards per 1,000 views at a shared horizon.
- Which measured post had the highest forward-to-view rate among the same results?
- Show why any candidate is excluded and when comparable data may be ready.
Forwards-per-view comparison recipe
A fixed-horizon specification for comparing forwarding relative to exposure while refusing unsupported propagation conclusions.
Compare [candidate posts] by captured forwards divided by views at one shared post-age horizon. Return numerator, denominator, rate, horizon, coverage status, exclusion reasons, next-ready time where known, and citations. Do not infer destinations or declare a global winner when coverage is incomplete.
normalized engagement ranking
forwards / views from one captured snapshot at the same target_age_seconds for every candidate.
Inputs to set
- Candidate set
- Selected source/date items or exact post references from the preceding result.
- Forward field
- The captured forwards numerator at the chosen horizon.
- View field
- The same snapshot's positive captured views denominator.
- Coverage rule
- The shared age and minimum evidence required before ordering.
Expected output
- Ordered forward/view rates
- Underlying forward and view counts
- Shared horizon and observation timing
- Coverage and missing reasons
- Evidence links for measured posts
Coverage rules
- Do not mix observations from different ages
- Do not infer zero from a null metric
- Withhold an overall winner for partial data
- Do not claim a propagation path
- Keep follow-up scope tied to the prior result
Read the complete resource
# Forwards-per-view comparison recipe A fixed-horizon specification for comparing forwarding relative to exposure while refusing unsupported propagation conclusions. ## Calculation - Mode: normalized_engagement_ranking - Formula: forwards / views from one captured snapshot at the same target_age_seconds for every candidate. ## Query Compare [candidate posts] by captured forwards divided by views at one shared post-age horizon. Return numerator, denominator, rate, horizon, coverage status, exclusion reasons, next-ready time where known, and citations. Do not infer destinations or declare a global winner when coverage is incomplete. ## Inputs - **Candidate set:** Selected source/date items or exact post references from the preceding result. - **Forward field:** The captured forwards numerator at the chosen horizon. - **View field:** The same snapshot's positive captured views denominator. - **Coverage rule:** The shared age and minimum evidence required before ordering. ## Expected output - Ordered forward/view rates - Underlying forward and view counts - Shared horizon and observation timing - Coverage and missing reasons - Evidence links for measured posts ## Coverage checks - [ ] Do not mix observations from different ages - [ ] Do not infer zero from a null metric - [ ] Withhold an overall winner for partial data - [ ] Do not claim a propagation path - [ ] Keep follow-up scope tied to the prior result
Boundaries
What this does not establish
- The rate cannot reveal forwarding destinations or users
- Posts missing forwards or views are excluded
- Collection may still be pending for the youngest publication
- Partial data cannot identify an overall winner
- A high rate does not prove coordination, authenticity, or impact
Founding research pilot
Apply with a forward-rate research question
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-limitations · product-citations