Hey, anyone experienced with the Segment > Mixpanel integration? We have deployed the Segment tracking on our website + Mixpanel Destination and event's mapping. However in our testing Mixpanel property it seems like it is not processing UTMs and Referrer data correctly. https://docs.mixpanel.com/docs/tracking-best-practices/traffic-attribution
Mixpanel’s Javascript library tracks all UTM tags by default. Mixpanel’s Javascript library will track Initial Referrer and Initial Referring Domain and append them as a property to any event that a user completes
Hi Josh, amazing. Thanks for such a quick reply. This is a list of dimensions that are created automatically in my production Mixpanel project where Mixpanel is directly part of the code. But it seems that Segment works slightly different and traffic attribution does not work.
This is how mapping is made. I think the Mixpanel’s Javascript library default functionality is not working in this case as it's managed by Segment.
is this web or mobile? Client or server side?
It is web, client side tracking via our own proxy domain.
Understood
If you haven't already - look at this
You will also notice in the debugger in Segment that it would generally pass through the referrer and path as standard. In Mixpanel you can create custom properties which can group certain values together, where you can actually provide a proxy name and also utilise this for traffic source measurement in Mixpanel 👌
Thanks, yes this is what I have checked, I have checked also User Traits in the Segment - it parses the UTMs out of the URL. Image 2 - Pageview event mapping.