snowplow-javascript-tracker

Snowplow[1] is an alternative to this. While they have a managed solution, their backend is open source and can be self-hosted. And they have a forked version of the Piwik client side library designed ot work with Snowplow[2]. Snowplow is a bit more generalized than just Piwik, and it shows in Piwik having a more robust featureset for website analytics specific. But Snowplow has a lot more usefulness if you're having to merge a bunch of data sources together to get a picture of what's happening. [1] https://snowplowanalytics.com/ [2] https://github.com/snowplow/snowplow-javascript-tracker

I've heard Snowplow is good. I think it's self-hosted so it's likely more complicated to setup than a complete solution like Google Analytics. But then Google doesn't get the data. https://github.com/snowplow/snowplow https://github.com/snowplow/snowplow-javascript-tracker

The event producer in this case is one of our Snowplow trackers (https://github.com/snowplow/snowplow-javascript-tracker) - and these tracking SDKs do indeed attach a UUID as a unique event ID at event creation time. However, this event ID is not enough to identify and then dedupe all types of duplicate events. This blog post provides more information: https://snowplowanalytics.com/blog/2015/08/19/dealing-with-d... Big thanks to pragmacoders for putting this tutorial together! It's awesome seeing what you are doing with the Snowplow platform :-)

This is known for a while and used to cause huge problems for our tracking: https://github.com/snowplow/snowplow-javascript-tracker/issu...