john

Thank you for your answering! Actually, i did intialize multiple Mixpanel instances with same library name in the past. And now, it is done in GTM only. So, it's not the case. And i finally found that the reset() method is the reason why inconsistency happened. Thank you for your contribution!!!

Good to see you, Julianne! i'm a developer in the same team with Sophie. Our project is built by Vue. And we track the events using GTM. So, the initialization is called twice with same library name before. So, as you said, we remove all the codes about Mixpanel in Vue. But, same cases are happening in our service. (First event has a different device id.). I know that the initialization is called automatically when i track the event. So, the only thing what i did in this project is creating the tag using GTM Mixpanel Template and triggering it. Or, does reset() method make this problem? The project must call reset() method when a user enters the project. I change the code now to call reset() when users logout only and monitor the problem. Below is the project we had problems... https://mixpanel.com/project/3846686/view/4342429/app/events Thank you for your cooperation!!! 🙂

kapa.ai i mean a Track Event's option, "send_immediately". it bypasses batching/queueing and send track request immediately in JS api reference.

kapa.ai i'm using 'send immediately' option on GTM tag. is it possible to happen something wrong in that case?

kapa.ai But it doesn't seem to be initialized before i trigger the first event. So, there's a difference in device id between the first one and the follwowing thing.

kapa.ai Is it neccesary to initialize the mixpanel for event tracking? I understand that the event tracking tags automatically intiallize the mixpanel SDK, so we can use the mixpanel template without initializing it. is it right?