> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-visualization-tools/mixpanel.md).

# Mixpanel

An overview of the Mixpanel integration with Secoda

{% content-ref url="/pages/Q7fYos8WhUZy6Jyjxqce" %}
[Mixpanel Metadata Extracted](/integrations/data-visualization-tools/mixpanel/metadata-extracted.md)
{% endcontent-ref %}

## Getting Started with Mixpanel

There are 2 steps to connect Mixpanel with Secoda:

1. Create a service account for your organization
2. Connect Mixpanel to Secoda

#### Create a Service Account

To create a service account, navigate to [Mixpanel](https://mixpanel.com/login/) and log into your account. Use the following steps to create a service account:

1. Click on the ‘settings’ button in the top right corner
2. Click on ‘organization settings’
3. Click on ‘service accounts’ on the left side bar
4. Click the ‘add service account’ button in the top right
5. Give it a name, select ‘member’, select all projects you want to be integrated with Secoda, select ‘analyst’ and ‘never’
6. **Save the username and secret, as the secret can not be accessed again**

> Note: Any service account settings will work for Secoda, so an existing account can be used as well. These are just our recommended settings.

#### Connect Mixpanel to Secoda

#### After creating your service account, the next step is to connect it to Secoda:

1. In Secoda app, select ‘add integration’ on the integration tab
2. Search for and select ‘Mixpanel’
3. Enter the service account username and secret, and the desired teams it will be linked to
4. Click ‘connect'

### After Connecting to Secoda

Due to [mixpanel rate limits](https://docs.mixpanel.com/docs/other-bits/rate-limits), some event properties may be missing after the initial extraction(s). Each time an extraction is run in Secoda, more event properties will be added until all events have been populated.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secoda.co/integrations/data-visualization-tools/mixpanel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.