> ## Documentation Index > Fetch the complete documentation index at: https://docs.linkedcamp.com/llms.txt > Use this file to discover all available pages before exploring further. # Analytics > Performance, at campaign, sending-account and whole-account level. Requires the **Reporting** permission. Tools in this group are hidden from `tools/list` and refused on call when your plan does not grant it. | Tool | Kind | | - | - | | [`analytics_account`](#analytics_account) | Read-only | | [`analytics_campaign`](#analytics_campaign) | Read-only | | [`analytics_campaign_funnel`](#analytics_campaign_funnel) | Read-only | | [`analytics_reporting`](#analytics_reporting) | Read-only | | [`analytics_trend`](#analytics_trend) | Read-only | ## analytics\_account Read-only Roll-up across every campaign in your account: totals by action type, reply sentiment breakdown, and tag distribution. SLOW — it aggregates every campaign and every lead. On a large account it may not complete at all. Prefer `analytics_reporting` for a time series or `analytics_campaign` for one campaign; reach for this only when a true account-wide roll-up is needed, and narrow it with `range`. ### Parameters Restrict to campaigns in this status. Restrict to leads carrying this tag. Date window as \{ from, to } — epoch milliseconds or ISO 8601. Omit for the backend default. Start of the window. End of the window. Alias for `from`. Alias for `to`. ## analytics\_campaign Read-only Headline performance for one campaign: prospects found, invites sent and accepted, messages, InMails, emails sent/opened/clicked/bounced, and replies. Omit `campaignId` for a roll-up across your whole account. Start here for "how is this campaign doing" — it is the cheap one. Totals only: for a day-by-day series use `analytics_reporting`, for where people drop out use `sequence_step_stats`, and for a spreadsheet use `campaign_export_stats`. ### Parameters Campaign id, from `campaign_list` or `campaign_create`. Sub-account owner id. Date window as \{ from, to } — epoch milliseconds or ISO 8601. Omit for the backend default. Start of the window. End of the window. Alias for `from`. Alias for `to`. Also return the day-by-day series for charting. ## analytics\_campaign\_funnel Read-only Stage-by-stage conversion for one campaign over a window — the numbers behind "where are we losing people". SLOW on a campaign with many leads: it walks every activity row and may not complete at all. Use `sequence_step_stats` for a fast per-step breakdown — it answers the same question on a large campaign. ### Parameters Campaign id, from `campaign_list` or `campaign_create`. Date window as \{ from, to } — epoch milliseconds or ISO 8601. Omit for the backend default. Start of the window. End of the window. Alias for `from`. Alias for `to`. ## analytics\_reporting Read-only Parallel daily series — engagements, invites, messages, InMails, follows, event invites, opportunities, emails sent/opened/clicked/bounced, accepted, replied — aligned to a shared `dates` array. The right tool for "how did we trend over the last 30 days". A series per day, not a total: for one campaign's totals use `analytics_campaign`, and for months rather than days use `analytics_trend`. Note it scopes by LinkedIn account, not by campaign. ### Parameters Narrow to one LinkedIn account. Sub-account owner id. Omit to act on your own data. Date window as \{ from, to } — epoch milliseconds or ISO 8601. Omit for the backend default. Start of the window. End of the window. Alias for `from`. Alias for `to`. Restrict to specific series names, e.g. \["invites","accepted","replied"]. ## analytics\_trend Read-only Month-over-month totals for one action type, optionally scoped to a campaign or LinkedIn account. One action type per call and one point per month — the long view. For daily granularity across all action types at once use `analytics_reporting`. ### Parameters How many months back to include. Action type, e.g. "CONNECT", "MESSAGE", "EMAIL". Campaign id, from `campaign_list` or `campaign_create`. LinkedIn account id, from `linkedin_account_list`. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.