Mixpanel Js Versions Save

Official Mixpanel JavaScript Client Library

v2.31.0

4 years ago

The default API server address has changed from https://api.mixpanel.com to https://api-js.mixpanel.com. Functionality is unchanged.

v2.29.1

4 years ago

Fix a race condition for events tracked before notifications are loaded

v2.29.0

4 years ago

mixpanel.identify() now sends a special $identify event to the API. This is not treated like a regular tracking event, but will aid in future platform improvements to support advanced identity management (linking anonymous and logged-in usage, multiple users on one system, etc.).

This release also contains a fix for accidental non-debug-mode console logging in the Group API module.

v2.28.0

5 years ago
  • Add support for event triggered in-app notifications Currently users have no control over when an in-app notification shows up. With this release users can now control when an in-app gets displayed based on an event that they track using the sdk. This "trigger" event is configured during the message creation flow. You can additionally filter the event based on properties that are tracked along with the event for even finer controls.

v2.27.0

5 years ago
  • new Mixpanel config option inapp_link_new_window controls whether links in inapp notifications will open in a new window/tab (defaults to false)
  • new Mixpanel config option inapp_protocol takes precedence over built-in protocol-agnostic resource links (for instance loading https://example.com/image.png rather than //example.com/image.png)
  • cross-subdomain tracking now works for TLDs with more than 6 characters, like .company

Example usage of new configuration options:

mixpanel.init('<MY-TOKEN>', {
  inapp_link_new_window: true,
  inapp_protocol: 'https://',
});

v2.26.0

5 years ago
  • Fix minification issue with DoNotTrack browser setting
  • Pass flag to backend indicating when $distinct_id might have been set to a pre-existing $distinct_id value instead of a generated UUID (used when resolving aliases)

v2.25.0

5 years ago
  • Change the behavior of opt_out_tracking_by_default to no longer override any existing opt status when the user has an opt-in cookie. It also no longer clears persistence when set to true.
  • Create a new param called opt_out_persistence_by_default which will determine whether SDK persistence is turned off during initialization

v2.23.0

5 years ago
  • time prop is now set automatically with all events, recording UTC timestamp (in seconds) as the client (browser) sees it. The automatic value can be overridden by setting the time prop explicitly in tracking calls.
  • $user_id and $device_id superprops are set as part of identify/reset flows. This allows finer-grained identity management around linking anonymous, logged-in, and logged-out behavior. New additional behavior is as follows:
    • If the distinct_id is not stored in the persistence (cookie/localStorage) at the time of mixpanel.init() then the lib will set a field $device_id which will be the same as the distinct_id generated using UUID.
    • When identify() is called, $user_id will be set in the persistence to the value passed to the identify() call. For example, if you call mixpanel.identify('[email protected]'), $user_id will be set to "[email protected]".
    • If any of those fields ($device_id and $user_id) is set in the persistence, all events and property updates will have those fields added in addition to your properties.

v2.22.4

5 years ago

Ensure GDPR cookies are always cleared when possible

v2.22.3

5 years ago

Bugfix for previous patch