Skip to content

Glossary

A reference for the numbers you see across the dashboard. Open it whenever a card, column, or tooltip leaves you wondering “computed how, exactly?”.

A single instance of a reader tapping a question inside the Elephany widget on your site. Every tap is one ad impression in the answer drawer, so taps and impressions are 1:1.

This is the dashboard’s most fundamental count. Most other numbers derive from it.

A unique reader who tapped at least one question during the selected period. Shown on the Reader depth KPI card as the count beneath the headline number.

How many questions an engaged reader tapped on average.

readerDepth = questionTaps ÷ engagedReaders

Higher means readers are following one question with another rather than bouncing after the first answer. The Overview tab also surfaces this as a daily series in the trend chart’s Reader depth toggle (plotted on a fixed 0 to 5 y-axis for legibility).

Total reader attention captured by the widget across the period, summed over all readers. Shown in hours and minutes on the KPI strip.

This is cumulative, not an average per reader. A site with 1,000 readers spending 10 seconds each would show “2h 47m”.

Your publisher revenue per 1,000 ad impressions. You enter this directly in the dashboard. The Estimated ad value card has an editable input for it.

The default placeholder is $30. Replace it with your real number from your ad-network report so the projection reflects your actual monetization.

The portion of your ad revenue attributable to question taps in the selected period.

adValue = questionTaps × RPM ÷ 1000

The math: one ad shows in the answer drawer per tap, so taps are impressions, and revenue = impressions × RPM ÷ 1000 is the standard CPM formula.

A linear extrapolation of adValue to a full year, normalized by the selected period length.

projectedAnnual = adValue × 365 ÷ periodLength

The ÷ periodLength matters. A 7-day total of $95 is not $95 × 365 (that would imply $95 per day). It’s (95 ÷ 7) × 365, about $4,955: the daily rate annualized.

The date window the dashboard is currently scoped to. Set via the Period chip in the header.

  • Last 7 days. Ends at the most-recent available day (today minus 3), goes back 7 days.
  • Last 30 days. Same anchor, goes back 30 days.
  • Custom. Any range you pick on the calendar.

The chosen period applies to every metric on the page: KPIs, trend chart, recipe table, and recipe peek.

The dashboard reports through today minus 3 days. The lag covers the time it takes for analytics events to land, deduplicate, and roll up reliably.

If today is Wednesday, the most-recent data point is from Sunday. The “Last 7 days” preset will read Sunday back to the previous Monday, not yesterday back 7 days.

The widget itself runs in real-time on your site. Only the reporting view is delayed.

A timestamped change to your Elephany setup or to the underlying model. For example, “Auto Injection Enabled” or “Model objective updated”. Release notes appear as small flag-pin markers above the top of the trend chart on the day they were published. Hover a pin to see the note text and the formatted date.