Radar · Engagement anomaly

Detect Telegram engagement spikes with comparable evidence

Detect unusually strong Telegram post engagement against each selected channel's own comparable history, with evidence, coverage, and timing controls.

Direct answer. The Ocean Radar can flag a recent Telegram post when reactions, views, or forwards are unusually strong relative to comparable posts from the same source. The comparison requires a shared post-age horizon and enough history. Each signal keeps the metric, baseline, window, evidence post, confidence, and coverage; it is a review lead, not proof that a post is viral or influential.

Research fit

Who this workflow is for

Researchers monitoring selected public Telegram channels who want early notice of unusual post performance without comparing young posts with mature counters or relying on an unexplained importance score.

01

Select monitored sources

Choose the public Telegram channels relevant to one beat or investigation; Radar does not discover or monitor every Telegram channel automatically.

02

Choose an evaluation window

Use the 24-hour, 3-day, or 7-day Radar window and keep its meaning separate from the post-age horizon used to compare engagement.

03

Require comparable snapshots

Compare a recent post only at a captured horizon also reached by enough historical posts from that same source.

04

Inspect the trigger

Review the observed metric, source-specific baseline, confidence, measured and missing coverage, and the cited post that caused the signal.

05

Validate the explanation

Open the message and surrounding channel activity before attributing the spike to content, promotion, coordination, audience growth, or an external event.

Practical module

Engagement-spike review card

The card makes the anomaly calculation inspectable and keeps the alert useful even when a reviewer ultimately rejects its significance.

Signal metricThe single captured field—reactions, views, or forwards—that exceeded the comparable source baseline.
Shared horizonThe post age at which both the recent post and historical reference posts were measured.
BaselineThe same channel's eligible historical distribution, sample size, and comparison period.
CoverageMeasured, missing, still-collecting, and unavailable posts plus any next readiness time.
EvidenceThe triggering message text, publication time, captured value, and direct Telegram permalink.
Review outcomeRelevant, expected, noise, or unresolved, with a short analyst note for future tuning.

Analysis contract

What the calculation actually does

Radar compares a recent post's captured reactions, views, or forwards at a shared post-age horizon with eligible historical measurements from the same source, then emits a signal only when readiness and anomaly rules are satisfied.

Scope

Selected ready Telegram sources evaluated over a configured 24-hour, 3-day, or 7-day Radar window. Historical comparison remains source-specific and excludes unmeasured posts from numeric baselines.

Measured fields

  • Triggering engagement metric
  • Comparable post-age horizon
  • Source baseline
  • Historical sample size
  • Coverage state
  • Signal confidence

Coverage rules

  • Recent and historical posts must share a measurement horizon
  • Missing metrics are not zero-filled
  • Collecting and unavailable states remain distinct
  • Weak history can suppress or lower confidence in a signal
  • Every signal retains at least one evidence post

Questions to ask

  • Alert me when a post has unusual reactions for its own channel at a comparable age.
  • Which monitored post triggered an engagement spike today and what baseline was used?
  • Show engagement anomalies with measured and missing coverage.

Comparable engagement-spike recipe

A reviewable specification for identifying unusually strong recent post metrics without mixing measurement ages.

Copy-ready query

For [selected sources] in the [24-hour, 3-day, or 7-day window], report engagement-spike signals. For each, name the metric, shared post-age horizon, observed value, source baseline, historical sample, confidence, coverage states, publication time, and evidence link. Do not describe a signal as viral or causal.

Deterministic calculation

radar engagement spike

Compare one recent captured metric at horizon H with the same source's eligible historical values at H; emit only when readiness, sample, and anomaly thresholds pass.

Inputs to set

Source set
Public indexed Telegram channels selected for Radar.
Radar window
The recent 24-hour, 3-day, or 7-day evaluation period.
Metric readiness
Comparable captured horizons and coverage states for recent and historical posts.
Review threshold
The anomaly and confidence rule used to create a triage item.

Expected output

  • Trigger metric and observed value
  • Comparable horizon and source baseline
  • Historical sample and confidence
  • Coverage and readiness state
  • Cited triggering post

Coverage rules

  • Never compare unequal post ages silently
  • Never treat missing metrics as zero
  • Keep baselines source-specific
  • Treat signals as review leads, not causal findings
  • Open the cited post before escalation
Download Markdown resource
Read the complete resource
# Comparable engagement-spike recipe

A reviewable specification for identifying unusually strong recent post metrics without mixing measurement ages.

## Calculation

- Mode: radar_engagement_spike
- Formula: Compare one recent captured metric at horizon H with the same source's eligible historical values at H; emit only when readiness, sample, and anomaly thresholds pass.

## Query

For [selected sources] in the [24-hour, 3-day, or 7-day window], report engagement-spike signals. For each, name the metric, shared post-age horizon, observed value, source baseline, historical sample, confidence, coverage states, publication time, and evidence link. Do not describe a signal as viral or causal.

## Inputs

- **Source set:** Public indexed Telegram channels selected for Radar.
- **Radar window:** The recent 24-hour, 3-day, or 7-day evaluation period.
- **Metric readiness:** Comparable captured horizons and coverage states for recent and historical posts.
- **Review threshold:** The anomaly and confidence rule used to create a triage item.

## Expected output

- Trigger metric and observed value
- Comparable horizon and source baseline
- Historical sample and confidence
- Coverage and readiness state
- Cited triggering post

## Coverage checks

- [ ] Never compare unequal post ages silently
- [ ] Never treat missing metrics as zero
- [ ] Keep baselines source-specific
- [ ] Treat signals as review leads, not causal findings
- [ ] Open the cited post before escalation

Boundaries

What this does not establish

  • Comparable engagement snapshots may still be collecting
  • A statistical anomaly does not explain its cause
  • The signal covers only selected indexed public sources
  • Small source histories can produce weak or unavailable baselines
  • High engagement does not establish truth, influence, or coordinated behavior

Founding research pilot

Apply with an engagement-spike monitoring task

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-radar-signals · product-radar-windows · product-chat-fixed-horizon-ranking · product-citations