Posted on

Mastering API Analytics for API Programs: Cohort Retention Analysis

There are few metrics more critical than retention for a platform business. If you’re acquiring customers for $25, but they stop using your API after a month, then you have a leaky boat. Don’t spend more money on developer acquisition until retention is fixed. This requires accurate measurement of API retention.

If you came from a web or mobile product background, you may already be familiar with mobile retention to measure how many acquired users keep using a mobile app. Growing a B2B platform requires tracking similar KPIs to measure the success of your acquisition and product strategies. This article will dig into the best practices for tracking and increasing API retention.

Posted on

How Can a DevRel Program Best Measure the Success of an API Platform?

Each developer relations program has a different opinion on what should be north star metrics to measure the success of their platform. Some metrics are valid while others can be what are called vanity metrics. This post discusses which metrics you should or should not be tracking.

What to Measure

The goal of developer relations is to ensure third-party developers are able to leverage your platform to create something of value. Value can be subjective but some examples include shipping a new integration or plugin that increases the usability of your products or integrating your APIs and SDKs into their web or mobile apps to deliver a better experience for their customers.

Posted on

13 API Metrics That Every Platform Team Should Be Tracking

A list of the most important API metrics every API product manager and engineer should know, especially when you are looking into API analytics and reporting.

API analytics

Identifying Key API Metrics

Each team needs to track different  KPIs  when it comes to APIs. The API metrics important to infrastructure teams will be different than what API metrics are important to API product or API platform teams. Metrics can also be dependent on where the API is in the product lifecycle.

An API recently launched will focus more on improving design and usage while sacrificing reliability and backward compatibility. A team that maintains an API that’s been widely adopted by enterprise teams may focus more on driving additional feature adoption per account and give precedence to reliability and backward compatibility over design.

You may also like: Analyzing API Call Performance From Different Global Locations Based on cURL Metrics