Stream Collector v2.1.1
In version 2.1.1 we identified an issue where in a scenario where anonymous tracking was turned on, then off and then back on again users could still be identified via the “leftover” cookie in their browser which populates the
network_userid field. This user had previously allowed their user identifiers to be captured, which meant the cookie was stored in the browser from the collector and subsequently is automatically sent, by the browser, with all future requests.
Stream Collector v2.1.2
To resolve this issue, we introduced 2.1.2 which removed the
Stream Collector v2.2.0
The behaviour from 2.1.2 was carried over in the subsequent 2.2.0 release.
We’re sorry this fell through our testing. The v2.1.1 issue was an untested edge case (which we address with additional tests in v2.1.2) and the other uncovered a gap in our integration testing. We’re addressing the latter with urgency.