Mixpanel

Server-side event and profile delivery to Mixpanel via the Ingestion API for product analytics, funnel analysis, and user segmentation.

Prerequisites

Before configuring Mixpanel in Datafly Signal, you need a Mixpanel account, a project, and your project token and API secret.

API Endpoint

POST https://api.mixpanel.com/track          (US - events)
POST https://api.mixpanel.com/engage         (US - profiles)
POST https://api-eu.mixpanel.com/track       (EU - events)
POST https://api-eu.mixpanel.com/engage      (EU - profiles)

Events and profile updates are sent as JSON payloads. Authentication is handled via the project token in the request body.

Configuration

Management UI Setup

1. Go to Integrations in the sidebar.
2. Open the Integration Library tab.
3. Find Mixpanel or filter by Analytics.
4. Click Install, select a variant if available, and fill in the required fields:
   • Enter your Project Token from Step 3.
   • Paste your API Secret from Step 4.
   • Toggle EU Data Residency on if your organization is EU-based (Step 5).
5. Click Install Integration to create the integration with a ready-to-use default blueprint.

Management API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/mixpanel/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Mixpanel",
    "variant": "default",
    "config": {
      "project_token": "abc123def456789",
      "api_secret": "your_api_secret",
      "eu_data_residency": false
    },
    "delivery_mode": "server_side"
  }'

Variants

Each variant provides a tuned default blueprint. You can customise any setting after installation.

Identity

Mixpanel uses a two-part identity model based on distinct_id and $user_id.

Anonymous Users

Before a user is identified, Datafly Signal sends the Datafly anonymous_id as Mixpanel’s distinct_id. This creates an anonymous user profile in Mixpanel.

Identified Users

When your application calls datafly.identify(userId), Datafly Signal sends the user ID as $user_id and calls Mixpanel’s $identify operation to merge the anonymous and known user profiles.

datafly.identify("user-123", {
  email: "jane@example.com",
  plan: "premium"
});

How Mixpanel Resolves Identity

1. Anonymous visitor: Events arrive with distinct_id set to the Datafly anonymous ID.
2. User identifies: A call to datafly.identify("user-123") triggers a $identify event linking the anonymous distinct_id to the known $user_id.
3. Merge: Mixpanel merges the anonymous and identified profiles, attributing prior anonymous activity to the identified user.
4. Subsequent events: All future events include $user_id as the distinct_id.

Event Mapping

The Retail variant maps the following events to Mixpanel’s product-analytics event names:

Identity (default blueprint)

The default blueprint forwards the following identifiers:

For anonymous visitors, Signal uses the anonymous identifier so events still create a profile in Mixpanel. When datafly.identify() is called, subsequent events resolve to the identified user.

Consent

Default consent category: analytics. Events are suppressed for visitors who have not consented to analytics tracking.

Revenue Tracking

When Datafly Signal receives an Order Completed event, it maps the transaction data to Mixpanel’s revenue tracking:

Revenue events appear in Mixpanel’s Revenue report and are attached to the user profile via the $transaction people operation.

User Properties

When datafly.identify() is called with traits, those traits are forwarded to Mixpanel as profile properties via the $set operation on the /engage endpoint:

{
  "token": "abc123def456789",
  "distinct_id": "user-123",
  "$set": {
    "$email": "jane@example.com",
    "$name": "Jane Smith",
    "plan": "premium",
    "company": "Acme Inc"
  }
}

Mixpanel reserves certain property names (prefixed with $) for standard fields like $email, $name, $phone, and $city. Datafly Signal automatically maps common trait names to the corresponding Mixpanel reserved properties.

Verify it’s working

1. In the Signal Management UI, open your Mixpanel integration and watch the Live Events stream as you trigger events on your site.
2. Confirm 200 responses from the Mixpanel /track endpoint.
3. In Mixpanel, open Events in the left sidebar — events arrive in seconds.

Testing

Once your integration is active and events are flowing, verify in Mixpanel:

1. In the Mixpanel dashboard, go to Events in the left sidebar.
2. The Events feed shows events arriving in real-time — look for your tracked event names.
3. Click on an event to inspect its properties and verify the data is correct.
4. Go to Users and search by distinct_id or user properties to find a specific user profile.
5. Check the user’s Activity Feed to see their full event history.

Troubleshooting

Delivery

Events are delivered server-side from your Datafly Signal infrastructure directly to the Mixpanel Ingestion API. No client-side Mixpanel scripts are loaded for this integration.

Blueprint

The Mixpanel blueprint version is 0.1.0 (alpha). It ships with Retail and B2B / SaaS variants covering pages, product views, add-to-cart, and purchase.

See also

• Amplitude — alternative product analytics destination.
• Heap — autocapture product analytics.