-
Notifications
You must be signed in to change notification settings - Fork 145
Create Tracks Client Wrappers #8
Comments
If we're going to support no-Jetpack users then we shouldn't create any dependencies on Jetpack code. We'll need to decide on how we identify sites (as there may not be a wp.com |
I totally understand that only a percentage of Woo users will likely have Jetpack installed so it restricts how many interactions we can track, but in-lieu of rolling our own tracks tooling I figured having a sample of usage would be better than none. Other consideration here is we can collect usage data via tracks by using Jetpack, and are okay doing so based upon the T.O.S. that Jetpack users agree to, so our feature plugin here can steer a bit clear of that and just use the tooling that is in place already. From a data-science standpoint, do you think the number of Woo sites with Jetpack connected is statistically large enough to base usage trends from @greenafrican ? |
Yeah, the trends from Jetpack connected sites are very representative of the population.
|
/cc @allendav if you wanted to chime in with any comments you had from our hangout today. One other concern I have with adding new tracks/tracker specific logic here is it might be cause some users to not test out the feature plugin potentially. |
The JP tracks PHP class prepends all event names with The admin JS client doesn't prepend |
Yeah I was a bit worried about that, but I suppose we could still get useful information even with using the jetpack namespace, alternatively we submit a PR there that makes the prefix configurable. |
The good news is that |
Closing this out since #452 shows the tracks wrapper working end-to-end 🎉 |
Collecting usage data of the new Analytics and Dashboard projects will be key to determine which features our users are interacting with most frequently. During the last woo-dash hangout we discussed the notion of using the Jetpack Tracks Clients to implement tracks within dash/analytics.
Goals
The text was updated successfully, but these errors were encountered: