This repository has been archived by the owner on Feb 29, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 112
Engagement data collection #28
Labels
Milestone
Comments
Other measurements:
Other engagement metrics TBD
|
|
emtwo
pushed a commit
that referenced
this issue
Feb 17, 2016
following a meeting with @nchapman, @tspurway jotted down some notes in #27. The pings should be as follows: When a user opens a newtab page, we make note of the time (start a counter). We then capture an exit condition:
In case #1, when that happens, we want to record:
in case #2 we only want to record an impression, but that they used the URL bar, and the dwell time in case #3 we only want to record an impression, but that they closed it, and the dwell time There may be more things to record, or more use cases, but this should give a good idea |
emtwo
pushed a commit
that referenced
this issue
Feb 20, 2016
emtwo
pushed a commit
that referenced
this issue
Feb 20, 2016
emtwo
pushed a commit
that referenced
this issue
Feb 22, 2016
emtwo
pushed a commit
that referenced
this issue
Feb 22, 2016
feature(addon): #28 Tab open time data collection.
ScottDowne
added a commit
to ScottDowne/activity-stream
that referenced
this issue
Oct 9, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Implement code in add-on to send messages to data-pipeline.
Maybe start with a few messages add-on side, we can do content in a follow-up ticket
The text was updated successfully, but these errors were encountered: