-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency mixpanel-browser to v2.55.0 #92
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/mixpanel-browser-2.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
837f640
to
ea1971a
Compare
ea1971a
to
344d00c
Compare
50a0811
to
c1bf1e8
Compare
c1bf1e8
to
d462959
Compare
4b6e63f
to
bd30a05
Compare
bd30a05
to
e697c96
Compare
e697c96
to
2e7ed78
Compare
2e7ed78
to
d97245f
Compare
d97245f
to
011e737
Compare
bcece01
to
b8d8ea8
Compare
b8d8ea8
to
56cda94
Compare
56cda94
to
c21aa38
Compare
c21aa38
to
32e2a54
Compare
32e2a54
to
aea1ebf
Compare
aea1ebf
to
fc8335e
Compare
fc8335e
to
4bb3a06
Compare
4bb3a06
to
61efabc
Compare
61efabc
to
3a06406
Compare
7b02cd7
to
8ccc0f7
Compare
8ccc0f7
to
3e9fc79
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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 contains the following updates:
2.45.0
->2.55.0
2.38.0
->2.49.1
Release Notes
mixpanel/mixpanel-js (mixpanel-browser)
v2.55.0
Compare Source
v2.54.1
Compare Source
v2.54.0
: Module bundling and session recording updatesCompare Source
The SDK is now provided in several new builds with different options around included modules and asynchronous loading:
mixpanel-recorder
session-recording module (default):mixpanel-recorder
asynchronously via script tag (previous default):This release also includes updates and improvements to the session recording module:
NOTE: with image-inlining turned on, image-intensive pages may increase payload size significantly and possibly surpass the API server's request size limit.
v2.53.0
: Session recording updatesCompare Source
v2.52.0
: Revert to persisting UTM params by defaultCompare Source
This release reverts the UTM param persistence change introduced in v2.51.0, to minimize disruption for older implementations. UTM parameters will be persisted by default in super property storage when the SDK finds them on pageload. To opt in to the recommended modern behavior, use initialization option
{stop_utm_persistence: true}
.v2.51.0
: Updates to UTM param persistence, localStorage/cookie migration, session recordingCompare Source
{stop_utm_persistence: false}
.record_block_class
,record_block_selector
, andrecord_mask_text_class
offer finer-grained control over elements to block in session recording, and provide stricter defaults.mixpanel.get_session_recording_properties()
exposes Replay ID property for tagging events controlled by other client-side SDKs such as Segment or mParticle.v2.50.0
Compare Source
v2.49.0
: Attribution/web analytics updatesCompare Source
This release updates capabilities related to web/marketing/attribution analytics.
The
track_pageview
init option now accepts three string values to support SPA pageview tracking:"url-with-path"
: fire pageview events only when main url path changes (https://example.com/foo
->https://example.com/bar
but nothttps://example.com/foo?bar=1
->https://example.com/foo?bar=2
)"url-with-path-and-query-string"
: fire pageview events only when main url path or query string changes (https://example.com/foo?bar=1
->https://example.com/foo?bar=2
but nothttps://example.com/foo?bar=1#baz
->https://example.com/foo?bar=1#qux
)"full-url"
: fire pageview events when anything on the URL changesExample:
Profile properties storing referrer info (
$initial_referrer
and$initial_referring_domain
) are now saved withset_once
instead ofset
, to prevent overwriting.Persistence of UTM parameters can now be turned off with the init option
{stop_utm_persistence: true}
. This is opt-in today but will be the default setting in a future release. Thestop_utm_persistence
option will also override thestore_google
option, which is responsible persisting UTM parameters today. Ifstore_google
andstop_utm_persistence
are bothtrue
, any persisted UTM parameters will be cleared from storage.Visits from AhrefsSiteAudit crawler are now ignored.
v2.48.1
: Minification fix for UTM campaign propertiesCompare Source
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.
v2.48.0
: Configurable API endpoints, miscellaneous updates and fixesCompare Source
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 listv2.47.0
: Marketing analytics improvementsCompare Source
New 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: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)v2.46.0
: Identity management updatesCompare Source
The
mixpanel.identify()
implementation has been updated for compatibility with Mixpanel's new identity management system (v3). From this version, we will prefix randomly-generated device-specific distinct_ids with "$device:". The prefix is applied the next time a new random ID is generated; any IDs generated by previous SDK versions and persisted in the browser will continue to be used as-is until reset is called to generate a new ID. This does not change the value sent for the$device_id
property, which will continue to be the randomly-generated ID without a prefix. Mixpanel's $identify endpoint has been updated to accept UUIDs with this prefix to coordinate with this change.This release also contains more aggressive client-side deduplication in the event-batching system, to reduce superfluous network sends in edge cases where parts of the queue/batch system fail. Related to this update, events now include a property
mp_sent_by_lib_version
which can distinguish the version of the library that actually sent an event over the network vs the version that originally queued the event.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.