Book Image

API Analytics for Product Managers

By : Deepa Goyal
Book Image

API Analytics for Product Managers

By: Deepa Goyal

Overview of this book

APIs are crucial in the modern market as they allow faster innovation. But have you ever considered your APIs as products for revenue generation? API Analytics for Product Managers takes you through the benefits of efficient researching, strategizing, marketing, and continuously measuring the effectiveness of your APIs to help grow both B2B and B2C SaaS companies. Once you've been introduced to the concept of an API as a product, this fast-paced guide will show you how to establish metrics for activation, retention, engagement, and usage of your API products, as well as metrics to measure the reach and effectiveness of documentation—an often-overlooked aspect of development. Of course, it's not all about the product—as any good product manager knows; you need to understand your customers’ needs, expectations, and satisfaction too. Once you've gathered your data, you’ll need to be able to derive actionable insights from it. This is where the book covers the advanced concepts of leading and lagging metrics, removing bias from the metric-setting process, and bringing metrics together to establish long- and short-term goals. By the end of this book, you'll be perfectly placed to apply product management methodologies to the building and scaling of revenue-generating APIs.
Table of Contents (24 chapters)
21
The API Analytics Cheat Sheet

Setting customer expectations of support and SLAs

In the previous section, we look at how large volumes of customer feedback are handled using tools to operate a support model. It is also vital that we communicate our support offering to customers so that they have a clear understanding of what level of support they can expect. This is where our concepts of API maturity from Chapter 3 are instrumental. For experimental APIs, we can control the exposure to a limited set of customers because it is natural that the product and documentation are not thorough at this point and there would be more support needed for customers to use such APIs.

It is standard practice for API product documentation to have a page dedicated to maturity. This maps each maturity level to the level of support provided. This allows customers to have an understanding of what to expect when they reach out to support for help. This mapping also involves expectations of how frequently APIs may change or whether...