> 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/flagship-deprecated/integrations/fe-and-r-mixpanel/fe-and-r-send-ab-tasty-event-to-mixpanel.md).

# \[FE\&R] Send AB Tasty 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 %}

#### Introduction

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 %}


---

# 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.abtasty.com/flagship-deprecated/integrations/fe-and-r-mixpanel/fe-and-r-send-ab-tasty-event-to-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.