All Collections
API & Integrations
API
Department Headcount Traction Metrics
Department Headcount Traction Metrics

Access traction metrics for headcount by department

Miles avatar
Written by Miles
Updated over a week ago

How do I access headcount by department traction metrics?

Traction metrics by department are currently available for ~90k companies via the API.

An example GraphQL response is available at the bottom of this page.

Note: Corrected Headcount does not impact Department Headcount because they are calculated independently.

How can I see a person’s department?

All person responses now have departments classified (e.g. a department field derived from their job title), and all company responses have a headcount_{department} key that lives within traction_metrics.

This information can be used to view growth by department via headcount_{department}.metrics. Essentially, each traction_metric has a metrics field that exposes time-series data.

For users familiar with our snapshots, this is the same data in an easier-to-access location. No changes have been made to how snapshots are populated.

Why do only some companies get this metric?

A company will receive traction metrics by department if it > 8 people and we have thorough coverage (details below) of the people who work at the company.

  • If current headcount is 0 or null or less than 8, the company is too small and we will not add traction metrics by department.

  • If current headcount is between 8 and 30, only include traction metrics if our overall average person record coverage percent is at least 75%

  • If current headcount is between 31 and 100, only include traction metrics if our overall average person record coverage percent is at least 60%

  • If current headcount is between 101 and 200, only include traction metrics if our overall average person record coverage percent is at least 50%

  • If current headcount is above 200, only include traction metrics if our overall average person record coverage percent is at least 40%

List of Supported Departments

  • Advisor

  • Legal

  • Support

  • Customer Success

  • Product

  • People

  • Data

  • Operations

  • Design

  • Finance

  • Marketing

  • Sales

  • Engineering

  • Other

Example GraphQL Snippet

query GetCompanyTractionMetricsByDept($getCompanyById: Int!) {
getCompanyById(id: $getCompanyById) {
entityUrn
tractionMetrics {
headcountAdvisor {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountCustomerSuccess {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountData {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountDesign {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountEngineering {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountFinance {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountLegal {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountMarketing {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountOperations {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountOther {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountPeople {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountProduct {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountSales {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
headcountSupport {
ago14d {
change
percentChange
value
}
ago180d {
change
percentChange
value
}
ago30d {
change
percentChange
value
}
ago365d {
change
percentChange
value
}
ago90d {
change
percentChange
value
}
}
}
}
}

Did this answer your question?