Skip to content
DestinationProduct analytics

Mixpanel

Events enter through /import, Mixpanel's server path: each carries distinct_id, the real event time and an $insert_id — the identifier Mixpanel itself uses to discard duplicates if a resend ever happens.

Data delivered

Data delivered

  • Free-form events with properties
  • Consistent distinct_id (lead or visitor)
  • Automatic $insert_id for deduplication

What it is for

What you can do with it

  • Bring conversions and business events into Mixpanel boards
  • Import with strict validation: malformed events come back with an error, not silently dropped

Why integrate

The business reason, not just the tech

Analysis on events that already earn money

The events firing ad conversions are the same ones telling the journey. In Mixpanel they become funnels, retention and cohorts — no re-instrumenting.

Imports that never fail silently

We use /import with strict validation: malformed events come back with a named error instead of being accepted and dropped. And $insert_id guarantees retries never duplicate.

How to connect

Step by step

  1. Step 1

    Copy the api_secret (or service account) and the project id.

  2. Step 2

    Create the destination with both.

  3. Step 3

    Create a Delivery with the events to track.

Frequently asked questions

Why strict validation?

The /import strict flag turns on Mixpanel's own validation: if something is off-contract, the response says which event and why — instead of accepting and silently discarding.

Start measuring what actually becomes revenue

Create a free account, connect your first source and see your first lead timeline today. No card required.