Closed surajpuvvada closed 10 months ago
βββββββ4 filesβββββ316 suitesβββ31m 50s :stopwatch: 1β135 testsβ1β135 :heavy_check_mark:β0 :zzz:β0 :x: 1β145 runsββ1β145 :heavy_check_mark:β0 :zzz:β0 :x:
Results for commit f5561e7e.
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
6646d3e
) 82.20% compared to head (f5561e7
) 82.20%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
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.0.
:information_source: 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.- The recommended version is **1 version** ahead of your current version. - The recommended version was released **22 days ago**, on 2023-11-13.
Release notes
Package name: mixpanel-browser
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 listUTM 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:<div class="highlight highlight-source-js notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="// track a pageview event 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
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