Limits and billing
Listening runs on the same platform as the rest of Lantfly: each read of a source is a scraper run, billed to the account that owns the project like any other run. Your plan sets how many projects and sources you can have.
What counts toward usage
| Activity | Runs started |
|---|---|
| A scheduled collection | One run per active source |
| Collect now (project) | One run per active source, plus the keyword sources it adds |
| Collect this source now | One run |
| Retries of blocked or failed collections | One run per retry, up to 3 |
| The first collection of a new source | One run, reading up to 3 times its posts per run |
| Crawl historical data | The first run of each source reads further back, so it is bigger |
| Comments (when turned on) | Extra runs for the comments of the top posts |
| Add posts by link | One run per platform and 50 links |
| Track creator | Adds a profile source, collected on every run |
Runs appear in Runs in the Console like any run, and usage is taken from your plan's included usage, then credit, then overage. See Billing and Usage.
Reading the feed, analytics, exports, alerts, reports and walls do not start runs.
- Use a longer Collect every interval. Every 6 hours (the default) costs a quarter of every 90 minutes.
- Lower Posts / run on noisy sources.
- Turn comments on only for the sources that need them.
- Turn off sources you no longer need instead of deleting them, so Collect now does not add them back.
- Pause or stop projects you are not using.
Plan limits
| Plan | Listening projects | Sources per project |
|---|---|---|
| Free | 1 | 5 |
| Starter | 5 | 20 |
| Pro | 10 | 30 |
| Scale | 20 | 50 |
| Business | 100 | 100 |
| Enterprise | By contract | By contract |
Over a limit, creating a project or adding a source answers 422. Collect now and Track creator stop adding
sources at the limit; existing sources keep collecting. Prices and included usage are on the
pricing page and in Billing.
Historical crawls go back at most 365 days, or less if your plan sets a lower limit. Collection run datasets are kept for your plan's storage retention; mentions stay in the project until you delete it.
Other limits
| What | Limit |
|---|---|
| Collection interval | At least 15 minutes (default 6 hours) |
| Posts or reviews per run | 1–500 (default 30) |
| Comments per post | 1–500 (default 50) |
| Contextual and context keywords | 50 each |
| Languages per project | 20 |
| Brands for share of voice | 10 |
| Attributes per project | 50 |
| Owned accounts per project | 50 |
| Alert rules per project | 20 |
| Report schedules per project | 5, with 10 recipients and 10 CC each |
| Uploaded reports per project | 200 (PDF up to 20 MB, 30 previews of up to 2 MB) |
| Posts added by link | 200 per request |
| Bulk actions | 200 items per request |
| Mention, lead, influencer and campaign exports | 10,000 rows |
| Creator directory export | 20,000 rows |
| Creator lists | 100 per account, 2,000 creators each |
| Compare | 2–8 projects |
| Industry overview | The 200 newest projects of the industry |
| Dashboard period | Up to one year |
| Metric history (snapshots) | 180 days |