Integrations / Analytics
Mixpanel
Server-side event tracking to Mixpanel for product analytics.
Datafly Signal delivers first-party events to Mixpanel server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Mixpanel expects.
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.
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.
What ships in the blueprint
Mapped events
add_to_cartfeature_usedloginpagepurchasesign_upsubscription_startedview_itemVertical presets
Retail, B2B / SaaS. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Mixpanel documentation.
Frequently asked questions
Does Datafly Signal integrate with Mixpanel?
Yes. Datafly Signal delivers first-party events to Mixpanel server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Mixpanel expects. The integration is included in every deployment at no additional cost.
How is server-side Mixpanel tracking different from the Mixpanel tag?
The Mixpanel tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Mixpanel from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Mixpanel?
The blueprint ships with mappings for add_to_cart, feature_used, login, page, purchase, sign_up, subscription_started, view_item. Any event in your schema can be mapped to Mixpanel through pipeline configuration without a code change.
Do I need to keep the Mixpanel tag on my site?
No. Signal delivers to Mixpanel from the server, so no client-side Mixpanel script is required on your site.
Other analytics integrations
Ready to move Mixpanel server-side?
See how Datafly Signal delivers first-party events to Mixpanel from infrastructure you control, with hashed identity and consent enforcement built in.