Scripts for Anthology. Datasnipper notes.
This commit is contained in:
@ -339,6 +339,19 @@ API Endpoint:
|
||||
Issuer:
|
||||
* https://login.microsoftonline.com/43f1ba74-0140-48d7-9ded-17e6e43a6ef6/wsfed
|
||||
|
||||
## 04-29-2024
|
||||
|
||||
## 05-30-2024
|
||||
|
||||
Health Scoring for DataSnipper
|
||||
* Started very sentiment based and everyone had a different sentiment
|
||||
* Zoom and CE bringing in data for new healthscores.
|
||||
* Zoom: if attendee, this improves score. Live attendee data being pulled.
|
||||
* All based on email domain - anyone with a domain can influence the health score
|
||||
* Courses: Enrolled or Completions
|
||||
* Health Scoring is strictly based on completions
|
||||
* Recent "middle step" of health score found some misalignments and found health scores are better than sentiment would lead them to believe.
|
||||
* Outside of client engagement, making the process more complex - activated in product, how many features being used, total activity numbers in use etc.
|
||||
* Ideally they would like to attach specific courses to features and track feature usage post course completion
|
||||
* Number of features being used has direct correlation to stickiness
|
||||
* KPIs are the health scores
|
||||
* Academy can negatively affect the score from the perspective if _no one_ accesses or completes a course.
|
||||
* 0-10, below 50% of people have completed a course, health score is 0
|
||||
|
||||
Reference in New Issue
Block a user