Mixpanel + Go Fig

Marketing

Connect Mixpanel to Go Fig to tie product events to revenue, LTV, and segment-level contribution margin.

Mixpanel records every product event your users fire, but the monetary context lives somewhere else: Stripe, Salesforce, NetSuite, QuickBooks. Go Fig pulls Mixpanel events, profiles, cohorts, and funnels into the Financial Intelligence Graph and joins them to billing, booked revenue, and cost-to-serve. The output is activation-to-revenue curves, per-feature monetization, cohort LTV built on real usage rather than proxy engagement, and an ability for Celeste to answer 'which activated-but-unconverted cohort is worth a sales touch' with the underlying unit economics ready.

Connect Mixpanel See All Integrations

Key facts

Auth: Service Account with Project-level access
Grain: Raw event, profile, and cohort membership
Projects: Multi-project supported per connection
Export API: JQL and Raw Events API used for backfills
Sync cadence: Daily incremental, hourly on high-volume projects

SOC 2 Type II · All integrations

What you can do with Mixpanel data in Go Fig

Activation-to-revenue economics

Define activation as a Mixpanel event sequence, then track the revenue outcome of activated vs unactivated cohorts over time using Stripe or Salesforce data joined in the graph. The monetary delta is the answer to 'is activation actually predictive'.

Per-feature monetization

Identify which product features correlate with expansion revenue, renewal, or churn by joining feature-level events to subscription and ARR changes. Supports pricing decisions, sunset decisions, and investment prioritization.

True cohort LTV

Build LTV curves by acquisition month, channel, or segment using real Mixpanel engagement signals rather than survey proxies. Finance gets a defensible payback-period number, marketing gets a CAC ceiling it can trust.

Data available from Mixpanel

Go Fig extracts and normalizes the following data from your Mixpanel account:

Raw events with full property bag

User profiles

Group profiles (B2B accounts)

Cohort memberships

Funnels and conversion rates

Retention curves

Custom properties

Lookup tables

Insights reports

Flow and path data

How to connect Mixpanel

Create a Mixpanel Service Account

In Mixpanel's Organization Settings, Service Accounts, create a new Service Account scoped to Project Member on the projects you want exposed. Service Accounts are preferred over personal API secrets because they do not consume user seats, do not break when someone leaves, and can be rotated without re-authenticating any users.

Choose projects and region

If you operate on Mixpanel's EU residency tier or have multiple projects (separate production, staging, or mobile and web), pick which projects to expose in Go Fig. Each project lands as its own partition so cross-project rollups are explicit rather than accidental.

Map event names to canonical definitions

Mixpanel implementations often have multiple synonyms for the same concept (Signup vs signed_up vs SignUp). Go Fig surfaces the top event names and lets you map them into a canonical set (Signup, Activation, Conversion, Churn). Celeste uses these canonical events for the activation and LTV analyses so naming variance does not break the math.

Join to billing and CRM in the graph

The final step is to join Mixpanel profiles to Stripe or Salesforce identities so revenue follows each user through the funnel. Identity resolution uses email first, then distinct_id if an email match is not available. Once joined, Celeste can answer per-feature revenue impact questions in natural language.

Authentication: Mixpanel Service Account with Project Member or higher role on the projects you want to expose. Service Accounts do not consume seats and can be scoped per project, which is the recommended production pattern over personal API secrets. EU-data-residency projects are supported; connection is region-aware.

Common Questions About Mixpanel Integration

How does Go Fig handle Mixpanel's Raw Events API rate and volume limits?

The Raw Events API (export endpoint) is paginated by date range and rate-limited per project. Go Fig uses an incremental strategy anchored on the event time field: an initial backfill is chunked by day (or hour on very high-volume projects), and steady-state sync pulls events since the last watermark. The connector dashboard surfaces export lag so you can tell if a sync is falling behind a fire-hose event stream.

Does Go Fig support Mixpanel's EU data residency tier?

Yes. Mixpanel's EU residency projects are region-aware, and the Go Fig connector routes API calls to the correct regional endpoint automatically based on the project's configuration. The service account and its permissions are scoped per project, which means a single Go Fig connection can span EU-resident and US-resident projects without data leaving either region improperly.

How is identity resolution between Mixpanel, Stripe, and CRM handled?

Identity resolution happens inside the Financial Intelligence Graph. Go Fig joins Mixpanel profiles to Stripe customers and Salesforce accounts primarily on email address, falling back to distinct_id with an optional override table for edge cases. For B2B products, group profiles (accounts) are joined to Salesforce accounts on domain or account name. Unmatched identities are flagged in the connector dashboard so you can see how much revenue is unassigned.

Can Mixpanel cohorts flow into Go Fig as dimensions?

Yes. Cohort membership is pulled with a timestamp, so 'users in Power User cohort as of Q2' works correctly. Cohorts are modeled as slowly-changing dimensions in Go Fig, which means a user who entered the cohort in March and left in May shows up in the March-April window but not after. This is how cohort-based LTV is calculated accurately rather than using current-state cohort definitions as if they were always true.

Does Go Fig write back to Mixpanel (cohorts, profile updates)?

Not in the default configuration. Go Fig is read-only against Mixpanel in a typical setup. For teams that want to feed finance-derived cohorts (high-LTV accounts, churn-risk accounts) back into Mixpanel for product team visibility, a reverse-sync flow can be configured using Mixpanel's Ingestion API. Write-back requires a separate service account with upload permissions and is opt-in per cohort.