How do I choose metrics for developer acquisition?

To choose metrics for developer acquisition, start by defining what “good acquisition” means for your product, then pick metrics that measure the funnel from awareness → signup → activation → retention → advocacy.

1) Start with the outcome you want

Ask:

• Do you want more signups?
• More activated developers who actually use the product?
• More qualified teams/accounts?
• More community contributors or API users?

For developer products, raw traffic or signups alone is usually misleading. The best acquisition metrics tie to real developer adoption.

2) Use a funnel, not one metric

A practical developer acquisition funnel:

1. Reach / Awareness

   • Impressions
   • Organic search traffic
   • Documentation visits
   • GitHub stars / community mentions

2. Interest / Intent

   • CTR from content, docs, or ads
   • Demo requests
   • Newsletter signups
   • “Try it now” clicks

3. Signup / Conversion

   • Visitor → signup conversion rate
   • Cost per signup
   • Trial starts
   • API key creations

4. Activation

   • % who complete first meaningful action
   • Time to first API call / first successful build
   • Docs-to-code conversion
   • SDK install → first successful request

5. Retention / Expansion

   • Weekly/monthly active developers
   • Retained accounts after 7/30/90 days
   • API calls per active account
   • Projects created per account

6. Advocacy

   • Referrals
   • GitHub issues/PRs
   • Community participation
   • Content shares / word of mouth

3) Choose a North Star metric

Pick one metric that reflects successful developer acquisition and early value realization. Examples:

• Activated developers per week
• New accounts that make a successful first API call
• New teams that reach a key usage threshold
• Qualified activated signups

A good North Star should be:

• tied to product value,
• hard to game,
• measurable consistently,
• leading indicator of retention/revenue.

4) Separate vanity metrics from decision metrics

Useful, but not enough alone:

• Page views
• Followers
• GitHub stars
• Raw signups

Better decision metrics:

• Signup-to-activation rate
• Cost per activated developer
• Activation rate by channel
• Retention by acquisition source
• Payback period or LTV:CAC for developer cohorts

5) Segment by acquisition channel

Developer acquisition quality varies a lot by channel. Measure each source separately:

• Organic search
• Docs
• GitHub
• Community/forums
• Product-led referrals
• Paid search/social
• Events / conferences
• Partnerships

For each channel, track:

• traffic,
• conversion to signup,
• activation,
• retention,
• revenue or expansion.

Often the “best” channel is the one with the highest activated and retained users, not the most signups.

6) Pick metrics based on your motion

Different developer motions need different metrics:

Self-serve API/SaaS

• Visitor → signup rate
• Signup → first API call
• Time to first success
• Activated account rate
• 30-day retention

Open source / community-led

• Qualified contributors
• Stars are secondary
• Contributor activation
• Repeat contributions
• Community-driven signups

Enterprise devtools

• Developer engagement inside target accounts
• Number of active users per account
• Account activation
• Pipeline influenced by dev adoption
• Expansion within accounts

7) Build a metric stack

A simple stack works best:

• Leading metric: Activated developer signups
• Quality metric: 30-day retained developers
• Efficiency metric: Cost per activated developer
• Growth metric: Net new activated developers per week

This helps you avoid optimizing for the wrong thing.

8) A good metric checklist

Before adopting a metric, make sure it is:

• Actionable — can you change it?
• Clear — everyone defines it the same way?
• Sensitive — does it move when acquisition changes?
• Aligned — does it reflect real product value?
• Segmentable — can you break it down by channel/cohort?

9) Example metric set

If you run an API platform, you might use:

• Visitor → signup conversion rate
• Signup → first successful API call rate
• Median time to first API call
• 7-day and 30-day retention
• Cost per activated developer
• Activated developers by channel
• Retained developers by channel

10) Practical recommendation

If you’re just starting, choose:

1. Signup conversion rate
2. Activation rate
3. 30-day retention
4. Cost per activated developer
5. Activated developers by channel

That gives you a solid view of volume, quality, and efficiency.

If you want, I can also help you:

• define a North Star metric for your specific developer product,
• build a developer acquisition dashboard, or
• suggest metrics for a particular channel like content, GitHub, paid ads, or community.