liveBook · Manning

Retention

As explained in Automating API Delivery

User retention is a measure of the proportion of users who continue to use a product during a specified later period.

User retention is the percentage of developers who return to use an API over time. It is a retention-stage API product metric: unlike a first call or a daily active-user count, it asks whether users come back after their initial use. For these metrics, calls from an application and its API key are attributed to the developer, not counted separately for each end user of the application. section 11.1.4 section 11.1.3

To create a daily retention report in Moesif:

  • Choose New > Users > Retention. section 11.1.4
  • Under Event Criteria, set both First Event and Returning Event to Event Type Is API Call. section 11.1.4
  • Save the view as Daily User Retention under ProductCatalogDashboard. section 11.1.4

Reading a zero-retention result

In the Product Catalog API example, day zero is the day a user's first request arrives. The chart falls to zero by day one because no users made repeat calls after that first day. Read this as an observation about the recorded calls, not as proof of why developers did not return. section 11.1.4

Figure 11.21 Setting the user retention chart criteria
figure

The report-criteria figure shows the two API Call events used to measure a return. section 11.1.4

How Automating API Delivery covers it

How deep it goes
Defines the percentage and walks through daily report setup and chart interpretation, without specifying a manual calculation.
Examples
Uses a Product Catalog API retention chart that reaches zero on day one after no repeat calls.
What it assumes
Assumes API calls can be attributed to developer users; supplies the report criteria needed to identify first and returning events.
What you can do after
Apply it via Moesif by configuring a daily API-call retention report and interpreting its return-rate chart.
How it connects
Connects retention to the developer journey, daily active users, time to first transaction, and conversion rate.

Also explained in

Compare how 7 books explain retention →

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.