Activity and analytics

Home is your at-a-glance landing page, the activity feed is the running log of everything happening, and Analytics holds the detailed performance numbers you can filter and export.

What it is

Handshake gives you three views of how your outreach is doing, from the quickest glance to the deepest detail:

Home is the page you land on. It shows what needs attention, how the account is doing, and where to go next, over a fixed last-30-days window.
The Activity Center is the full, searchable log of every event - each message sent, reply received, connection accepted, meeting booked, and any warnings.
Analytics holds the performance charts and the spreadsheet-style table where you break performance down by campaign, audience, account, or client, and export it to CSV or Excel. It is the one place that owns time ranges. The new portal calls this page Analytics and opens it on a chart Overview. The older Client, Partner and Admin portals call the same page Reports and open it straight on the table.

They all draw from the same underlying record of what happened, so the numbers line up.

Why it exists

Without these, you would be guessing. You would have no single place to see whether outreach is landing, which campaigns are working, or whether an account has gone quiet. Home answers "what needs me right now?", the activity feed answers "what just happened?", and Analytics answers "show me the numbers, broken down, so I can prove it and export it."

Who can see it

Everyone sees a version, shaped to their level:

Partners see performance across all their clients, plus counts of active clients, seats and campaigns.
Clients see their own outreach and meetings.
Seat users see their own sending and meetings.
Admins see everything, and reports show extra money columns (costs, revenue, profit) that nobody else sees.

What you see is always limited to your current scope. The breadcrumb bar at the top lets you narrow down (for example, a partner viewing just one client, or one campaign).

How it works

Home

Home is your landing page, and it is the same page in every portal. It answers three questions, top to bottom: what is broken, how is the account doing, and where do I go next. There is no time-range selector - Home is fixed at the last 30 days, and Analytics (called Reports in the older portals) owns ranges.

Top to bottom, Home shows:

A greeting line with the account name and today's date.
Needs attention - one row per real problem, each with a single fix to click: a disconnected seat, a paused seat or campaign, an audience about to run out of contacts, replies waiting for your approval, and unpaid invoices. When nothing needs you, the whole section is absent rather than empty.
Account health - four cards that never move: Campaigns, Audiences, Seats and Signals. Each shows one number, a status chip and a one-line reason. A card with no data yet says what will make it appear instead of showing a zero.
Buying signals - the people who have shown a buying signal this week, with the evidence, how certain the signal is, and a suggested angle to open on.
Performance - four cards for the last 30 days: Replies, Reply rate, Acceptance rate and Meetings booked, each with a trend line. Before your first sends they show a hyphen and the sentence that names what will fill them in.
A right-hand column with quick links (badged with your waiting approvals and CRM tasks due), your next meetings, and your team seats with each seat's sending status and stored health score.

New accounts see a setup checklist at the top instead of the numbers, with the real steps, a rough minute estimate each, and a link straight to the next one. Each module switches from its waiting state to live on its OWN data, so the page fills in as you go.

Workspace users also see a Financial Summary and a Live Activity panel in the right column - a compact, real-time feed of recent events. Those two are workspace-only.

Setup cards on the dashboard are gone: connecting LinkedIn, email and a calendar is now a step on the checklist and, for an existing account, an attention row. See Seats and account safety.

The activity feed (Activity Center)

The Activity Center is the complete, scrollable log of everything that has happened. Open it from the sidebar or from the Live Activity panel on Home.

It has the same time-range selector (1 day to 1 year, default 30 days) and a Refresh button. The breadcrumb lets you filter by client, account or campaign. The feed groups events into categories you can show, hide and search:

Messages - messages sent and replies received, with a short preview of the text.
Connections - connection requests sent, accepted, withdrawn or failed.
Conversions - a contact became a lead, and meeting events (requested, confirmed, held).
Clients - clients added, activated, paused or terminated.
Campaigns - campaigns and audiences created, started, imported, approved or completed.
Warnings - things to notice but not panic over, such as a LinkedIn or email account disconnecting, a rate limit being reached, or a campaign that "can't send yet".
Errors - genuine failures, such as a sync or connection error.

Each event shows an icon, a plain-language title (often naming the contact, campaign or person), a timestamp like "5 minutes ago", and where relevant a View link that jumps to the contact in the Outreach Hub. Use the Search box to find events by contact name, campaign, message text and similar, and Load more to page back through history.

You can rearrange the Activity Center to suit you - toggle Edit to show, hide, resize and drag the widgets, and Reset Defaults to put them back.

Analytics, called Reports in the older portals

Analytics is the detailed, exportable view. Open Analytics from the sidebar of the new portal. The address is /reports in every portal, so old links and bookmarks keep working.

The page comes in two shapes:

The new portal shows it under the heading "Analytics", with three tabs: Overview, Report and Campaign Comparison.
The older Client, Partner and Admin portals show it exactly as they always have, under the heading "Reports", with two tabs: Report and Campaign Comparison. There is no Overview tab there. The Partner sidebar lists it as Reports; the Client and Admin sidebars do not list it.

The tabs:

Overview (new portal only) - the performance charts the old dashboard carried, with their own time range (1 day to 1 year, default 30 days). Organization users also get the meetings row here: Meetings Booked, Attended, Cancelled and No Shows, each with its rate.
Report - the metrics table.
Campaign Comparison - overlay trend lines for a handful of campaigns.

The Overview charts, in the new portal, cover Connection Requests, Connections Accepted, Acceptance Rate, Messages Sent, Replies, Reply Rate, Conversions, Conversion Rate and Reply Conversion Rate. The Acceptance Rate trend line is event-based; see the Reports definition below for the people-based table rate.

Choosing what each row is. Use the Group by control to pick what a row represents: Campaign, Audience, Account or Client. Audience is the most granular.

Choosing the period. Pick a recent month with the preset buttons (for example "Jun 2026"), or type an exact Start date and End date. The default is the start of the current month through today.

The columns. Each column has a tooltip explaining it. The key ones (rates are shown to two decimals, e.g. "16.89%"):

Column	What it means
Name	The campaign, audience, account or client this row is for.
Total Contacts	All real contacts in this view, excluding duplicates and invalid ones.
Left to Connect	Contacts not yet connected and not muted - still available to reach.
Muted	Contacts you have muted, so no more messages are sent to them.
Connections Sent / Accepted	Connection requests sent, and how many were accepted, in the period.
Accept Rate	Share of unique people sent a request in the period who accepted: unique people accepted divided by unique people requested.
Messages Sent	All messages in the period; LinkedIn Messages and Email Messages break this down.
Replies	Replies received; LinkedIn Replies and Email Replies break this down.
Reply Rate	Share of people you messaged who replied (per person, not per message).
Conversions	Contacts who became a lead in the period.
Conv. Rate	Conversions divided by accepted connections.
Projected Conv. Rate	Estimated final conversion rate once recent contacts have had time to convert. Shows "-" when the period is too recent to project.
Reply-to-Conv. Rate	Conversions divided by replies.
Avg Time to Convert	Average days from connecting to converting, once there is enough data.
Total Connections	All accepted connections since launch, ignoring the date range.
Warm	Contacts showing early interest.
Hot	Your most engaged, highest-intent contacts.

Some columns are hidden by default; use the gear icon in the table header to show or hide columns. You can also drag column headers to reorder them and drag a column edge to resize. Click a header to sort. The totals row at the bottom also shows the change versus the previous equal-length period.

Admin-only money columns. Admins additionally see Total Costs, Revenue Billed and Gross Profit. These are never shown to partners, clients or account users.

Conversions take time. Because a conversion can lag the first contact by a couple of weeks, the report quietly flags very recent periods as "still settling" and dims the conversion columns, so you do not read too much into numbers that have not matured yet.

Exporting

Above the table are export buttons. CSV downloads instantly; XLSX produces an Excel spreadsheet. (A PDF button is shown but marked coming soon.) The export includes every row (not just the page on screen) and only the columns you currently have visible, and it matches the on-screen numbers exactly, including the Total Contacts / Left to Connect / Muted / Warm / Hot pipeline counts. The file is named for the date range, e.g. report-2026-06-01-2026-06-26.csv.

Understanding reply rate

Reply rate is the number partners ask about most, so here is exactly what it means.

Reply rate is people-based, not message-based. It is the share of the people you messaged who replied:

people who replied and had received an outreach message ÷ people who received an outreach message

Two things follow from this:

It counts people, not messages. If you send one person three follow-ups and they reply twice, that is still one person messaged and one person who replied - not three sends and two replies. This is why reply rate cannot be reconstructed by dividing the "Replies" column by the "Messages Sent" column; those are raw message counts, and reply rate is a headcount.
A reply only counts if that person actually received an outreach message. Someone who replied to your connection-request note but never got a real follow-up message is not part of the messaged group, so they do not move the reply rate. This keeps the rate honest.

For a single date range, Handshake works out reply rate by counting distinct people across the whole range (so a person messaged on two different days is still one person). The little trend line under the reply-rate card is a day-by-day approximation for showing direction, so it can read slightly differently from the headline figure - the headline is the one to trust.

The same definition is used everywhere - the Home card, the Analytics table, and exports - so the figure is consistent wherever you see it.

Understanding Accept Rate in Reports

Reports Accept Rate is people-based, just like Reply Rate. It counts distinct people who were sent a connection request in the selected period, then asks how many of those people accepted. If 12 of 25 people accepted, the rate is 48%.

This is intentionally different from the connection volume columns. Connections Sent, Connections Accepted, and Withdrawn count events. One person can have more than one request event, so dividing accepted events by sent events does not recreate the Reports rate. Use the rate to understand how people responded, and the volume columns to understand how much activity occurred.

The Overview acceptance-rate sparkline is event-based because it is a daily trend display. For ranges of 42 days or fewer, that event-based sparkline is exact because requests are withdrawn after 21 days and a further 21-day cooldown prevents another request. For longer ranges, rely on the displayed Reports definition rather than trying to derive it from the event volumes.

Limits and what to watch out for

The time range changes everything. Almost every Analytics number is for the selected period. If a count looks low, check the range first. "Total Connections" in reports is the deliberate exception - it ignores the date range and counts since launch.
Reply rate is a headcount, not Replies ÷ Messages Sent. See above. Do not expect those two raw columns to divide into the reply rate.
Recent conversions are not final. Conversions can take a couple of weeks to show up, so treat conversion numbers for the last week or two as provisional - the report flags this for you and may show "Projected Conv. Rate" instead.
Reports Accept Rate is a people count. It is unique people accepted divided by unique people requested in the selected period. Connections Sent, Connections Accepted, and Withdrawn are separate event-volume columns, so do not divide them to recreate the rate.
What you see is scoped. You only ever see data for your current breadcrumb scope. If a client or campaign seems to be missing, check the breadcrumb at the top - you may be filtered to a narrower view.
Analytics is the new portal's name for Reports, not a new address. The new portal reads "Analytics" and adds the Overview tab. The older Client, Partner and Admin portals keep the "Reports" name and their two original tabs. The URL is /reports in all of them, so existing links keep working.
Home has no time range. It is always the last 30 days. Change the period in Analytics.
Money columns are admin-only. Costs, revenue and profit never appear for partners, clients or seat users.
Warnings vs errors. A "Warning" (for example a disconnected LinkedIn account or a rate-limit notice) is worth checking but is not a failure. An "Error" is a genuine problem. A disconnected seat is the most common reason outreach quietly stops - reconnect it from Seats and account safety.