usage statistics tracking, form submission

noamoss commented 4 years ago

Part of #236

Here's what we want to know (checked the metrics we already hold):

[x] layout (display/device type)
[x] referrer *
[x] age (of first responder)
[x] city
[x] date of first report
[x] referrer of first report *
[x] number of reports so far
[x] HP map visit
- [x] map help interaction: (?)
- [ ] map interaction: (swipe, zoom, etc…)
- [ ] map engagement: (time)
[ ] HP scroll
[x] HP tabs
[x] number of entries in the report (reporting for others)
[x] end of flow map expand (prompted "preview")
[ ] share (which channel)
[x] reminder (which channel)
[ ] total engagement time
[ ] avg engagement time (local data's avg)

noamoss commented 4 years ago

@mushon please elaborate on what data needs to be collected on submission.

mushon commented 4 years ago

Here's what we want to know (check the ones we already know and suggest additions and edits):

[ ] device (desktop / mobile / tablet / other)
[ ] referrer
[ ] age (of first responder)
[x] city
[x] date of first report
[ ] referrer of first report
[x] number of reports so far
[ ] HP map visit
- [ ] map help interaction: (?)
- [ ] map interaction: (swipe, zoom, etc…)
- [ ] map engagement: (time)
[ ] HP scroll
[ ] HP tabs
[ ] number of entries in the report (reporting for others)
[ ] end of flow map expand (prompted "preview")
[ ] share (which channel)
[ ] reminder (which channel)
[ ] total engagement time
[ ] avg engagement time (local data's avg)

noamoss commented 4 years ago

@mushon

(check the ones we already know:

done

device (desktop / mobile / tablet / other

currently, we have layout: "desktop" / "mobile" (which is practically wide/narrow display). Is it enough? what is other?

referrer

I assume you don't mean the referrer URL, please approve. We already have the ?source=[x] parameter.

number of first reports so far

If you mean first-time users/joiners - we have that available on the dashboard, by date.

number of entries in the report (reporting for others)

a bit tricky - different users can cooperate on the save device. Do you assume the first reporter created in the device is the owner ("main"), reporter? This can help differentiate "my reports" from "other's reports"

HP tabs / maps

what do you want to know?

suggest additions and edits:

add: total engagement time, avg. engagement time

mushon commented 4 years ago

layout

we can stay with that

referrer

It would be useful to know how do people get to the site, even if they don't use our custom urls. But I'm not sure it would jive well with our privacy policy.

number of reports so far

I mean how many reports did this device submit before this one

HP tabs / maps

How many people visit these pages

additional edits

added

noamoss commented 4 years ago

@mushon

[referrer] It would be useful to know how do people get to the site, even if they don't use our custom urls. But I'm not sure it would jive well with our privacy policy.

It won't, but as a reminder - there is an alternative solution of separating data from user/reporter which could solve this obstacle. Not sure it worth the effort.

I mean how many reports did this device submit before this one

Currently, have a submissions counter in the reporter level, not the device level. Is it something to add/change?

[HP tabs/maps] How many people visit these pages

Just the total number? Don't you care about the ongoing usage (total/per user) of these pages? Let's define all the necessary(!) questions we know we would like to track, to better define the required metrics.

noamoss commented 4 years ago

@akariv Some of the metrics discussed here are at the device level and others are at the reporter level. Is it a problem?

akariv commented 4 years ago

Not sure what's the difference between device and reporter in this context. Is it possible that you want to separate a 'report' and a 'session'?

One thing that comes to mind - some of these metrics are only known after the reports had been sent (e.g. share / reminder interaction). These would have to be sent separately - which brings me to support @noamoss suggestion of separating the medical and interaction data into two separate tables.

noamoss commented 4 years ago

@akariv

Not sure what's the difference between device and reporter in this context.

device == data points related to all of the reporters (for example referrer- all the reports were sent thanks to the same share link or the same reminder or number of entries reported today) while a reporter is a person-centered metric (like engagement time per report)

noamoss commented 4 years ago

These would have to be sent separately - which brings me to support @noamoss suggestion of separating the medical and interaction data into two separate tables.

@mushon assuming you agree as well, I believe that will enable us to collect much more useful data.

mushon commented 4 years ago

Indeed, as agreed, we will start with analyzing what we get and create new requirements based on that analysis

akariv commented 4 years ago

Most is done, I suggest we analyze what we currently have and open a new issue with the new requirements.

maryLoi commented 4 years ago

@noamoss

noamoss commented 4 years ago

I will explore and update, hopefully within 2 days.

noamoss commented 4 years ago

Available Data points int he device / main user level:

layout (display/device type)

V

referrer

V

age (of first responder)

V

city

X

date of first report

V

referrer of first report

V

number of reports so far

V

HP map visit

V

map help interaction: (?)

V

map interaction: (swipe, zoom, etc…)

X

map engagement: (time)

X

HP scroll

X

HP tabs

X

number of entries in the report (reporting for others)

V

end of flow map expand (prompted "preview")

Irrelevant

share (which channel)

Partly: True/False, no share channel

reminder (which channel)

V

total engagement time

X

avg engagement time (local data's avg)

X

noamoss commented 4 years ago

@mushon these are the relevant data points in the device level. I will spend 1-2h to generate relevant queries (on #236). Feel free to throw in relevant questions, you can assume I will think of the obvious ones.

akariv commented 4 years ago

@noamoss:

I think you missed:

main_city: main reporter's city
hp tabs and share channel are implemented (they only appear when they are true)

On Sun, May 3, 2020 at 4:25 PM noamoss notifications@github.com wrote:

Closed #197 https://github.com/hasadna/avid-covider/issues/197.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hasadna/avid-covider/issues/197#event-3297419981, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACAY5O5DURUF6EYH57ERP3RPVWDPANCNFSM4MHSXKPA .

noamoss commented 4 years ago

@akariv can you be more explicit about hp_tabs metric logic? What/when does it count?

akariv commented 4 years ago

It's true if the specific hp tab was clicked

akariv commented 4 years ago

{"layout":"mobile",
 "locale":"he",
 "version":"2.7.6",
 "location":"https://coronaisrael.org/",
 "main_age":"17",
 "main_uid":"aCAGDN",
 "referrer":"https://www.google.com/",
  "num_aliases":0,
 "dateFirstReport":"2020-03-25T14:52:20.443Z",
 "hasLocalStorage":true,
 "engagementSource":"direct",
 "originalReferrer":"https://www.google.com/",
 "event_hp_tab_about":true,
 "event_hp_tab_media":true,
 "event_share_action":false,
 "numPreviousReports":1,
 "notificationsEnabled":false,
 "action_reminder_wanted":"wanted",
 "action_reminder_required":"required",
 "action_reminder_selected":"telegram",
 "event_hp_map_nudge_shown":true,
 "action_reminder_telegram_approved":true,
 "affiliate_questionnaires_preference":"ok",
 "affiliate_questionnaires_preference_alon_chen":"ok"
}

hasadna / avid-covider

usage statistics tracking, form submission #197

Available Data points int he device / main user level: