Skip to content
This repository has been archived by the owner on Apr 28, 2018. It is now read-only.

Add & verify telemetry probes #553

Open
mcomella opened this issue Feb 24, 2017 · 1 comment
Open

Add & verify telemetry probes #553

mcomella opened this issue Feb 24, 2017 · 1 comment

Comments

@mcomella
Copy link
Contributor

Initial comments: collect the same data we did in Hawaii.

@mcomella mcomella added this to the Sprint #3 – map view milestone Feb 24, 2017
@mcomella mcomella changed the title Add telemetry Add & verify telemetry probes Feb 24, 2017
@mariappopova mariappopova removed this from the Sprint #3 – map view milestone Mar 9, 2017
@brampitoyo
Copy link

I’ve been thinking about solving some problems with analytics in a document called Detecting Activities.

The gist of my proposal was to correlate some of the data that we’re already planning to collect (under the heading “Optional for Prox v2”) and some new data:

  • (Item 11) What individual cards in the Home view are being viewed?
  • (Item 12) What cards serve as user session end points? (i.e. cards where they click on a link for directions)?
  • (New) How many users ended up actually arriving (being in the proximity of) at a place after tapping “Get directions”?
  • (New, but for the future) What places get rated (using third-party app, connected to Prox) after a visit?

TL;DR – We should add telemetry probes for which cards are viewed in the app, and which cards are visited in real life.

By collecting this data, I argued that we’d be able to augment our default sort order. Instead of sorting by proximity, we can prioritise cards with the same same category as:

  1. Cards you’ve highly rated in Yelp, TripAdvisor and/or Foursquare
  2. Cards you’ve physically been to
  3. Cards where you’ve tapped “Get directions”
  4. Cards that you’ve spent a lot of time viewing/engaging with

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants