Skip to content
stack
Get started
Provider · Analytics

Mixpanel — Ashlr Stack Provider

Mixpanel: Product analytics. Project token + optional API secret stored in Phantom. Review adapter-specific setup, credential and MCP requirements in Ashlr Stack.

Analytics · API key KEY-ONLY · supplied credential attachment
Mixpanel — Product analytics. Project token + optional API secret stored in Phantom.
Dashboard ↗

One command

Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results. 

stack add mixpanel

Or retrieve catalog matches for what you're building via stack recommend: 

stack recommend "product analytics and feature flags"

Auth flow

Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed.

How-to: Find your project token and API secret in Mixpanel → Settings → Project Settings.

Secret slots

stack add mixpanel has these 2 catalog secret slots; verify which values its adapter actually materializes through Phantom:

  • MIXPANEL_PROJECT_TOKEN
  • MIXPANEL_API_SECRET

Use stack env export --example for an empty-key skeleton. Stack does not automatically fill env files or resolve credential placeholders. stack exec -- <cmd> forwards to installed Phantom exec; configure and verify the app separately.

  • PostHog — Product analytics + flags. Personal API key stored in Phantom.
  • Plausible — Privacy-friendly web analytics. API key verified against the stats API.

FAQ

Do I need a Mixpanel account to use it with Stack?

Use an existing Mixpanel account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed. If you don't have a credential yet, create one at https://mixpanel.com and supply the required inputs; inspect verification and persistence results.

Where does Stack store my Mixpanel credentials?

Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (MIXPANEL_PROJECT_TOKEN, MIXPANEL_API_SECRET); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.

Can I rotate or revoke this integration later?

Use `stack remove mixpanel` for local Mixpanel configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Mixpanel credentials through https://mixpanel.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.

Outbound