Mixpanel Event Tracking: CS vs. Server-Side Sessions Explained
How does Mixpanel treat events sent to Mixpanel via CS tracking and Server Side tracking how can I ensure that both are treated as the same session?
Hi B, Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> đź‘‹
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
To answer your question about how Mixpanel treats events sent via client-side (CS) tracking and server-side tracking, and how to ensure they are treated as the same session, I'll provide information based on Mixpanel's documentation.Mixpanel treats client-side and server-side events differently when it comes to user identity and session management. Here's how you can ensure that both are treated as the same session: 1. User Identity Management: For server-side tracking, Mixpanel doesn't automatically generate IDs. You need to manage the distinct_id yourself. On the client-side, Mixpanel generates a device_id for both client-side and server-side events. c) Once the user is identified, use the same user ID (device_id and $user_id) across both tracking methods for the best results.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.