Search People Metrics

Surface people-level metrics from Sales Navigator results to rank leads and tune sequences.

Edges is not related to LinkedIn and is not an official LinkedIn product.

API Endpoint

POST/v1/actions/salesnavigator-search-people-metrics/run/live

Parameters

Input Parameters

Configuration Parameters

Integration Parameters

Guide

What Search People Metrics does

Search People Metrics surfaces people-level metrics from Sales Navigator search results so you can rank leads, tune sequences, and size audiences before you commit to extraction. You get the counts and distributions behind a Sales Navigator people search — total matches, breakdown by title, seniority, geography — returned as structured JSON. It targets RevOps and growth engineers who use Sales Navigator as a programmatic data surface.

The action runs on the Sales Navigator level and uses your authenticated Sales Navigator session on Edges.

How it works

You point Search People Metrics at a Sales Navigator people search URL or a saved lead list, and Edges pulls the metric payload behind that view. The action reads the totals and facet breakdowns that Sales Navigator renders — by function, seniority, geography, years at company — and returns them as a single structured object.

Every request is signed with your Sales Navigator session, paced within activity guidance, and returns typed errors if the search has expired or the list is no longer accessible. The operation is synchronous for a single search and supports async execution for batches.

When to use Search People Metrics

Reach for Search People Metrics when you need the numbers behind a Sales Navigator lead search before committing to a full extraction. Metric pulls are cheap; lead extractions are expensive — so use this action to size, rank, or monitor before you spend the budget.

It plugs into the LinkedIn signals and intent API use case. Teams wire it into ABM dashboards and triggered workflows where a threshold crossing (e.g., "more than 50 new VP Engineering matches this week") kicks off extraction and outreach.

Use cases

  • Sequence tuning. Snapshot the distribution of titles and seniorities in a saved list weekly to tune messaging variants against the real audience.
  • List-growth alerting. When newSinceLastRun crosses a threshold, fire a Slack alert and trigger Search Sales Navigator People to pull the new leads.
  • ICP audit. Validate that a saved Sales Navigator list actually resolves to your ICP distribution before handing it to SDRs.
  • Budget planning. Before launching a campaign, size the addressable audience across filter variants and pick the one that fits your capacity.
  • Board reporting. Track ICP coverage trend lines quarter over quarter from metric snapshots alone.

Best practices

  • Run metrics before extraction. The cheapest way to avoid wasted extraction runs is to check the count and distribution first.
  • Snapshot on a schedule. A single metric point is weak signal; deltas across daily or weekly snapshots are what drive action.
  • Cache by URL. Within a short window, the same search returns the same numbers; cache aggressively.
  • Stay inside your seat's pacing budget. Edges paces requests, but polling metrics on hundreds of lists should be spread across the day.

Common questions

How many searches can I check per run?

One per call. Parallelize at the workflow level when you monitor many saved lists, and let Edges pace Sales Navigator safely.

Does Search People Metrics use my Sales Navigator account or a shared pool?

Your Sales Navigator account. Every metric pull runs through your connected session, so the numbers match what your seat would see in the Sales Navigator UI.

Can I chain Search People Metrics with other Edges actions?

Yes. When the count and distribution look right, chain into Search Sales Navigator People or Extract Sales Navigator Leads List to pull the actual people.

Get started

Run Search People Metrics from the Edges library, schedule it on a cron to drive alerting, or call it directly from the Edges API to feed dashboards. Browse the full Actions library to see the Sales Navigator actions that pair with it.

Code Examples

bash
curl -X POST "https://api.edges.run/v1/actions/salesnavigator-search-people-metrics/run/live" \
  -H "X-API-KEY: <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
  "identity_ids": [
    "your-identity-uuid"
  ],
  "identity_mode": "direct",
  "input": {
    "custom_data": "example_value",
    "sales_navigator_company_id": "example_value",
    "sales_navigator_profile_search_url": "https://www.linkedin.com/in/example-profile"
  },
  "parameters": {
    "geo": "example_value",
    "geography_excluded": [
      "item1",
      "item2"
    ],
    "function": "example_value",
    "function_excluded": [
      "item1",
      "item2"
    ],
    "seniority": [
      "item1",
      "item2"
    ],
    "seniority_level_excluded": [
      "item1",
      "item2"
    ],
    "employees_title": "example_value",
    "current_job_title_excluded": [
      "item1",
      "item2"
    ],
    "exclude_saved_leads": true,
    "exclude_crm_contacts": true,
    "exclude_viewed_leads": true,
    "keywords": "example_value"
  }
}'

Output Example

{
  "sales_navigator_company_url": "https://www.linkedin.com/in/example-profile",
  "company_name": "Example Name",
  "sales_navigator_company_id": 42,
  "linkedin_company_url": "https://www.linkedin.com/in/example-profile",
  "total_leads": 42,
  "new_leads": "example_value",
  "leads_posted_recently": "example_value",
  "leads_mentioned_in_news": "example_value",
  "leads_with_common_experience": "example_value",
  "leads_following_your_company": "example_value",
  "leads_past_colleague": "example_value",
  "leads_teamlink_your_executives": "example_value",
  "leads_viewed_profile_recently": "example_value"
}

Explore More Actions

Discover other powerful LinkedIn automation actions in our library.