Releases: keen/keen-tracking.js
Releases · keen/keen-tracking.js
v3.2.0
v3.1.2
New AutoTracking feature:
- Ability to collect the pageview data when the guest is leaving (unloading) your website.
This way you will get exact number of secondstime_on_page
, or milliseconds to be more precisetime_on_page_ms
. You will get information aboutscroll_state
, that will help you determine in which point people stop reading your content.
To use it, pass this option to your initAutoTracking method
recordPageViewsOnExit: true,
v3.1.0
New:
-
AutoTracking and Listeners are now using the Beacon API to record clicks and form_submissions in a much faster non-blocking manner
-
The autoTracking referrer object receives a new key called:
initial
. Usage: Let's imagine that your guest visited your website 10 times in the last 30 days. Initial referrer is the url that was the very first referrer for this guest. -
Server-side tracking is now Promise-based: recordEvent method returns a Promise. Callbacks are still supported by our library, so it's up to you which coding style you prefer.
v3.0.0
New:
- Ability to handle connection problems:
Keen-tracking.js will automatically retry to record an event if previous request failed.
More about configuration options here:
https://github.com/keen/keen-tracking.js#handling-connection-problems
AutoTracking - IP addresses
New:
- Turn off IP collecting with:
client.initAutoTracking({ collectIpAddress: false });
Fetch & Promises
New:
- Fetch API is now the default method of communication. Polyfill of Fetch included.
- client.recordEvent returns a Promise. Polyfill of Promise included.
FIXED:
- auto-tracking listeners will wait more than 500ms if necessary
Fixes
Move from Gulp to Webpack / UMD
We are upgrading our development tools to match current trends
NEW
- all JS /dist files are now bundled by Webpack 4.8.3 - UMD!
1.4.1 Fixes
v1.4.0 Protocol Handling and Dev Setup
NEW:
- Server-side tracking now respects the
"http"
value forprotocol
option, using thehttp
module. Previously this always usedhttps
, regardless of the configuration value, which can cause issues for internal proxies (#82, via #92 contributed by lukechilds) - Auto-tracking now records
page.time_on_page
(seconds) for all events
FIXED:
- This project now builds and runs correctly in NodeJS v7 and v8 (#95, via #96 contributed by lukechilds)