Releases: mParticle/mparticle-web-sdk
Version 1.14.5
- Reduce the size of persistence by removing any keys that have no value attached, and by removing server settings that are not being used
Version 1.14.4
- Support for Chrome headless testing
- Allow logging of multiple impressions at once as an array
- Move cartProducts and productBags to localStorage
Version 1.14.1
- Fixes for cookie syncing. Properly cookie sync when MPID changes, and only perform a cookie sync when debug modes for defined pixel and mParticle match
- Store productsBags and cartProducts to cookies, with config option to change number of products allowed in each (config.maxProducts = 20 by default)
- Prevent setUserIdentity from accepting booleans
- Clean up code - Add additional validations, convert remaining == to ===
Version 1.14.0
- Support for cookie-syncing. Cookie-syncing enables the optional collection of 3rd-party IDs to enable enhanced audience sharing with advertising platforms such as DoubleClick, Adobe, and AppNexus
- Add application state transition to mParticle initialization
Version 1.13.1
In this release, we now send the duration of the session length as an event parameter when a session ends.
Includes a fix for removing duplicate user identities where ID is missing, allow ID to be undefined. Includes a fix for creating CGID on initial load
Version 1.12.0
In this release, we added the ability to retrieve deviceIds via mParticle.getDeviceId().
Version 1.10.0
In this release, we added a config option for useCookieStorage to allow use of either cookies or localStorage. If localStorage is not available, the SDK reverts to cookie use. By default, localStorage is used.
We also fixed a bug where the forwarders array included a mix of both initialized and uninitialized forwarders. Now it only contains initialized forwarders, which is defined as when the forwarder and the mParticle instance are both in the same environment (both in production, or both in development).
Version 1.9.0
In this release, we fixed bug where calling setUserIdentity with a similar type added another identity, rather than replacing the identity. Relatedly, calling setUserIdentity with id = null and a valid type will remove the user identity of that type.
Additionally, we now include CommerceEvent custom attributions in expansion. Rather than referencing the original commerce event (which would mutate it), this makes a copy.