## Set up Mixpanel

URL: https://docs.atlan.com/apps/connectors/business-intelligence/mixpanel/how-tos/set-up-mixpanel

> Create a Mixpanel service account with access to your project's Lexicon, and gather the Atlan credentials the app uses to create assets and write certified descriptions back to Lexicon.

:::warning Who can do this?
You probably need your Mixpanel **Organization Admin** to create the service account, and an Atlan admin to generate the Atlan API token—you may not have access to both yourself.
:::

Atlan uses Mixpanel's [Service Accounts](https://docs.mixpanel.com/docs/orgs-and-projects/service-accounts) to read your project's Lexicon (events, event properties, and user properties) and to write certified descriptions back. Because the app runs on the Atlan side and authors assets in your workspace, setup requires **two sets of credentials**:

- A **Mixpanel service account** (username and secret) with access to the project you want to catalog.
- An **Atlan API token** and your Atlan tenant URL, so the app can create the Mixpanel assets, glossary terms, and custom metadata in your workspace and read the certified descriptions it writes back to Lexicon.

## Create service account

1. In Mixpanel, sign in as an **Organization Admin**.
2. Click the **settings gear** and open **Organization Settings** > **Service Accounts**.
3. Click **Add Service Account** and give it a recognizable name (for example, `atlan-catalog`).
4. Grant the account access to the **project** you want to catalog, and assign a **role** that can read the project's Lexicon and (for description write-back) edit it. **Admin** is the safest choice; a read-only role catalogs metadata but can't complete the write-back step.
5. Set an expiration that fits your governance policy, then click **Add**.
6. Copy the **username** and **secret** immediately—Mixpanel shows the secret only once. Save both somewhere secure for [crawling Mixpanel](https://docs.atlan.com/llms/connectors/mixpanel/crawl-mixpanel/llms.txt).

> **Why a service account rather than a personal token?** Service-account credentials are decoupled from any individual's login, survive team changes, and keep your Mixpanel audit log clean. A role with project-wide Lexicon access ensures the crawl returns a complete tracking plan.

## Find your Mixpanel project ID

The connector catalogs one Mixpanel project per connection. To find the project ID:

1. In Mixpanel, open **Project Settings** (the settings gear, then **Project Settings**).
2. Copy the **Project ID**, a numeric value (for example, `12345678`). It also appears in your project URL as `mixpanel.com/project/{project_id}`.

You enter this project ID when you [crawl Mixpanel](https://docs.atlan.com/llms/connectors/mixpanel/crawl-mixpanel/llms.txt).

## Gather your Atlan credentials

The Mixpanel app writes assets and descriptions into your Atlan workspace, so it also needs to authenticate to Atlan:

- **Atlan base URL**: your tenant URL, for example `https://your-tenant.atlan.com`.
- **Atlan API token**: [generate a personal API token](https://docs.atlan.com/llms/platform/get-started/api-authentication/llms.txt) from your Atlan profile. The token must belong to a user (or API-token identity) with permission to create connections and assets, manage glossary terms, and read and write custom metadata.

Keep both ready for the [crawl step](https://docs.atlan.com/llms/connectors/mixpanel/crawl-mixpanel/llms.txt).

## What's next?

You're ready to [crawl Mixpanel assets](https://docs.atlan.com/llms/connectors/mixpanel/crawl-mixpanel/llms.txt).

---