Releases: Conviva/conviva-js-script-appanalytics
Releases · Conviva/conviva-js-script-appanalytics
v0.6.6
0.6.6 (25/APR/2024)
- Enables auto-tracking of visibility change events in the web applications by sending the
conviva_application_foreground
andconviva_application_background
events, which are enabled by default. - Enables auto-tracking of lcp (Largest Contentful Paint) context.
- Enables auto-tracking of the First App Launch feature by using the First Launch custom tag context.
- Allows auto-tracking of the Window Load event in the web applications. This is achieved by sending the
conviva_window_loaded
custom event, which is enabled by default. - Allows auto-tracking of visibility state change to be hidden before tracking the page view. This is achieved by sending the
conviva_app_backgrnd_before_page_view
custom event, which is enabled by default. - Optimizes the payload size by applying gzip encryption and schema optimization.
- Supports custom gateway URL by using the unique
CUSTOMER_KEY
associated with each customer. - Renames the remote configuration URL domain to
*.[conviva.com](http://conviva.com/)
. - Updates the default block list of the Network Request Tracking feature.
- Introduces a new Performance Context based on
PerformanceNavigationTiming
. The old Performance Context, based onPerformanceTiming
, is deprecated. By default, the old Performance Context remains enabled. Configure the new Performance Context via Remote Config. - Integrates custom and video events tracking configurations into Remote Config to offer a unified setup.
- Improves the Custom Event Blocking logic by implementing the substring matching technique.
- Resolves the Traceparent header generation issue. Now the Traceparent header is generated for all target URLs that are set to
*
intraceparentconfig
. - Reduces the number of cached payload data entries in local storage from 1000 to 10, and the sending limit of the entries without caching from 40kb to 20kb. Both these settings are manageable via Remote Config.
- Changes the behavior of local storage from Last In, First Out (LIFO) to First In, First Out (FIFO), when the maximum limit (10 entries) is reached.
- Reduces the payload size of Network Request Event by limiting the default attributes to
targetUrl
,method
,responseStatusCode
andduration
. However, the retention of request/response body/header attributes remain unchanged.
v0.5.3
v0.5.3 (07/FEB/2024)
- Added capability to generate "traceparent" header for network requests based on config. Please refer to traceparent feature for more details.
- Fixes issue of missing "assetName" from conviva video events.
v0.4.8
v0.4.8 (25/JAN/2024)
- Added capability of autotracking meta tags present inside HEAD section of HTML page based on keys provided as config. Please refer to Meta Tags feature for more details.
- Added functionality for app to report appVersion as part of init config. Please refer to Initialize the tracker for more details.
- Enhances network requests & response collection feature to support collection of response and request body where content-type is
text/javascript
,application/javascript
along with already supportedtext/plain
andapplication/json
. - Enhances trackPageView api to take custom page title as input. Please refer to trackPageView Info for more details.
v0.4.6
v0.4.5
v0.4.4
v0.4.3
v0.3.34
v0.3.34 (19/OCT/2023)
- Fixes issue in linkClickTracking & buttonClickTracking generating lots of console errors due to internal initialization sequence.
- Fixes and stops reporting exceptions / errors containing no information, status code and stacktrace. Such as browser errors caused due to extensions.
- Removed the dependency on "Request()" API while tracking network requests to avoid side effects of API compatibility to affect xhr or fetch API calls in application.
v0.3.32
v0.3.32 (06/OCT/2023)
- Supports the trackCustomEvent() with JSON Object as an argument.
- Enhances default blocklist for Network Request Tracking.
- Fixes issue of not reporting network request when the fetch request is failed.
- Fixes the issue of target url being reported with only relative path in case of xmlHttpRequest Request is made with relative path by appending
window.location.domain
to the relative path.