Release History - medullan/navocat-collector GitHub Wiki

See also https://github.com/medullan/navocat-collector/releases

Release v2.2.0 - Current

Features

The Request Verification API (RVA) is a tool used to verify analytics hits sent to the Collector. Such hits are classified currently as IDENTIFY, PROFILE, PAGE, TRACK and ENDSESSION. RVA will generate a record/log for each hit and stores useful information about all interactions/events that occurred for this hit. These interactions/events mentioned are things such as sending information to external sources such as Google Analytics (GA), writing information to disk or even exceptions that occurred during the processing of each hit.

See https://github.com/medullan/navocat-collector/wiki/Request-Verification-API for more information.

Release v2.1.2

Features

Client ID Expiration: Persists the client id cookie for the entirety of the user browsing session.

Release v2.1.1

Features

Dynamic logging: Provides the ability to change the application log level at runtime by updating the configuration file.

Release v2.1.0

Features

Server Based Session Unification: The client id that is used by Google Analytics for session unification is now generated by the Collector. Previously the client id was generated and maintained by the client side javascript. The Collector will ensure that a client id cookie is set for all http requests.

IE Compact P3P Support: Allow IE P3P policy

GA Debug API Hit Validation: This feature enables the collector to log the validity of http request going to Google Analytics. This log can be inspected for the http requests to Google Analytics that failed, and the reasons why it failed.

Bugs

Remove database calls for anonymous page hits/requests

Release v2.0.0

Features

Enhanced datastore suppor:

  • Redis
  • H2
  • Ruby In Memory Hash

The in memory profile data store was changed from Mapdb to Redis as the main datastore. Ruby in memory hash is used for testing and debugging purposes.

Deterministic Profile Id:

  • Profile id are always the same for each member and are no longer time dependent
  • Single Key to Profile Data
  • Support for multiple keys to the same profile data is deprecated.
  • Single member_id is now recommended.

Feature Toggling

  • New features such as logging and single profile id as keys are togglable

Logging Metrics

Benchmarks for datastore queries

Bugs

Removal of cb from profile data