Provider · Analytics

Mixpanel — Ashlr Stack Provider

Mixpanel: Product analytics. Project token + optional API secret stored in Phantom. Wire it into your project with one command via Ashlr Stack.

Analytics · API key KEY-ONLY · v0.2 adds provisioning

Mixpanel — Product analytics. Project token + optional API secret stored in Phantom.

Dashboard ↗

One command

Add Mixpanel to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.

stack add mixpanel

Or describe what you're building and let Claude pick it up via stack recommend:

stack recommend "product analytics and feature flags"

Auth flow

Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.

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

Secret slots

stack add mixpanel writes these 2 secret slots into your Phantom vault:

MIXPANEL_PROJECT_TOKEN
MIXPANEL_API_SECRET

The values never leave Phantom in plaintext. Your .env file references slot names, and stack exec -- <cmd> swaps them in at process-spawn time via Phantom's local proxy.

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?

Yes — Stack provisions Mixpanel on your behalf, but it authenticates as you. Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://mixpanel.com and paste it once.

Where does Stack store my Mixpanel credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (MIXPANEL_PROJECT_TOKEN, MIXPANEL_API_SECRET) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.

Can I rotate or revoke this integration later?

Yes. Run `stack remove mixpanel` to pull the Mixpanel service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Mixpanel credentials in their dashboard — https://mixpanel.com — and Stack's next `doctor --fix` will pick up the new values.