While you can't record replays server-side, Mixpanel's Server-Side Stitching allows server-side events (sent via API, backend code, or warehouse imports) to be linked to existing client-side replays. It works by matching the event's timestamp and Distinct ID to an active replay session. [Server-Side Stitching]
For example, if a Purchase Completed event is fired from your server, Mixpanel can infer which replay it belongs to and let you view what the user was doing at that moment. [Server-Side Stitching]
To ensure this works correctly, you should call identify() from the client-side SDK so that both client and server events share the same Distinct ID. [Replay ID docs]
So in summary:
Recording replays → client-side only
Associating server-side events with replays → possible via Server-Side Stitching
