people.set_once does not include default people properties about mixpanel-js HOT 3 OPEN

@jacobwegner i think you're dead on here - we're a bit inconsistent with .set/.set_once and Super Properties across our client-side libraries. just so I know the use case, why are you using .set_once more frequently than .set? is there some reason why you're not calling .people.set({"last login": new Date().toISOString()}); (or something similar) regularly to merge in these props? let me know - i'm going to bring this to our product team to see what improvements can be made.

from mixpanel-js.

@arittr sorry for the delay in responding.

The issue I ran into with set versus set_once is that calling set will overwrite the initial referrer info with whatever is currently set in the Mixpanel cookie, while calling set_once would respect the existing value.

In my mind, set_once should mimic any defaults included with set, but never overwrite an existing default if it already exists.

from mixpanel-js.

@jacobwegner no worries - this makes perfect sense and is the perfect use case for set_once . we should be working on an update for the JS lib reasonably soon and will look to include this - we'd also love a PRQ if you ended up fixing the code on your end. thanks for the feedback and sorry for the frustration here!

from mixpanel-js.