Push GitHub Leads to Mixpanel for Developer Funnel Analytics

Why Send GitHub Signals to Mixpanel

Mixpanel is the product analytics tool of choice for developer-led growth teams. Most companies use it to track in-product behavior — signups, activations, feature usage. But there's a significant gap: Mixpanel does not capture pre-signup developer intent. A developer who starred your GitHub repo three weeks before signing up is a completely different user from someone who discovered you via a Google ad. Mixing those cohorts distorts your funnel analysis.

By pushing GitLeads signals into Mixpanel as user profiles or events, you can build cohorts based on pre-signup GitHub activity. Track whether developers who starred your repo before signup activate faster, convert to paid at higher rates, or have lower churn.

Two Integration Patterns

There are two ways to use GitLeads data in Mixpanel:

1. User profile enrichment — When a GitHub signal fires, check if the developer's email already exists as a Mixpanel user and add signal metadata as a profile property (github_signal_type, tracked_repo, signal_date)
2. Pre-signup event tracking — Create a Mixpanel event for each GitHub signal. When the developer later signs up and you identify them by email, Mixpanel's identity merge connects the anonymous pre-signup events to the identified user

Webhook Integration: GitLeads to Mixpanel

GitLeads delivers lead data via webhook. Use a lightweight serverless function or n8n/Make workflow to forward signals to Mixpanel's Ingestion API:

// Vercel Edge Function: /api/gitleads-to-mixpanel
import type { NextRequest } from 'next/server';

interface GitLeadsPayload {
  lead: {
    name: string;
    email?: string;
    github_username: string;
    company?: string;
    followers: number;
    top_languages: string[];
  };
  signal: {
    type: 'stargazer' | 'keyword';
    repo?: string;
    keyword?: string;
    context?: string;
  };
}

export async function POST(req: NextRequest) {
  const payload: GitLeadsPayload = await req.json();
  const { lead, signal } = payload;

  // Only process leads with known emails (profile enrichment)
  if (!lead.email) {
    // Still track as anonymous event keyed by github_username
    await fetch('https://api.mixpanel.com/track', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify([{
        event: 'GitHub Signal',
        properties: {
          distinct_id: `github:${lead.github_username}`,
          token: process.env.MIXPANEL_TOKEN,
          signal_type: signal.type,
          repo: signal.repo,
          keyword: signal.keyword,
          github_username: lead.github_username,
          company: lead.company,
          followers: lead.followers,
          top_languages: lead.top_languages.join(', '),
        },
      }]),
    });
    return Response.json({ ok: true });
  }

  // Enrich or create Mixpanel profile
  await fetch('https://api.mixpanel.com/engage#profile-set', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify([{
      $token: process.env.MIXPANEL_TOKEN,
      $distinct_id: lead.email,
      $set: {
        github_username: lead.github_username,
        github_signal_type: signal.type,
        github_signal_repo: signal.repo,
        github_signal_date: new Date().toISOString(),
        github_followers: lead.followers,
        github_top_languages: lead.top_languages,
        company: lead.company,
      },
    }]),
  });

  return Response.json({ ok: true });
}

Building Cohorts from GitHub Signal Data

Once GitHub signal properties are in Mixpanel user profiles, you can build powerful cohorts for analysis:

• "GitHub Starred Before Signup" cohort — Users where github_signal_date < first_seen, compare activation vs non-GitHub signups
• "Competitor Stargazer" cohort — Users who starred a competitor repo before signing up, analyze upgrade rate vs average
• "High Follower Count" cohort — github_followers > 500, these are developers with distribution; check if they have higher referral counts
• "Multi-Signal" cohort — Users who triggered both a stargazer AND a keyword signal, likely your highest-intent segment

Using n8n or Make Instead of Custom Code

If you prefer a no-code approach, use n8n or Make to connect GitLeads webhooks to Mixpanel without writing a serverless function. In n8n: (1) create a Webhook trigger node, (2) add an HTTP Request node pointing to the Mixpanel /engage or /track endpoint, (3) map GitLeads fields to Mixpanel properties using n8n's expression editor. This takes about 10 minutes and requires no deployment.

What Mixpanel Cannot Do Without GitHub Signals

Without pre-signup intent data, Mixpanel analysis is limited to post-signup behavior. You can see that developer A activated faster than developer B, but you cannot see that developer A starred three repos in your category before signing up. GitHub signals are the missing layer between awareness and account creation — and they're invisible to Mixpanel without an integration like GitLeads.