Listening alerts and exports
Get told when a Listening topic gets busy, read a daily or weekly briefing, send new posts to a webhook, download a topic's posts as CSV or JSON, and use topics from the API.
Alerts, briefings, webhooks and downloads are all free. Set them when you save a topic, under More in the Keep listening dialog, or later in the topic's Settings (the webhook is set when you save).
There are no emails: alerts show on the topic's page and on the Listening page, and go to its webhook if it has one.
Volume alerts
Alert me when it finds N or more posts in an hour (or a day). When a run takes the topic over that number of new posts in the last hour or day, the topic shows Volume alert: N posts found in the last hour (alert at M), and its webhook gets a saved_query.threshold event with five of the posts.
- It alerts at most once a window.
- An hourly alert needs a topic that runs at least hourly, and a daily one a topic that runs at least daily.
- A run catching up after a long gap doesn't alert.
- With insights on, only posts about the topic count.
Spikes
Spikes need no setting: a topic spikes when a day brings far more posts than usual. See Spikes. Its webhook gets a saved_query.spike event with five of the posts.
Briefings
A briefing sums up a period: how many posts, the change on the period before, the stories (reposts and copies counted once), each platform's posts, the loudest voices and the most engaged posts, and, with insights, how many need a reply and the riskiest posts. Nothing in it is written by AI: every figure comes from the posts kept.
- Daily, 08:00 UTC covers the day before; Weekly, Monday 08:00 UTC covers Monday to Sunday.
- It shows on the topic's page and goes to its webhook as
saved_query.briefing. - A topic gets one only for a period in which it was active and ran.
Webhooks
A topic with a webhook endpoint sends each run's new posts to it as a saved_query.matches event (up to 25 posts, with a link to see the rest), as well as its spikes, volume alerts and briefings. Each post includes its sentiment and insights when those are on. Create endpoints under Monitors → Webhooks, then choose one in the Keep listening dialog. See Webhooks for signatures and retries, and the saved queries recipe for each event's payload.
Download
On a topic's page, Download gives its posts as:
- CSV: the posts it keeps, newest first, for a spreadsheet.
- JSON: every field, as the API gives it.
A download holds the newest 5,000 posts. It includes your corrections to sentiment and relevance.
The API
Topics are saved queries in the API, and the app and the API share them: a topic you save in the app is in the API, and the other way round. The saved queries recipe covers saving one, reading its posts (with the same filters), stats, and every webhook event. To search once without saving, use Search with a query.
Sentiment and insights
Two Listening options that read every post: sentiment (positive, neutral or negative) and insights, which sets aside posts that aren't about your topic, says what each post is, flags what needs a reply or could hurt you, and answers your own yes/no questions.
Costs and limits
What Listening spends credits on, the limits you set on a preview and on each run, a topic's monthly cap, sentiment and insights, how to spend less, and Listening's other limits.