This seems like it's just a serialized cookie, am I missing something?<p>One thing that would make this insanely valuable is if you had the option to follow the same rules that google analytics uses to store UTM cookies.<p>Since the release of analytics.js they no longer allow you to ask the ga object what it thinks the current utm variables are (as they can be overwritten, expire, etc). One might want to do this to track stuff in their own database, etc.<p>That means one has to attempt to model their algorithm to get it to work, and lets just say thats super annoying:<p><a href="https://lh3.googleusercontent.com/8EiYEKczs9NLsuKkZjRmeygRZ1DjP2NWTI5BQ2_3n8iOjfsbb3GjL4ETu241M5gZEOs=w721" rel="nofollow">https://lh3.googleusercontent.com/8EiYEKczs9NLsuKkZjRmeygRZ1...</a>
This is pretty cool, but it seems like it doesn't store data for multiple visits. Say I land via Google yesterday, come back today via HN, then sign up. I'd like to know all that.