Blog Operations

How to Read Stackora Analytics (Advanced Plans)

The Analytics page summarizes email volume, summarization success, digest density, and action patterns. Here is how to interpret each block and what to change when the picture looks wrong.

| | 3 min read

Analytics unlocks on plans that include the Advanced analytics feature. If you do not see /analytics, everything below still helps you reason about dashboard trends — but the numbers live behind that gate.

Volume and summarization health

Emails received counts everything that hit your intake window. Summarized shows how many were processed into structured items, and the UI derives a success rate between them.

How to read it

  • A summarization rate that suddenly drops often means forwarding rules changed, provider throttling, or a burst of mail types the parser rejects (blank bodies, oversized attachments).
  • A rate stuck near 100% while you feel overwhelmed usually means you are forwarding too much — the pipeline is healthy, but your scope is not.

Levers: tighten Gmail or Outlook filters; add ignore lines under Intelligence; unsubscribe or downgrade noisy senders in Subscriptions.

Daily average and peak day

These describe rhythm, not quality.

Spikes that line up with newsletter days or billing cycles are normal. Spikes with no explanation often trace to a new mailing list or a school blast you forgot to chunk into its own filter.

Levers: split high-volume sources into dedicated forwarding rules so you can pause one without touching the others.

Digest cadence and density

Digests sent and ~items per digest show whether output chunks are reviewable.

How to read it

  • Single-digit averages usually mean narrow forwarding scope or genuinely low volume — fine if that is intentional.
  • Very large averages week after week mean your review session will drag. Few people process eighty fresh decisions on a Sunday night without fatigue.

Levers: narrow forwarding, strengthen ignore rules, or upgrade scheduling if your plan supports more frequent, smaller sends.

Action items and completion rate

Action items captures items flagged for follow-up. Completion rate shows how often those marks clear.

How to read it

  • Chronic low completion with high creation means either the flags are too aggressive or your review cadence is misaligned with real capacity.
  • High completion with missed real-world deadlines means flags may be optimizing for easy tasks — revisit Intelligence focus rules so urgent mail surfaces first.

Category and importance distributions

Charts break volume into categories (school, travel, finance, etc., depending on detection) and importance buckets.

How to read it

  • One category swallowing the chart is a sign your forwarding scope is dominated by a single source class. Decide whether that matches your goals.
  • Importance skewed entirely to “low” while you still feel chaos usually means urgent mail never reaches Stackora — check filters.

Feedback quality

Thumbs-up and thumbs-down rates are a blunt instrument: they tell you whether the prose and extraction directionally help.

If unhelpful feedback clusters around one sender or template, capture that pattern in focus or correlation hints instead of clicking through every week.

Use the 7 / 14 / 30-day toggles the page provides. One weird Tuesday is noise; four weeks of rising volume is a systems problem.

Good tuning tends to show:

  • Stable summarization rates
  • Predictable digest counts
  • Slow improvement in completion as rules mature

When a long-stable chart moves, assume something external changed — new school portal, new job listserv, a teenage Amazon habit — before you blame Stackora.