Mixpanel

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

Why route Mixpanel through Datafly Signal

• Your numbers stop depending on what the browser allows. Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so Mixpanel receives the complete event stream.
• Client IP and user agent are carried in the payload. Both are taken from the original visitor request rather than your server, which is what Mixpanel needs to attribute the event to the right session.
• Delivery is batched, rate-limited, and retried. Signal buffers to Kafka, respects the Mixpanel rate limit, and retries on 429 or transient failure rather than dropping the event.
• Presets for Retail and B2B / SaaS. The mapping starts from a working configuration for your vertical instead of a blank field map.
• One consent decision governs every destination. Mixpanel is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Prerequisites

Before configuring Mixpanel in Datafly Signal, you need a Mixpanel account, a project and its project token.

API Endpoint

POST https://api.mixpanel.com/track?verbose=1       (US)
POST https://api-eu.mixpanel.com/track?verbose=1    (EU Data Residency)

Each event is a JSON object {"event": "<name>", "properties": {...}} with the project token in properties.token, time in epoch milliseconds and $insert_id (the Signal event ID) for deduplication (Track Events). verbose=1 makes Mixpanel answer {"status": 1} or {"status": 0, "error": "..."}, so a rejected event is reported instead of counted as delivered.

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.
   • 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",
      "eu_data_residency": false
    },
    "delivery_mode": "server_side"
  }'

Presets

Each event keeps its Signal name (page views are sent as page_view) and its documented properties as event properties, numbers typed as numbers. Events a preset does not list are not sent. You can customise any preset after installation.

Identity

Signal follows Mixpanel’s server-side Simplified ID Merge guidance: every event carries $device_id (the Signal anonymous ID) and, once the visitor is identified, $user_id (the user_id from datafly.identify()). Signal also sets distinct_id to the user ID once known, else the anonymous ID: under Simplified ID Merge that is the value Mixpanel would derive (a set distinct_id must equal $user_id), and projects on the Original ID Merge API, the default for organisations created before April 2024, need it on every event. Mixpanel merges $device_id and $user_id when an event carries both (Simplified ID Merge only).

identify() traits are not forwarded, and user profile updates (/engage) are not part of this integration. Event properties are forwarded as sent, so keep personal data out of track() properties (the event specs require it), and the client IP is sent as ip for geolocation.

Consent

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

Revenue

purchase carries value (a number), currency, transaction_id and the items array as event properties. Use value as the revenue property in Mixpanel’s reports.

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 the user ID ($user_id) or the anonymous ID ($device_id).
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.4.0 (not yet tested against a live Mixpanel project). It ships with Default, Retail, B2B / SaaS, Media & Streaming, Insurance and Travel presets.

See also

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