Track SDK adoption after release

Measure whether developers upgrade to a new customer-facing SDK version after launch and which accounts remain behind.

Published

difficulty intermediate · time to value 5 minutes
#analytics #deploys #sdk #releases #devtools #product

Start from this 

After the latest SDK release, show adoption by version, language, account, and API usage. Identify accounts still on old versions.

Why this matters

SDK launches do not create value until customers actually upgrade. Product and developer relations teams need to know whether a release is spreading or sitting unread in a changelog.

What you get

  • Adoption curve by SDK version and language
  • Accounts still using deprecated versions
  • API usage volume by version
  • Upgrade targets for CS or developer relations

Walk through it

You

Did customers adopt the SDK version we released last week?

Agent

I’ll find the latest release, then group SDK initialization and method calls by version.

GET /v1/projects/:project_id/deploys { project_id: "default", limit: 5 }
POST /v1/projects/:project_id/analytics/query {
  project_id: "default",
  hogql: "SELECT properties.sdk_version AS version, properties.language AS language, count(DISTINCT properties.account_id) AS accounts, count() AS events FROM events WHERE event IN ('sdk_initialized','sdk_method_called') AND timestamp > now() - INTERVAL 30 DAY GROUP BY version, language ORDER BY accounts DESC"
}

The output

The agent returns adoption by version and language, then calls out large customers still on old versions. It should recommend docs, outreach, or compatibility fixes depending on the pattern.

Setting it up

Emit SDK usage events from the customer’s application or API edge when requests include SDK metadata. Do not imply Agentry has an SDK; this recipe is about your product’s customer-facing SDKs.

Variations

  • “Show Python SDK adoption after the release.”
  • “Which enterprise accounts are still on deprecated versions?”
  • “Compare error rate by SDK version.”

Related recipes

ops 1 minute

Track which SDK versions your customers are on

Look at sdk_version on api_request events. What % are on latest vs N-1 vs older? Critical for the 'when can we deprecate?' conversation.

ops 3 minutes

Per-customer API call analytics

Group api_request events by customer_id over 30 days with daily breakdown. The view usage-based pricing needs but most teams cobble together from logs.

growth 5 minutes

Which doc page leads to the most API adoption?

Funnel from a docs page view to first api_request by the same distinct_id within 7 days. Per-doc-page breakdown — find the highest-leverage page in your docs.

Try this recipe in your own agent.

Ask your agent to adapt the starter prompt to your saved signal map and live events, then run it against your data.

Install agentry.sh/install.md for me
Agent will onboard itself and then your app
← all recipes