1. Time period selection

When using daily_sessions, to use a longer period (ex: 2 months), is better than just one week. Also, try to focus on the usage trend instead of an isolated usage metric for a specific period. And ask yourself this question; how often do your clients need to connect to your App?

2. Use of "And" & "OR"

Use of AND / OR: "And" in Good can be risky as it might be too demanding and many Accounts will fall into Bad or Average. "Or" is much less demanding.

3. Daily sessions

Daily sessions can be more relevant than sessions, as it indicates that your client has been in the Solution at least once each day (for example over a full week period), whereas sessions can all happen on the same single day.

4. Weekend days

Weekend days are counted as normal days in our time periods (e.g: in the last week, month, etc..). It needs to be taken into account if your Users are connecting during office hours only.

5. Complex Health conditions

Avoid adding too many conditions in your Health Score as it can create confusion when it comes to understanding Health evolution reasons (e.g from Good to Bad). It is always good to have a group of 1 to 3 max, health conditions on top of mind.

6. Set, then iterate

Your first Health configurations are usually not the most efficient one, but it finetunes progressively as you will understand which health conditions settings you can improve.

Did this answer your question?