Mixpanel + Data Alias: Read Mixpanel profile properties with a secret that stays in your tab
Why use Mixpanel with Data Alias
User profiles in product analytics sit right next to emails, names and account IDs. This reads only the properties you choose into review, so the behaviour stays analysable without the identities riding along.
How it works
Mixpanel has no sign-in for this: it takes a service account, which is a username and a secret. You pick the data residency your project lives in — US, EU or India — and give the project ID. The secret is kept in this tab's memory only and travels in an Authorization header to Mixpanel, never to a Data Alias server. The property list comes from your project's Lexicon schema rather than from anyone's profile, so you choose before any person is read.
What it does
- Read profiles with the properties you pick, and the distinct ID
- Offer the property list from Lexicon, without reading a profile first
- Show the secret only as a mask
- Drop a secret Mixpanel rejects instead of retrying it
- Forget the secret on request, on sign-out and when the tab closes
How it will connect
These are the steps once the connection is available. Until then: Export the profiles from Mixpanel as a CSV and upload the file to Data Alias.
- 1
Create a service account in Mixpanel
Organization settings → Service Accounts. Give it read access to the project you want, and remove it afterwards.
- 2
Read where the secret will be kept, then paste it
Data Alias shows those terms above the field, before you paste.
- 3
Pick the region, the project and the properties
US, EU or India data residency, the numeric project ID, then the properties to read. The distinct ID always counts as one column.
- 4
Review in your browser
Detection, your rules and the review before export run in the tab, the same as for an uploaded file. Change any suggestion you disagree with.
What moves where
- What reaches Data Alias servers
- Nothing. There is no server step at all — your browser talks to Mixpanel.
- Where the secret is kept
- This tab's memory. Never in storage, a cookie, a URL or a Data Alias server.
- What Data Alias reads
- Your project's Lexicon property names, then profiles with the properties you picked.
- Never sent
- The original file, the alias mapping, and restored results with real names never leave your browser.
Limits worth knowing
- The properties on offer are the ones your project defines in Lexicon. A project with none shows an empty list, and you can still import the distinct IDs.
- “Forget this secret” removes it from Data Alias; it doesn't revoke it. Delete the service account in Mixpanel when you're done.
- While the secret is in memory, it is as reachable as any other value in the page. What this removes is the lasting exposure — disk, logs, URLs, screenshots and servers.
Can I connect Mixpanel today?
No. The connection is built and tested against stand-ins for Mixpanel, but it hasn't been run against a real Mixpanel account, so there is nothing to connect yet. Export the profiles from Mixpanel as a CSV and upload the file to Data Alias.
Where is my service-account secret kept?
Only in this tab's memory. It isn't written to local storage, session storage, IndexedDB or a cookie, and a refresh clears it.
Why a service account instead of the project secret?
Mixpanel accepts either for this API. A service account is the narrower credential and can be removed on its own, so it is the only one Data Alias offers.
Does Data Alias read events too?
No. It reads user profiles — the distinct ID and the properties you pick. Event streams are not part of this.
Data Alias reduces exposure risk but cannot guarantee detection of every sensitive value. Every transfer passes the same review as a download — check the result before you send it. How connected services are handled.