Introduction to Deep Dive into Key Metrics for API Products

The goal of any product is to drive value for its customers. If customers can discover our product, easily understand the utility it provides, and start using it effectively in a way that they find valuable, our product has successfully achieved its goal.

We previously learned about the roles and responsibilities of an API product manager and how to build, grow, maintain, and support APIs as products, and about the developer journey and how the consumers of API products discover, evaluate, integrate, test, and measure the APIs they consume. Now that we have a deep understanding of the customer, we can start to think about metrics that can measure various aspects of a product across producers and consumers. We'll learn to manage APIs methodically and learn about the levers we have to improve these metrics so that our product can be successful.

Translating touchpoints to measurable metrics

Using steps of the customer journey to establish metrics to measure a product’s performance is a useful approach because it allows us to understand how customers interact with our product and identify areas for improvement. By identifying and tracking metrics that correspond to each stage of the customer journey, we can gain a deeper understanding of how customers interact with our product and identify areas for improvement. This can help to improve the overall customer experience and drive growth for the business.

Earlier, we broke down each interaction the customer has with a product into individual touchpoints; now we'll learn to measure each of these steps and identify patterns in user behaviors that work in favor of or against our product goals. By following the developer journey, we can identify the different steps customers take to successfully use our product. In this process, we'll also be able to identify where our customers struggle. In this section, we'll learn to translate the steps of the developer journey into a measurable conversion funnel and the methods to identify signals, such as activation, engagement, retention, and scale.

Across the user journey, users go through discovering a product, learning and adopting the product, and then either scaling or declining their usage. All of the components of the API experience drive the discovery and adoption of API products.

A holistic approach to analytics

There are three core dimensions to API product analytics that measure a product across all aspects of the customer journey—infrastructure, product, and business—as shown in the following illustration.

Being data-driven in API management is important because it allows companies to make informed decisions about their API strategy, operations, and performance. A data-driven approach enables a company to understand how its API is being used, how it’s performing, and how it’s impacting a business.

Here are some examples of why a data-driven approach is important in API management.

Infrastructure: API infrastructure metrics such as uptime, response time, and error rates can be collected and analyzed to identify and troubleshoot issues, and to ensure that an API is performing well and meeting service-level agreements.

Product experience: Metrics such as user engagement, user satisfaction, and conversion rates can be collected and analyzed to understand how well an API is meeting customer needs and how it is impacting a business.

Business: Business-related metrics such as revenue, customer acquisition, and retention can be collected and analyzed to understand how an API is impacting the overall performance of a business.

By being data-driven, companies can make informed decisions about their API strategy, operations, and performance. For example, by analyzing the usage data, companies can understand which features are being used most and which are not, and make decisions on which features to invest more in. Additionally, by analyzing performance data, companies can identify bottlenecks and make decisions on scaling the infrastructure accordingly.

Overall, being data-driven in API management allows companies to make informed decisions about their API strategy, operations, and performance by providing a clear picture of how an API is being used, how it’s performing, and how it’s impacting a business.

We've learned about how APIs are built, the growth goals that drive the development of API products, how API products are discovered, evaluated, and integrated by developers on the customer side, and how we can better understand the touchpoints to help API customers be successful. In this chapter, we'll learn about how to establish specific metrics that tie together the goals of the API producers and API consumers so that we can measure whether those goals are being met.

We'll learn about the language and how to calculate and understand the most important metrics in all areas of APIs in these chapters:

• Infrastructure Metrics

• API Product Metrics

• Business Metrics