Listening 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.
Listening runs on your Social Fetch credits. Each search it makes is charged at its normal credit price, and never more than the limit you set. Credits a search didn't use aren't charged.
What uses credits
| What | Credits |
|---|---|
| A preview | The searches it runs, up to Spend (50 by default, up to 10,000) |
| A topic's run | The searches it runs, up to its credits per run (20 by default, up to 10,000) |
| Sentiment | 1 per 10 posts given a sentiment, on top |
| Insights | 1 per 10 posts given insights, on top |
Free: writing a query (including Describe it), checking it as you type, Leave out, filters, downloads, volume alerts, spikes, briefings and webhooks. Opening a topic or its posts costs nothing.
The limit is shared between the platforms with something to search. Before you preview, Up to N credits under the query shows the most it can cost. If the limit is too low to give every platform a search, it says which platforms it leaves out, with Raise the limit for X.
A topic's spend
- Each run spends at most its credits per run, plus sentiment and insights for its new posts.
- At most N credits a month in the Keep listening dialog is the most a month of runs could cost at that schedule: runs a month × credits per run, plus sentiment and insights.
- Most runs cost less than their limit: after the first run, each one reads only what's new.
- Change a topic's credits per run in its Settings. A run that stops at its limit shows Partial on the Runs tab; a higher limit reads further back.
- A topic's page shows credits this month, and its Runs tab each run's credits. Your Usage page lists every charge.
Monthly cap
Under More (or later in the topic's Settings), a Monthly cap stops a topic spending more than you choose in a calendar month (UTC), sentiment and insights included. When a run could take it past the cap, it waits: the topic shows Capped, This month's credit cap is spent: it runs again next month, or raise the cap. A cap must be at least one run's credits, or the topic could never run. Raising the cap, or removing it, in Settings lets a capped topic run again straight away.
Spend less
- Run less often. Every 6 hours is plenty for most brands; Every day for a quiet topic.
- Lower the credits per run in Settings once you see what a run usually costs on the Runs tab.
- Make the query more specific, so fewer searches are needed and fewer posts need sentiment or insights.
- Pause a topic you don't need for a while (under ⋯). Nothing runs or is charged until you resume, and its posts stay.
- Delete one you've finished with. Its posts and runs are deleted too, and it can't be undone: download them first if you want them.
Running out of credits
A search sets aside its whole limit from your balance while it runs, and gives back what it didn't use. So your balance must cover the limit, not just what the search ends up costing:
- A preview whose limit is more than your balance doesn't run, and nothing is charged. Lower Spend, or Buy credits.
- A topic's run that your balance can't cover doesn't search; its run says Not enough credits to run it. and the topic tries again at its next run. After 5 failed runs in a row the topic shows Failing: add credits, then Resume it.
- Sentiment and insights that your balance can't cover are left off those posts, uncharged, with a note. The search itself still runs.
Other limits
| Limit | Value |
|---|---|
| Topics a workspace can have | 100 |
| How often a topic runs | Every 15 minutes to every week |
| A query's length | 8,192 characters, up to 500 terms |
| A description for Describe it | 2,000 characters, with up to 5 posts it should find and 5 it should leave out |
| Your own insights questions | 3 a topic, each up to 200 characters |
| Searches you choose for a platform | 10, each up to 200 characters |
| How long a topic keeps a post | A year |
| A download | The newest 5,000 posts |
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.
Troubleshooting
The messages Listening shows, why they appear, and what to do: query errors, previews that find nothing or too much, topics that are paused, capped or failing, and sentiment or insights that are missing.