| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Event | Amplitude event | where | Udayan (1. accurate in amplitude/2. can be tracked/3. can't be tracked/4. needs audit / 5. unsure, need to check / 6. alternative available) | Arghya comments | Adi comments | Example questions of interest | useful for IT Admin | Priority for our analytics- Bharathi | Effort | Backend exists y/n | Udayan Questions | Adi answers | status | |||||||||||||
2 | Action Items | action_items_submit | 1) We could use the ACTION_ITEMS_SUBMIT event | how many meetings had AIs/ last week/ on ios/ by user/ by org | High | Easy | |||||||||||||||||||||
3 | Agenda | agendas_submit | 1) We could use the AGENDAS_SUBMIT event to track this, and the device/user/org details would be available via that event's session info | how many meetings had agenda/ last week/ on ios/ by user/ by org | High | Easy | Y | ||||||||||||||||||||
4 | Org ID | any | org ID= | 1) This should be available via session info | how many times has an Org ID been logged/ last week/ on mobile/ as a host/ as a participant | High | Easy | Y | |||||||||||||||||||
5 | Device | any | device type= | 1) should be accessible via session info | how many meetings joined by mobile/desktop/ last week/ by user ID/ by org ID/ in the last 20 days | High | Easy | Y | |||||||||||||||||||
6 | App type | any | device type= | 1) Should be accessible via session info | Web no differentiation across platforms; OS is captured so can be derived from logs | how many meetings joined by ios/android/mac/windows/ last week/ by user ID/ by org ID/ in the last 20 days | Y | High | Easy | Y | |||||||||||||||||
7 | Audio only | conference_join_call, where joining_with | 1) We should be able to track this via the CONFERENCE_JOIN_CALL event, which has the joiningWith property. Mentions 'audio' or 'video' | Derived from ICM stats | how many meetings were audio only/ last week/ by user/ by org/ by connxn type/ by device | High | Easy | ||||||||||||||||||||
8 | Audio and video | conference_join_call, where joining_with | 1) Same as above | Derived from ICM stats | how many meetings were A&V/ last week/ by user/ by org/ by connxn type/ by device | High | Easy | ||||||||||||||||||||
9 | Meeting scheduled | create_instant_meeting, create_schedule_meeting | 1) We can track this, and we can track whether it was an instant meeting or a regular scheduled one. | how many meetings have been scheduled/ last week/ on ios/ by user/ by org | Y | High | Easy | Y | |||||||||||||||||||
10 | Screen shared | na | 2/4) Seems to be missing, can be tracked | how many meetings has screen been shared/ last week/ on ios/ by user/ by org | High | Easy | Y | ||||||||||||||||||||
11 | PSTN | na | Let's not group. We want to track these separately. | how many meetings were PSTN/ last week/ by user/ by org/ by connxn type | Y | High | Easy | Y | |||||||||||||||||||
12 | Recorded meeting | na | 2) Can be added | how many meetings were recorded/ last week/ by user/ by org/ by connxn type/ by device | Y | High | Easy | Y | |||||||||||||||||||
13 | App version | na | 1) should be accessible via session info | how many meetings joined by app version/ last week/ by user ID/ by org ID/ in the last 20 days | High | Easy | |||||||||||||||||||||
14 | Organizer ID | na | 1) should be accessible via session info | Organizer and Attendee. An attendee is classified as Huddl User and Guest. Guest here is one who doesn't have Huddl credentials and has nothing to do with organization. | how many host IDs by org ID/ in May vs Jun | High | Easy | ||||||||||||||||||||
15 | Attendee ID | na | 1) Should be accessible in Amplitude and meeting analytics dashboard | how many atendee IDs by org ID/ in May vs Jun | High | Easy | |||||||||||||||||||||
16 | Huddl offline | na | 6) not sure how we would like to ideally track this. | Planning to add in logs | number of meetings with offline event/ by Org/ last week/ by connxn type/ below a certain bandwidth | High | Easy | Would meeting analytics maybe be a better dashboard for this? | Bytex mostly for customer IT admin and user management. Let's keep all internal analytics on amplitude? | ||||||||||||||||||
17 | bitrate | na | 6) not sure how we would like to ideally track this. | ICM | average bitrate by user/ org/ connxn type/ device | High | Easy | Would meeting analytics maybe be a better dashboard for this? | Bytex mostly for customer IT admin and user management. Let's keep all internal analytics on amplitude? | ||||||||||||||||||
18 | App crash | na | how many app crashes by version/ device | High | Easy | ||||||||||||||||||||||
19 | 4G | na | 2) will need to check if we can determine the exact network type, but we might be able to provide a rough estimate | number of meetings joined by 4G/ by user ID/ org ID/ kickout event | High | Hard | N | Would meeting analytics maybe be a better dashboard for this? | Bytex mostly for customer IT admin and user management. Let's keep all internal analytics on amplitude? | ||||||||||||||||||
20 | Kick out | na | ICM stats could be used, but no idea how amplitude is tracking | If #conf_end_call>1 AND bandwidth <Xkbps = kickout | how many times has there been a kickout/ last week/ by user ID/ by device/ by Org ID/ guest ID | Y | High | Medium | U: Is this for when the organizer kicks someone out? Or when it happens due to a bad connection? | Bad connxn | |||||||||||||||||
21 | Meetings not attended | na | 3) Can't be tracked via Amplitude | #attendee_IDs - #conf_join_call | how many meetings have not been attended/ last week/ on ios/ by user/ by org/ with more than 10 attendees | Y | High | Medium | Y | ||||||||||||||||||
22 | Highlights | na | 2) Needs to be added, but basically can be tracked. We can also track when a person converts a highlight to an action item | how many meetings had highlights/ last week/ on ios/ by user/ by org | High | Medium | |||||||||||||||||||||
23 | Duration | na | 6) Not sure if it can be tracked. Might be better to view this via meeting analytics. | Derived from meeting start and meeting end | Average meeting duration by user ID/ org ID/ device | Y | High | Medium | Y | How should a duration be defined? | whatever is easier. just length of meeting, or, sum of end_times- sum of join_times | ||||||||||||||||
24 | Wifi | na | 2) we can check if a user is on wifi connection at join time | number of meetings joined by wifi/ user ID/ org ID/ kickout event | High | Medium | N | Would meeting analytics maybe be a better dashboard for this? | Bytex mostly for customer IT admin and user management. Let's keep all internal analytics on amplitude? | ||||||||||||||||||
25 | 3G | na | 2) we can also check if a user is on a cellular connection | number of meetings joined by 3G/ by user ID/ org ID/ kickout event | High | Medium | N | Would meeting analytics maybe be a better dashboard for this? | Bytex mostly for customer IT admin and user management. Let's keep all internal analytics on amplitude? | ||||||||||||||||||
26 | Guest ID | na | 6) not sure how we would like to ideally track this. | number of meetings with guest ID/ by Org/ with kickout event/ offline event | High | Medium | Any Guest in a meeting would count? | Bytex mostly for customer IT admin and user management. Let's keep all internal analytics on amplitude? | |||||||||||||||||||
27 | Frame rate | na | 6) Can be tracked. We'll need to push some average measurement per user after the meeting ends for this. | what is average frame rate/ last week/ by device/ by user ID/ by org ID/ by app version/ by connxn type | High | Medium | Y | Could some of these be tracked via the meeting analytics dashboard instead? There seems to be an overlap. In terms of metrics, we might not want to pass that info through amplitude on top of our own collation | Bytex mostly for customer IT admin and user management. Let's keep all internal analytics on amplitude? | ||||||||||||||||||
28 | Bandwidth | na | 6) Same as above | what is average bandwidth/ last week/ by device/ by user ID/ by org ID/ by app version/ by connxn type | Y | High | Medium | Y | Same as above | Bytex mostly for customer IT admin and user management. Let's keep all internal analytics on amplitude? | |||||||||||||||||
29 | Huddl invitation accepted | na | how many employees at prospect accepted invitation | High | Medium | ||||||||||||||||||||||
30 | CPU usage | na | what is cpu usage by version/ org/ device | High | Medium | ||||||||||||||||||||||
31 | Battery usage | na | what is battery usage by version/ org/ device | High | Medium | ||||||||||||||||||||||
32 | Meetings attended | conference_join_call | 6) Same as above | how many meetings have been attended/ last week/ on ios/ by user/ by org/ with more than 10 attendees | Y | High | NA | Y | |||||||||||||||||||
33 | App uninstalled | na | 3) Can't be tracked as of now | No way as of today | Can use daily motes unsubscribe and no meeting scheduled as proxy | how many app uninstalls/ last week/ on desktop/ by user/ by org | High | NA | |||||||||||||||||||
34 | New user | new user | 2) We can track installation per user only after a user starts using for the first time. We can also track gross # of installations without user info. | We cannot track this, download can be captured but not installation. Installation can be tracked only after a user logs in | how many app downloads/last week/ on device/ by user/ by org | High | |||||||||||||||||||||
35 | Moment capture (heart icon) | na | High | ||||||||||||||||||||||||
36 | Notes | notes_submit | 1) We could use the NOTES_SUBMIT event | how many meetings had notes/ last week/ on ios/ by user/ by org | High | Y | |||||||||||||||||||||
37 | Search | na | 2/4) Events for SEARCH need to be added | how many meetings did users search/ last week/ by user/ by org/ by device | Low | N | |||||||||||||||||||||
38 | Hovered on assistant | assistant_open, assistant_close | 1) Should be accessible via ASSISTANT_OPEN/ASSISTANT_CLOSED events | how many meetings did users hover on assistant/ last week/ by user/ by org/ by device | Low | Easy | |||||||||||||||||||||
39 | User ID | any | user ID= | 1) This should be available via session info | How is the data being recorded? Host ID, Attendee ID, Guest ID | how many times has a user ID been logged/ last week/ on mobile/ as a host/ as a participant | Low | Y | |||||||||||||||||||
40 | Recorded timeline | na | how many meetings recorded timeline/ last week/ by user/ by org/ by connxn type/ by device | Low | Does this mean was the timeline opened/viewed? | User clicked record timeline | |||||||||||||||||||||
41 | Sent Message | na | 1) Should be trackable via which app was used in the meeting, via the CONFERENCE_SELECT_ACTIVITY event + CHAT_SUBMIT | how many meetings did users send a message/ last week/ by user/ by org/ by device | Low | N | |||||||||||||||||||||
42 | Clicked settings | na | 2) Can be added | how many meetings did users click settings/ last week/ by user/ by org/ by device | Low | N | |||||||||||||||||||||
43 | Changed theme | na | 1) Is accessible via APP_SELECT_THEME event | how many meetings did users change theme/ last week/ by user/ by org/ by device | Low | N | |||||||||||||||||||||
44 | Changed brightness | na | 2) can be added | how many meetings did users change brightness/ last week/ by user/ by org/ by device | Low | N | |||||||||||||||||||||
45 | Changed image | na | 2) can be added | how many meetings did users change image/ last week/ by user/ by org/ by device | Low | ||||||||||||||||||||||
46 | App responsiveness | na | what is app speed by device/ version | Low | |||||||||||||||||||||||
47 | Instant meeting - Search participant | FREQUENT_CONTACTS_SEARCH_USER | |||||||||||||||||||||||||
48 | Search icon | SEARCH_OPEN | |||||||||||||||||||||||||
49 | Search for keyword(Either hit enter or click on the search icon ) | SEARCH_SUBMIT_QUERY | |||||||||||||||||||||||||
50 | Clear text | SEARCH_CLEAR_QUERY | |||||||||||||||||||||||||
51 | Search and enter | CHAT_FOCUS_FILTER_INPUT | |||||||||||||||||||||||||
52 | Take a screenshot(Image search) | PRESENTATION_SEARCH_SLIDE | |||||||||||||||||||||||||
53 | In-meeting search | APP_MENU_SELECT_ACTIVITY, { activity: ‘Search’ } | |||||||||||||||||||||||||
54 | Text search and image search(Toggle) | SEARCH_TOGGLE_SEARCH_MODE, { mode: 'text' || 'image' } | |||||||||||||||||||||||||
55 | Filters open | SEARCH_EXPAND_FILTERS | |||||||||||||||||||||||||
56 | Filters close | SEARCH_COLLAPSE_FILTERS | |||||||||||||||||||||||||
57 | See more button | SEARCH_VIEW_MORE, { type: 'Meetings' || 'Action Items' || 'Agendas' || 'Notes' || 'Moments' } | |||||||||||||||||||||||||
58 | More button(Three Dots) | LANDING_MORE_OPTIONS, { open: true || false } | |||||||||||||||||||||||||
59 | Action items assigned to you | LANDING_SHORTCUT_OPEN_ACTION_ITEMS_TO_YOU | |||||||||||||||||||||||||
60 | Action items assigned by you | LANDING_SHORTCUT_OPEN_ACTION_ITEMS_BY_YOU | |||||||||||||||||||||||||
61 | Create meeting shortcut | CREATE_MEETING_START | |||||||||||||||||||||||||
62 | Calendar - Change date(Arrows - Next and Previous) | LANDING_CALENDAR_QUICK_NAVIGATE, { direction: 'previous' || 'next' } | |||||||||||||||||||||||||
63 | Go to next meeting | LANDING_FOCUS_NEXT_MEETING | |||||||||||||||||||||||||
64 | Instant meeting - Frequently called user | FREQUENT_CONTACT_SELECT | |||||||||||||||||||||||||
65 | Meeting card - more options | MEETING_CARD_MORE_OPTIONS | |||||||||||||||||||||||||
66 | Meeting card - Copy joining info | MEETING_CARD_COPY_JOINING_INFO | |||||||||||||||||||||||||
67 | Meeting card - Set callback | MEETING_CARD_SET_CALLBACK | |||||||||||||||||||||||||
68 | Meeting card - Cancel callback | MEETING_CARD_CANCEL_CALLBACK | |||||||||||||||||||||||||
69 | View meeting/ Join meeting | LANDING_SELECT_MEETING | |||||||||||||||||||||||||
70 | Assistant navigation | APP_MENU_OPEN, { location: ‘landing’ } | |||||||||||||||||||||||||
71 | Notifications | APP_MENU_SELECT_ACTIVITY, { activity: 'Notifications' } | |||||||||||||||||||||||||
72 | Discard notification | NOTIFICATIONS_CLEAR_ONE | |||||||||||||||||||||||||
73 | Clear all | NOTIFICATIONS_CLEAR_ALL | |||||||||||||||||||||||||
74 | Do not disturb | NOTIFICATIONS_SET_DO_NOT_DISTURB | |||||||||||||||||||||||||
75 | Action Items | APP_MENU_SELECT_ACTIVITY, { activity: ‘Action Items’ } | |||||||||||||||||||||||||
76 | Action items - Assigned to me | ACTION_ITEMS_TAB_ASSIGNED_TO_ME | |||||||||||||||||||||||||
77 | Action items - Assigned to me | ACTION_ITEMS_TAB_ASSIGNED_BY_ME | |||||||||||||||||||||||||
78 | Mark as done | ACTION_ITEMS_SET_COMPLETED, { completed: true || false } | |||||||||||||||||||||||||
79 | Open in motes | ACTION_ITEMS_OPEN_IN_MOTES | |||||||||||||||||||||||||
80 | Edit action item | ACTION_ITEMS_SET_EDITING | |||||||||||||||||||||||||
81 | Delete action item | ACTION_ITEMS_DELETE | |||||||||||||||||||||||||
82 | Settings | APP_MENU_SELECT_ACTIVITY, { activity: 'Settings' } | |||||||||||||||||||||||||
83 | Meeting card - Arrows(Previous and Next) | MEETING_CARD_NAVIGATE_CAROUSEL, { direction: ‘previous’ || ‘next’, isKeyPress: true || false } | |||||||||||||||||||||||||
84 | Schedule meeting - Select participants | SCHEDULE_MEETING_SELECT_PARTICIPANT | |||||||||||||||||||||||||
85 | Schedule meeting - Remove participants | SCHEDULE_MEETING_REMOVE_PARTICIPANT | |||||||||||||||||||||||||
86 | Meet now | CREATE_INSTANT_MEETING | |||||||||||||||||||||||||
87 | Schedule meeting | CREATE_SCHEDULE_MEETING_START | |||||||||||||||||||||||||
88 | Date | SCHEDULE_MEETING_SET_DATE, { which: 'start' || 'end' } | |||||||||||||||||||||||||
89 | Time | SCHEDULE_MEETING_SET_TIME, { which: 'start' || 'end' } | |||||||||||||||||||||||||
90 | Next | SCHEDULE_MEETING_NEXT | |||||||||||||||||||||||||
91 | Back | SCHEDULE_MEETING_BACK | |||||||||||||||||||||||||
92 | Confirm meeting | CREATE_SCHEDULE_MEETING | |||||||||||||||||||||||||
93 | Edit meeting details | SCHEDULE_MEETING_EDIT | |||||||||||||||||||||||||
94 | Select mic in settings | SETTINGS_SELECT_MICROPHONE | |||||||||||||||||||||||||
95 | Select camera in settings | SETTINGS_SELECT_CAMERA | |||||||||||||||||||||||||
96 | Select speaker in settings | SETTINGS_SELECT_SPEAKER | |||||||||||||||||||||||||
97 | Speaker test sound | SETTINGS_SPEAKER_TEST | |||||||||||||||||||||||||
98 | Theme | APP_TOGGLE_THEME | |||||||||||||||||||||||||
99 | Lobby | ||||||||||||||||||||||||||
100 | Close lobby | LOBBY_CLOSE, { variant: ‘lobby’, ‘motes’, ‘preview’ } |