Requires the Reporting permission. Tools in this group are hidden from
tools/list and refused on call when your plan does not grant it.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. Preferanalytics_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
string
Restrict to campaigns in this status.
string
Restrict to leads carrying this tag.
object
Date window as { from, to } — epoch milliseconds or ISO 8601. Omit for the backend default.
analytics_campaign
Read-only Headline performance for one campaign: prospects found, invites sent and accepted, messages, InMails, emails sent/opened/clicked/bounced, and replies. OmitcampaignId 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
string
Campaign id, from
campaign_list or campaign_create.string
Sub-account owner id.
object
Date window as { from, to } — epoch milliseconds or ISO 8601. Omit for the backend default.
boolean
default:"false"
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. Usesequence_step_stats for a fast per-step breakdown — it answers the same question on a large campaign.
Parameters
string
required
Campaign id, from
campaign_list or campaign_create.object
Date window as { from, to } — epoch milliseconds or ISO 8601. Omit for the backend default.
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 shareddates 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
string
Narrow to one LinkedIn account.
string
Sub-account owner id. Omit to act on your own data.
object
Date window as { from, to } — epoch milliseconds or ISO 8601. Omit for the backend default.
string[]
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 useanalytics_reporting.
Parameters
integer (1–24)
default:"6"
How many months back to include.
string
Action type, e.g. “CONNECT”, “MESSAGE”, “EMAIL”.
string
Campaign id, from
campaign_list or campaign_create.string
LinkedIn account id, from
linkedin_account_list.