v1.8.13

1. update campaign logic

V1.18.12

1. Add Idempotent transaction id support

V1.18.11

Optimizing batching:

• if failed to enqueue an event, send immediately.
• if in very rare cases, failed to remove from queue 5 times, stop batching.
• drop very old events

v1.8.10

• Improved support for UTM tracking for companies to ensure initial campaign data used

V 1.8.9

• If identifyUser/identifyCompany/identifySession is called with null or undefined, print out error message and skip.

V 1.8.8

Add:

Better handling if browser blocks web3 instrumentation.

v1.8.5

Add:

• Don't save referrer info if it's the same domain
• More relaxed query string parsing for non-conforming URLs such as /#signup?utm_source=x

v1.8.2

Fix:

• Issue where marketing campaign data may not be collected until after identifyUser is called

v1.8.1

Fix:

• Issue where navigating cross subdomains may still create a new anonymous user

v1.8.0

Fixes:

• Improved how anonymous ids are stored in cookies vs local storage. Now when set to localStorage (the default setting), the SDK write session info to localStorage and then replicate to a cookie for redundancy. This ensures that if the user clears local storage or visits a different subdomain (like from docs.acmeinc.com to acmeinc.com), there is still
  a cookie to fall back to.