Reports
Read the board of items a digest keeps, look back through past versions, and decide who else gets it — by link or by email.
A report is the document a digest keeps current. It sits in the middle pane of the Smart Digest page: a board of the items that cleared the digest's bar, plus coverage charts drawn from the pages it read.
What a row holds
The board has one row per item the digest tracks, in four columns:
| Column | What it shows |
|---|---|
| Item | The name the agent gave the item, tagged new or updated when it moved this refresh |
| What it is | One line on the item, from the point of view in your brief |
| Latest change | What changed most recently and why it matters |
| Reported by | The pages behind the item, each shown as its site's icon and linking to the page |
Above the board, Since the last refresh lists the items that moved this refresh. What the agent writes into each cell follows the brief — a competitor digest records the move and what it means for your company, a brand digest records what was said and in what tone — so ask the agent to change it when a column reads wrong.
Refreshes
A digest refreshes on its own cadence: Hourly, Every 6 hours, Every 12 hours, Daily, or Weekly. Every cadence except Hourly runs at a clock time you pick, and Weekly also takes a weekday. The schedule control in the header shows the cadence and the next run, and opens the fields that change them.
In the digest list, a green dot means the digest is on its schedule, a hollow grey dot means it is paused, and a pulsing amber dot means a refresh is under way.
Run now refreshes the report outside its schedule. A refresh reads the new matches, judges them, and re-renders the report, so it takes minutes rather than seconds; the button reads Refreshing… until the new report lands. A refresh that fails leaves the previous report in place and the header says so, with the error behind Last refresh failed.
The header's More digest settings menu (⋯) holds the rest: email notifications, pause and resume, and delete.
A refresh, scheduled or manual, is free, so press Run now as often as you like. See Cost.
History
Every refresh keeps the report it replaced. A digest stores its 200 newest reports and drops the oldest beyond that. Open the history menu beside the timestamp to read any of them; the menu appears once a digest has more than one report.
Pause and resume
Pause schedule stops future refreshes. A paused digest keeps its reports, its rules, and its cadence — nothing is scheduled until Resume schedule. A refresh already under way is not affected by a pause.
A digest and its tap move together. Pausing the digest pauses its tap, so the tap's rules stop matching and its feed goes quiet. Pausing the tap — from the Taps page, over the API, or by a plan downgrade that leaves more active taps than the new plan allows — pauses the digest with it. Resuming either one resumes both. A paused tap doesn't count toward the plan's active-tap limit, so resuming can be refused at the limit; pause or delete another tap first, or upgrade the plan.
A digest the agent is building or redesigning also reads as paused in the list, but its tap stays active so the agent can test rules against live matches. It returns to the schedule when the agent publishes.
Email notifications
Email notifications are off by default and belong to the digest rather than to your account. Turn them on from Email notifications… in the ⋯ menu.
With them on, a refresh that keeps at least one new item mails a summary to the digest's owner: the run's one-line summary, the items that are new or updated with what changed, and a count of what is on the board. The subject says how many items moved, so a mail arrives when the report changed. Each mail carries an unsubscribe link that turns the setting off straight from the mail.
The report, with its sources, is one click away at Open report.
Sharing by link
Share publishes the digest at a link on firehose.com. Anyone with the link reads the current
report and its history, with no Firehose account.
- The link covers the digest, not one report, so a reader who opens it later sees the newest refresh.
- Shared pages carry a noindex header, so search engines leave them out.
- Turning sharing off destroys the link permanently. Sharing again publishes a different link, and the old one stays dead.
The link is the only thing a reader needs. Anyone who receives it, or is forwarded it, can read the report and everything in its history, so share it as you would a private document.
Next steps
Refine a digest
Change what's kept, the point of view, and the layout in chat.
Smart Digest overview
How a digest fits beside Stream and URL Watch, and what it costs.