Measurement & Analytics Methodology
Feym relies exclusively on verifiable, mathematical engagement metrics and market data aggregated from public telemetry. We reject arbitrary opaque scoring and black-box algorithms.
01. Engagement Rate (ER) Calculation Formulas
Engagement formulas reflect each platform’s distinct content distribution mechanics. Rather than a generic blanket metric, we apply tailored mathematical equations:
ER = (Likes + Comments) / Views * 100%
Calculated from the median of the 10 most recent long-form uploads (excluding Shorts to isolate sustained attention).
ER = (Likes + Comments) / Followers * 100%
Calculated across a rolling sample of the last 12 grid publications (images, reels, carousels).
ER = (Likes + Comments + Shares) / Views * 100%
Calculated based on the last 20 video publications on the public profile timeline.
02. Audience Quality Score (AQS) – Bot Detection
The AQS metric evaluates follower integrity on a 1–100 scale using multi-vector behavioral telemetry:
- ✓ Comment Entropy Analysis: identifying recurring generic emoji patterns and automated spam scripts.
- ✓ Geographic Discrepancy Audits: flagging unusual follower concentrations in foreign geographies discordant with content language.
- ✓ Follower-to-Following Ratios: detecting programmatic mass follow/unfollow patterns typical of click-farms.
03. Data Ingestion Architecture & Rolling Snapshots
Our telemetry pipeline processes market observations in a 24-hour rolling snapshot cadence:
1. Open Telemetry Harvesting
Ingesting public creator attributes (views, likes, comments, subscriber totals) within ethical rate thresholds.
2. Statistical Normalization
Excluding three-sigma statistical outliers to prevent single viral anomalies from corrupting baseline performance.
3. Cohort Median Calculation
Synthesizing benchmark medians across 180 national segments, empowering direct peer-group evaluation.
Methodological Boundaries & Disclosures
Public telemetry estimates operate within inherent network boundaries. These include third-party caching latencies (up to 24 hours) and the inaccessibility of private authenticated metrics (such as private unique reach or save counts), which remain confidential to account owners.