-
Notifications
You must be signed in to change notification settings - Fork 47
Migrate from mixpanel to segment #869
Copy link
Copy link
Closed
Labels
analyticsIssued connected to tracking and analytics.Issued connected to tracking and analytics.t-webIssues with this label are in the ownership of the web team.Issues with this label are in the ownership of the web team.
Milestone
Metadata
Metadata
Assignees
Labels
analyticsIssued connected to tracking and analytics.Issued connected to tracking and analytics.t-webIssues with this label are in the ownership of the web team.Issues with this label are in the ownership of the web team.
Type
Fields
Give feedbackNo fields configured for issues without a type.
In order to unify the single source of truth of analytical tracking, we want to migrate from
mixpaneltosegmentas we do across all web apps. In this initial update we just want to replace packages, no need to adjust event names etc.Example of server side tracking implementation in core can be found here. Make sure both
userIdandanonymousIdare filled with each event. Contact @mr-rajce about setting up custom segment workspace and providing token key.We've added new segment workspace for production data:
For development and testing purposes this segment workspace can be used:
For current implementation we don't need to send
identifyevents, it should get matched automatically in segment as long as we senduserIdintrackevents.