Optimizing UTM Parameters in Mixpanel for Accurate Member Tracking

Hey, I have a question about UTM parameters... we want to track where members come from when they come back to their accounts e.g. how many click a webapp notification. We are using UTM parameters for this, but I've just found out that mixpanel stores the first UTM parameters a user touchers as a global property and so it doesn't get replaced if they come back from a different link, this is very annoying! Is there a way to get around this?

17 comments

Juan I.
·
·
have you seen this? https://docs.mixpanel.com/docs/features/attribution#attribution-models
Juan I.
·
·
By the way, I saw your question and asked the AI. I didnt even know MP had this feature available.
Paul C.
·
·
Hey, I'd seen some of this, but when I look at the actual event itself in the Events tab, it doesn't have the correct UTM details and so I'm not sure this will help
Juan I.
·
·
Are you setting the utm? Are you using the front end api? It should come automatically per my understand if you’re using it
Paul C.
·
·
Yeah, it gets set automatically but as a global property in the front end, so it doesn't get replaced when they arrive via a new link
Juan I.
·
·
the idea of the attribution is that you are able to set multiple UTMs so why not letting it with new links? When you say correct UTM what does it mean?
Paul C.
·
·
1.
Member follows a link to their account and it has UTM information A, which mixpanel automatically sets as a global property
2.
A few days later they follow another link to their account and this has UTM information B
3.
But as UTM info A was set as a global property, mixpanel doesn't add UTM information B to the events fired
Paul C.
·
·
Unless I'm missing something, but that's how it seems to be
Paul C.
·
·
The event in mixpanel only shows 1 set of UTM properties, so unless some are hidden somewhere
Juan I.
·
·
Ok. So you will always have A as your utm information. There is no sense of attribution since you won’t to have multiple ones. Correct? Regarding setting utms. Could be an issue in how you are setting with that global property? Have you checked if the property is not being set in some other property? When doing this attribution analysis it doesn’t matter what’s the name of the property. It seems it can be done with any property. It shouldn’t matter.
Paul C.
·
·
re: attribution, yeah exactly
Juan I.
·
·
Oh. It’s an event property?
Juan I.
·
·
It’s not the same as a user property
Paul C.
·
·
re: setting of the UTMs, we don't set them as global properties. The mixpanel library does automatically
Juan I.
·
·
Juan Ignacio Onetto [9:13 AM] Are you setting the utm? Are you using the front end api? It should come automatically per my understand if you’re using it Paul Cox [9:15 AM] Yeah, it gets set automatically but as a global property in the front end, so it doesn't get replaced when they arrive via a new link This was that confused me. You said "yes" to setting global properties 🙂 ok ok. So, I understand now that it looks like its global, where it shouldnt and that you are not setting it yourself and that you are sure they are coming from the different UTM.
Paul C.
·
·
yeah sorry, maybe super property in the front end is the more correct term
Paul C.
·
·
but yeah, we're definitely not setting it ourselves and I'm sure they are coming from a different UTM because I can see it in the current_url parameter