> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentations-integrations/mixpanel-feature-experimentation-integration/send-feature-experimentation-event-to-mixpanel.md).

# Send Feature Experimentation Event to Mixpanel

{% hint style="warning" %}
The AB Tasty **Decision API** must be called using this visitor ID; otherwise, the event will not be sent to Mixpanel.
{% endhint %}

### Overview

The AB Tasty > Mixpanel Connector allows you to automatically send server-side experiment data from AB Tasty’s Feature Experimentation platform to Mixpanel.\
This integration enables you to analyse how specific feature flags and variations impact your product metrics directly within Mixpanel, providing consistent, event-based tracking without requiring client-side scripts.

{% stepper %}
{% step %}
**Configuration on the Mixpanel dashboard**

* Access your **Mixpanel project dashboard**.
* (If you don’t have access yet) Request access from your Mixpanel admin.
* Go to **Project Settings**.
* Copy the **Project Token** (do not use the API secret).
  {% endstep %}

{% step %}
**Create the Mixpanel connector in AB Tasty**

* Access your **Mixpanel project dashboard**.
* (If you don’t have access yet) request access from your Mixpanel admin.
* Go to **Project Settings**.
* Copy the **Project Token** (do not use the API secret).
  {% endstep %}

{% step %}
**Visitor ID Requirement**

Mixpanel requires a known **visitor ID** (`distinct_id`) to link events to the right user.

**Preferred option:** Identify users before sending hits using:

```js
mixpanel.identify('VISITOR_ID');
```

**Alternatively**, retrieve the existing ID via:

```js
mixpanel.get_distinct_id();
```

{% endstep %}
{% endstepper %}

Hit Exemple

```
const uniqueId = uuidv1();
const url = `https://api.mixpanel.com/track`;
const payload = [{
  event: 'flagship',
  properties: {
    token: Configs.token,
    distinct_id: Hit.Vid,
    $insert_id: uniqueId,
    flagship_campaign: `[${Hit.Caid}] ${Hit.Caname}`,
    flagship_variation: `[${Hit.Vaid}] ${Hit.Vaname}`
  }
}];
const defaultHeaders = { 'Content-Type': 'application/json' };
return axios.post(url, payload, { headers: defaultHeaders });
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentations-integrations/mixpanel-feature-experimentation-integration/send-feature-experimentation-event-to-mixpanel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.