liveBook · Manning

User engagement

As explained in Automating API Delivery

An engagement metric measures the extent to which potential API consumers interact with API documentation and developer portal tools.

User engagement measures how potential API consumers interact with API documentation and developer-portal tools. It belongs to API product metrics, which function as action metrics and leading indicators for management’s focus metrics. section 11.1.3

Interpret engagement within the API consumer model:

  • Treat developers as the primary API users, even when their applications serve many end users. section 11.1.3
  • Use developer-portal analytics to obtain continuous feedback about the user experience. section 11.1.3
  • Attribute API calls from an integrated application and its API key to the developer user for product-metric analysis. section 11.1.3

How Automating API Delivery covers it

How deep it goes
Defines engagement as a metric category and situates it among six API product categories, without listing engagement measures or implementation steps.
Examples
Points to Google Analytics, Mixpanel, Amplitude, and Readme as developer-portal analytics examples, though they are discussed for discovery metrics.
What it assumes
Assumes an API product view that treats developers as primary users and distinguishes them from application end users.
What you can do after
Evaluate developer-portal experience through continuous feedback from web analytics tools.
How it connects
Connects engagement metrics with API product metrics, developer portals, web analytics, discovery metrics, and leading indicators.

Also explained in

Compare how 5 books explain user engagement →

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.