Closed cvan closed 3 months ago
I'm going to defer working on this for now, since @delapuente has gotten Google Analytics-based Telemetry working quite nicely with in the telemetry
branch branch and the incoming changes in PR #200.
The main reason I filed this was to hide the complexity in a script we could remotely update/improve whenever we needed. I still think we should do it. I've been iterating on a proof-of-concept in branches at https://github.com/MozillaReality/metrics It's built atop Google's Universal Analytics (i.e., the server-side Measurement Protocol API).
But the analytics.js
approach taken here is sufficient. So given the lack of urgency here, I'm moving this issue out of this milestone.
@delapuente: I'd like your input on whether we should move some of these Telemetry issues I just filed into the Telemetry
milestone or the v1.1.0
milestone: #206, #207, #208
Ideally, we get those three resolved before we tag and release a new version of this package to the Unity Asset Store. I can most definitely help here; I just wanted you to see the feedback from https://github.com/mozilla/unity-webvr-export/pull/200/files first before I started triaging Telemetry issues more. Thanks!
Move https://github.com/mozillareality/metrics to its own repo. Instead of using Google's
analytics.js
, we can use Google's Universal Analytics. You can just usenavigator.sendBeacon
to POST a JSON payload tohttps://ssl.google-analytics.com/collect
.Current work in progress: https://github.com/MozillaReality/metrics
Some context here about documenting it: https://github.com/mozilla/unity-webvr-export/issues/164#issuecomment-372900401
That way, it won't interfere with a user's Google Analytics script they put on their page. And it's as simple as dropping in this script: