Get audience statistics
get_audience_statsUse this when the founder asks how many signups they have, how a week or a launch is going, how many verified their email, where signups come from, or how well the launch page converts. Not for finding or listing people (use search_audience), for the top referrers (use get_leaderboard), or for the plan's billable contact count (use get_workspace).
It returns total audience, signups today and over a trailing window, how many verified their email (confirmed: they clicked the link we sent to verify their address; everyone who joins is subscribed either way), and the breakdown by subscription status, pipeline stage and first-touch source.
Every number comes from precomputed counters, so it costs a handful of indexed row reads no matter how large the audience is. To count, use this rather than paging through search_audience: that is capped at 50 rows per call and wrong as soon as there is a second page.
total counts live contacts and excludes test-mode and flagged-for-review rows, so it can differ from the billable count in get_workspace. referred counts signups that arrived through somebody's referral link.
views is how many times the launch page was viewed over the same window, and conversion is the percentage of those visits that became signups on that page (page_signups, the numerator: signups from an import, the API or an embed have no visit behind them and are not counted). It is null, with conversion_note, when there were no views or more signups than views.
The plan sets limits, the same ones the Analytics page has. days is capped at how far back the plan's analytics history reaches: a longer request is shortened, and signups.window_days is the window actually used. source is null unless the plan includes advanced analytics. total counts every saved contact, including any held past the plan's size; hidden_contacts is how many of those the founder cannot see or use until the plan holds them.
When the plan limits any of that, the answer is still returned, with a reason beside the missing part (source_unavailable_reason, window_limited_reason, hidden_contacts_reason) and one upgrade object: the lowest plan that clears all of them, with its link. Say plainly what is missing and why it matters for what the founder asked, and give them the link. Do not mention an upgrade when there is no upgrade object.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project": "<project>"
},
"name": "get_audience_stats"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | How many days of daily arrivals to include, counting back from today. 1-90, defaults to 7. | |
| project | Yes | The project handle, like `prj_…`. |