Bump mixpanel-browser from 2.45.0 to 2.47.0 in /apps/block_scout_web/assets

[dependabot]

Bumps mixpanel-browser from 2.45.0 to 2.47.0.

Release notes

Sourced from mixpanel-browser's releases.

Marketing analytics improvements

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.

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:

// 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:

• UUID generation now uses performance.now() when available as part of its time-based entropy algorithm
• The network payload format now defaults to JSON for any API host containing the string mixpanel.com (looser than previous host checks)

Identity management updates

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.

Changelog

Sourced from mixpanel-browser's changelog.

2.47.0 (27 Apr 2023)

• Collect richer marketing attribution properties for multi-touch attribution
• New implementation of previously-deprecated track_pageview() method and init option to send automatically
• Use performance.now when available for time-based entropy component of UUID-generation (thanks @​adrianherd)
• looser API Host check for default JSON-payload sending to mipxanel.com hosts

2.46.0 (20 Mar 2023)

• Updates for new identity management system
• More aggressive deduplication within batch sender

2.45.0 (17 Feb 2022)

• Remove all code related to in-app messaging feature
• Add error_reporter config option for user-configurable handling of errors
• Fix missing var declarations in HTML script snippet
• Fixes for some batch/retry edge cases where localStorage write failures resulted in duplicate sends

2.43.0 (5 Jan 2022)

• Support plain JSON tracking payloads (no base64-encoding) and use as default when sending to *.mixpanel.com API hosts

2.42.1 (20 Dec 2021)

• Add new crawler user agents to blocked list (ahrefsbot, petalbot)

2.42.0 (9 Nov 2021)

• Make batch_requests default-on for all remaining projects
• Replace unload event listener with modern alternatives (thanks @​JoaoGomesTW)
• Don't retry requests blocked by client (adblockers)
• Retry with backoff after 429

2.41.0 (28 Jan 2021)

• Remove all code related to Autotrack feature

2.40.1 (19 Jan 2021)

• Add new crawler user agents to blocked list (pinterest, fb, bingpreview, more google crawlers etc)
• Add debug-mode logging when opt-out/DNT is preventing tracking
• Add more explicit console warning when embed script has been added multiple times on a single page

2.40.0 (2 Dec 2020)

• Add persistent option to register(), to support setting superproperties only for the current pageload
• Add before-send hooks for transforming/enriching data before it goes over the network
• Add batch_autostart config option and start_batch_senders() method, to allow extra control over when batches start sending over the network
• Fix request-batching when sendBeacon is specified as default API transport
• Increase batch_requests default rollout to 60% of projects

2.39.0 (17 Aug 2020)

• Escape body of POST requests to ensure valid base64 is sent to APIs (thanks @​dpraul)
• Don't opt in to request-batching automatically if using a custom API host (thanks @​chriszamierowski)
• Increase batch_requests default rollout to 30% of projects

2.38.0 (12 Jun 2020)

• Ensure that first-touch referrer/UTM params get saved in superproperty storage even if no events are tracked on the page

... (truncated)

Commits

• 8ac526e 2.47.0
• fd79882 rebuild 2.47.0
• 0302eb3 changelog for 2.47.0
• b28e501 jsdoc type fix for track_pageview
• cc05245 loosen restriction on automatically setting payload type to json from mixpane...
• ba3532c make batcher tests resilient to lib version changes
• cda87b5 rebuild 2.47.0-rc1
• be51d6a Merge branch 'adrianherdfixUuidStalling' into v2.47.0-rc
• 557b4db fix track_pageview minification bug and ensure legacy function signature does...
• b8d61ab a little marketing branch cleanup
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)