[Snyk] Upgrade mixpanel-browser from 2.47.0 to 2.48.1 #232
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade mixpanel-browser from 2.47.0 to 2.48.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: mixpanel-browser
This update patches a discrepancy between the minified and unminified versions of the packaged SDK. Campaign parameters will now be stored as super properties persistently in all versions.
API endpoint routes can now be configured individually, so you can rename /track, /engage, and /groups HTTP endpoints arbitrarily. Configure with the
api_routes
option:In the above example, event-tracking requests will go to
https://my-proxy.example.com/foo/
, user profile updates tohttps://my-proxy.example.com/bar/
, etc.Other fixes:
mixpanel.track()
will no longer be mutatedadd_group()
when adding a new group to an existing listNew default event properties are now captured with each event, holding campaign data present on the URL at the time of tracking. These include UTM parameters (in the format
utm_source
,utm_campaign
, etc.) and Click Identifiers (e.g.,gclid
,fbclid
, etc.). This functionality can be disabled with the initialization setting{track_marketing: false}
.UTM parameter properties are no longer persisted across pageloads as superproperties. They will be present only on events tracked on the same pageload where they were present initially.(2023-09-13) Correction: UTM parameter properties still persist across pageloads as superproperties. Persistence will be removed in a future release.For better first-touch attribution, UTM parameters present on the URL on pageload will be "set once" as profile properties (meaning that a new value will not overwrite any existing value on the profile property). These property names take the format
initial_utm_source
,initial_utm_campaign
, etc. This functionality can be disabled with the initialization setting{skip_first_touch_marketing: true}
.Support for automatic page-view tracking has been restored. With the init option
{track_pageview: true}
, an event named$mp_web_page_view
will be tracked on pageload, containing properties identifying the current page (current_page_title
,current_url_path
, etc.) as well as any UTM parameters and Click Identifiers. Pageview events with these properties can also be triggered manually:mixpanel.track_pageview();
// track pageview with additional properties
mixpanel.track_pageview({'Test variant': 'control'});
Automatic page-view tracking may be turned on by default in a future release.
Miscellaneous updates:
performance.now()
when available as part of its time-based entropy algorithmmixpanel.com
(looser than previous host checks)Commit messages
Package name: mixpanel-browser
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs