liveBook · Manning

Acquisition metric

As explained in Automating API Delivery

An acquisition metric measures developers' initial sign-up or adoption of an API.

An acquisition metric measures developers’ initial sign-up or adoption of an API. It belongs to the API product metric categories used to track action metrics and leading indicators for management’s focus metrics. section 11.1.3

Interpret the developer as the primary API user: API calls from an integrated application and its associated API key count as coming from that developer, regardless of the application’s end-user count. Developer account sign-ups by referral channel are identified as a related measurement example under discovery metrics. section 11.1.3

Figure 11.5 Extending the developer journey map with API product metric categories
figure

Use the developer journey map to place acquisition alongside discovery, engagement, activation, retention, and experience metrics. section 11.1.3

How Automating API Delivery covers it

How deep it goes
Defines the category and its measurement scope but does not detail acquisition formulas, instrumentation, or analysis procedures.
Examples
Uses developer account sign-ups by referral channel as a related example of measuring developers’ movement toward API adoption.
What it assumes
Assumes familiarity with API product metrics while clarifying the distinction between developer users and application end users.
What you can do after
Evaluate developer adoption as a leading indicator contributing to management’s focus metrics.
How it connects
Connects acquisition with discovery, engagement, activation, retention, experience, and API product metrics.

Also explained in

Compare how 2 books explain acquisition metric →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.